spree/spree — comment on commit 87db50934376e05f44530ce2330f9bb2782f1403
File:  line 0
By sbeam:

the problem with when you always "explicitly freeze the gem dependencies" is that you prevent spree users from upgrading a certain gem in case there is an important bugfix - they'd have to wait for a new release of spree just to (hopefully) allow bundler to grab the new version. This is what the `~>` operator is for -- although I admit you are then victimized when gem authors break back-compat on point-releases, which happens as we see here. But, in that case, that's exactly the kind of thing that CI is there to catch and should be treated as a special case.

the reason I have an opinion, in fact, was because I just found an issue in paperclip that means I need 2.5.0, but can't get it because I am on spree 1.0.0.rc2 which required `paperclip '=2.4.1'`. Fortunately I am not in production yet so can go to edge to get this commit, but in the case of a production app which was a couple versions behind, I'd be SOL.