Top

A Fresh Cup is Mike Gunderloy's software development weblog, covering Ruby on Rails and whatever else I find interesting in the universe of software. I'm a full-time Rails developer and contributor, available for long- or short-term consulting, with solid experience in working as part of a distributed team. If you'd like to hire me, drop me a line. I'm also the author of Rails Rescue Handbook and Rails Freelancing Handbook.


Navigation
« Double Shot #412 | Main | Double Shot #411 »
Wednesday
18Mar2009

Rails 2.3.2.1

DateWednesday, March 18, 2009 at 6:49AM
Rails 2.3.2.1 is out. There's some confusion about this floating around already, so here's the scoop as I understand it:

  • The original Rails 2.3.2 gems were built including this commit from the Rails master tree, which is critical for proper functionality.

  • The 2.3.2 tag in GitHub unfortunately points to this commit, which is before the critical fix.

  • The net result is that rake rails:freeze:edge RELEASE=2.3.2 would freeze a bad version of Rails into your application.


To fix this, the Rails team has re-tagged the master tree at a safer spot, after the critical fix. This new tag is for release 2.3.2.1. So if you're freezing Rails 2.3 into your applications (as opposed to running it from gems) be sure to use rake rails:freeze:edge RELEASE=2.3.2.1. That .1 makes all the difference.
AuthorMike Gunderloy | Comment3 Comments |
in

Reader Comments (3)

Hi, yes I think this is a pretty big problem and the Rails core team's general silence about it coupled with a confusing solution has not been much help.

The actual problem at the original tag is that the installed Rack gem (0.9.1 I think) was taking precedence over the bundled one (1.0!) and causing nested parameters to flatten out so none of your update actions work anymore.

Andrew

March 18, 2009 | Unregistered CommenterAndrew France

Thanks for the tip. I was trying all sorts of different arguments to RELEASE (2.3, 2.3.0, etc...) and it was not working. Much appreciated!

March 19, 2009 | Unregistered CommenterJoe

[...] be careful if using rake rails:freeze:gems. You can read more about it in the official post or in this post which I found more [...]

May 4, 2009 | Unregistered CommenterUpgrading from Rails 2.2.2 to

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>