Rails Changelog
What's new in Rails 3.1.3
Nov 28, 2011- Action Pack:
- Downgrade sprockets to ~> 2.0.3. Using 2.1.0 caused regressions.
- Fix using translate helper with a html translation which uses the :count option for pluralization.
- Active Record:
- Perf fix: If we're deleting all records in an association, don't add a IN(..) clause to the query. GH 3672
- Fix bug with referencing other mysql databases in settablename. GH 3690
- Fix performance bug with mysql databases on a server with lots of other databses. GH 3678
- Railties:
- New apps should be generated with a sass-rails dependency of 3.1.5, not 3.1.5.rc.2
New in Rails 3.0 Beta (Feb 6, 2010)
- Brand new router with an emphasis on RESTful declarations
- New Action Mailer API modelled after Action Controller (now without the agonizing pain of sending multipart messages!)
- New Active Record chainable query language built on top of relational algebra
- Unobtrusive JavaScript helpers with drivers for Prototype, jQuery, and more coming (end of inline JS)
- Explicit dependency management with Bundler
New in Rails 2.3.5 (Dec 11, 2009)
- Rails 2.3.5 was released over the weekend which provides several bug-fixes and one security fix. It should be fully compatible with all prior 2.3.x releases and can be easily upgraded to with “gem update rails”. The most interesting bits can be summarized in three points.
- Improved compatibility with Ruby 1.9:
- There were a few small bugs preventing full compatibility with Ruby 1.9. However, we wouldn’t be surprised you were already running Rails 2.3.X successfully before these bugs were fixed (they were small).
- RailsXss plugin availability:
- As you may have heard, in Rails 3 we are now automatically escaping all string content in erb (where as before you needed to use “h()” to escape). If you want to have this functionality today you can install Koz’s RailsXss plugin in Rails 2.3.5.
- Fixes for the Nokogiri backend for XmlMini:
- With Rails 2.3 we were given the ability to switch out the default XML parser from REXML to other faster parsers like Nokogiri. There were a few issues with using Nokogiri which are now resolved, so if your application is parsing lots of xml you may want to switch to this faster XML parser.