Updating gem version

In the last two tutorials we've built a gem and added tests and documentation.

We're going carry on working with the same gem, first publishing it on and Github, and then finishing it off by adding an executable.

Luckily for me, the previous developer had checked in the application’s So how do you keep your dependencies in line?

The best way is to make a habit of including version numbers as you add dependencies.

Therefore, specifying versions like this is considered the safest method.

For minor and major releases, things can be broken and so developers should take care when running any kind of task that updates their gems to the latest version.

Still, there are some tips for using Bundler that will make deployment much easier.

Because we've specified a major, minor and tiny version here, we'll get the latest tiny release of the , only patches.At Engine Yard, we advocate for the use of Bundler in users’ applications, mainly because it makes dependency management very easy.Avrohom Katz wrote a post with pro tips for Bundler and Evan Machnic wrote a post about some issues with Bundler and Rails 3.1.If you are making a minor update (for example from 3.3.1 to the latest version at the time 3.3.2) run ‘bundle update jekyll’ when in your site directory.If you would like to update all your gems, run ‘bundle update’ when in your site directory.

Leave a Reply