News for hackers. Stuff that matters.
Re:Rails 3.2.13, 3.1.12, and 2.3.18 have been released by techpeace on Monday March 18, 2013 @05:14PM (#5397165)
Anybody else unable to to upgrade via bundler? I can report also seeing the following behavior: https://twitter.com/jamesgolick/status/313751280210288641

Not sure if this is a rails, bundler, or rubygems issue, at this point.

Re:Rails 3.2.13, 3.1.12, and 2.3.18 have been released by gsiener on Monday March 18, 2013 @11:02PM (#5398658)
I had this issue as well. My hacky workaround was to add the version to the Gemfile, bundle update rails, remove the version from Gemfile, then bundle update rails again (to remove the hardcoded version in the lockfile).

Yuck.

Re:Rails 3.2.13, 3.1.12, and 2.3.18 have been released by kawsper on Monday March 18, 2013 @10:49PM (#5398607)
Doesn't the gem command obey your Gemfile.lock? If your Gemfile.lock mandates an old version, it would install that.