Re:How fresh are your gems?
by jwilliams on Thursday September 29, 2011 @12:04AM
(#3051080)
Doesn't keep me up at night, but it was something I was doing manually and I thought better off scripted. Even with fuzzy/handwave "~> 1.1.1" specifications you can end up off the most current version. I've got a handful of projects on the go and as a rule I don't like to let them go stale.
[ Parent
| on HN ]
but, just simply leaving the version number blank, "bundle update" will get the latest. correct?
Yes, that's correct.
Personally I always assign the working version numbers to the Gemfile. What happens in say a years time when you're meant to come back and maintain the site? New versions could mean a drastically broken system and you won't be maintaining a contracts codebase if you are not getting paid to do so.
The .lock file will have the versions that are currently bundled, so you can always check what versions are bundled there. But I guess that requires a bit of messing around, where as what you do seems quite straight forward.
Yes but if the repository is cloned with a lock file, when you bundle install, the lock file is then updated with your new gem versions if you have not specified a specific gem version number.