Updating gem version Free granny hookups com
Periodical update Every so often, gem update to update all gems with the latests bugs fixes and all for everything I'm using.
Even assuming a perfectly setup Gemfile, and all gems using semantic versioning, there are still regressions possible and I will have my QA team go over everything (say I don't have complete integration specs, I'm not perfect you know).
bundler/bundler#2016 potentially more things then I want will be updated.
Are things still supposed to work like @indirect says? @chrismo I don't have a simple repro, sorry, these things tend to occur in complicated gem files.
What this issue is asking for is related to the quote above, originally from indirect.
Consider a Gemfile with lots of things in it, including . But it's not clear to me that bundler/bundler-features#122 is describing anything like this at all.
Or worse, result in devs fiddling with their (see Options 1 & 3 in this post).
Rails (the gem) does not conform to Semantic Versioning, and therefore the best practice is to explicitly state which version of Rails your application is compatible with in your Gemfile.
Bundler will honor explicit versions set in the Gemfile, even while you run 1 for "bundle update [some gem] [--conservative]" (where '--conservative' can only be added when a gem name is specified on the bundle update command).
"Conservative updates" appears to have varying meaning to folks and your reply plus the comments on 122 from yesterday are already drawing out some additional use cases that weren't at the forefront of my mind when I wrote what I did.
If you're cool with it, I'd like to move this discussion over to that issue, so we can try to accumulate discussion there.
Fetching version metadata from https://rubygems.org/... Fetching dependency metadata from https://rubygems.org/.. You have requested: rails = 4.2.5 The bundle currently has rails locked at 4.2.0.