Ruby Gems is a package management framework for Ruby. You must have an installation of Ruby Gems before this update can be applied.
See Gem for information on Ruby Gems (or Ruby Gems is maintained by Ruby Together, a grassroots initiative committed to supporting the critical Ruby infrastructure you rely on.
If you don’t find what you need on Google and you have an idea what gem is causing issues, the next place to search is the issues page for the gem’s Github repository.
Too often Ruby developers will blindly copy-paste their error messages into a Google search without really reading the console output carefully.
This can actually waste more time, since thinking about the problem for a moment can often give you a solution without Google, or you’ll write a better search query.
If you don’t have adequate tests, then be ready to do some adequate manual testing.
Even if you have lots of tests, you still need to do manual testing if you upgrade a UI library such as to see what got updated.
At least you’ll be able to quickly verify a good chunk of your app can at least navigate the “happy path” as you iterate updating your gems.
If you’ve updated gems recently, sometimes you can run and everything works great.
If you don’t get any search hits, then typically you have some problem in app customizations (see below).
Some essential places to look at when upgrading gems are: Errors or deprecation messages can come from compatibility issues among your gems. If you’re having an upgrade issue, then a concise, detailed post of a new issue typically results in a very quick response. I search for gems on Ruby Gems so often that I created a Chrome search shortcut.
Unless you have a good reason, don’t lock a gem to a specific version as that makes updating gems more difficult.
In general, consider only locking the major Rails gems, such as rails, RSpec, and bootstrap-sass, as these are the ones that will likely have more involved upgrades. It’s not necessary to introduce the added complexity of the test accelerators when doing major library updates. Naturally, it’s an iterative process to get tests passing when updating gems. You can try updating the gems one by one until you get a test failure.
Recently, that strategy failed miserably when I tried going from Rails 4.0 with RSpec 2.2 to Rails 4.1 and RSpec 3.