Fix 2.3.2 tag?

This wreaked havoc for me in production. Without those Rack commits in there, all POSTed params were getting blanked out by Rails.

Please fix ASAP so others don't have to suffer.

The major problem is that the .tar.gz archive on dev.rubyonrails.org appears to use the tag to create the archive, so it's inconsistent with the gem release. As it now, the archive release contains the nasty bug described above since it doesn't include Rack 1.0.

Yes, the Rubyforge version is correct.

What isn't correct is this version:

http://dev.rubyonrails.org/archi...

Which is what is called when doing:

rake rails:freeze:edge RELEASE=2.3.2

from a Rails app.

I'm not sure about RubyForge, but github looks wrong to me.

This tag:

http://github.com/rails/rails/co...

...doesn't include some commits:

http://github.com/rails/rails/co...

...that I've been lead to believe:

http://rails.lighthouseapp.com/p...

...are included in the gem, but not the tagged version.

I'm not sure what impact having the tag on github not match the gem. I'm reporting it because I'm used to being able to freeze my production apps to a tag and/or a stable branch.

Right, we know that Github tag doesn't match the gem, and the impact this has on freezing edge. Those issues will be corrected soonish. Just wanted to confirm that there wasn't yet another copy floating around somewhere.

Until then, use the gem or grab edge straight from GitHub.

That's great - thanks very much for the quick fix!