UPDATE 2014-12-21: Ruby Gems 1.8.30, 2.0.15, and 2.2.3 have been released.
It requires manual installation, please see instructions below.
@byrnejb : Do you have a link to a blog post or other explaining how P. If you run bundle update --source gem_name and gem_name is not updated then gem_name has other dependencies which differ from those already locked.
You will have to discover which of these dependencies must be updated to allow gem_name to update as well.
There are a couple of solutions I’ve seen people use to solve this.
Neither of them is that great: would just update that gem.
All source code included in the card How to update a single gem conservatively is licensed under the license stated below.
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).
This error is produced by changes in infrastructure. Please follow the instructions below to update your Ruby Gems: Now that Ruby Gems 2.6.x has been released, you can manually update to this version.
Download the latest Ruby Gems Please download the file in a directory that you can later point to (eg.