Updating gem

Thus, after some months, you should try to remove any previously necessary github references in your Gemfile.

I ran into a case where including rspec-instafail before rspec resulted in zeus failing due to In general, when doing relatively major gem upgrades, you really need to evaluate customizations to these places.

Sometimes the fix you need has already been released to Ruby Gems in an RC version (RC means Release Candidate). Here’s an example of an RC version gem that I’m currently using: Sometimes what you need has not been shared with Ruby Gems, yet the issue has received commits on Github.

Here’s my favorite reasons for keeping gems relatively current: That being said, recent versions can have new bugs, so it’s best to avoid versions that are unreleased or that haven’t aged at least a few weeks.

I.e., don’t do a without specifying which gems to update. And then when tests fail, you won’t be able to easily decipher which dependency is the problem.

Specify which gems to update by running the command: and verify your tests pass. Consider putting a summary of how many tests pass and how long it takes.

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.

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.

You must have an account to comment. Please register or login here!