7 ms·

Looks like the Rails 3.2 update drags along a few other unrelated changes, although they appear to be fairly minor: https://github.com/rails/rails/compare/v3.2.

• jerhinesmith 12y ago
  You'd have thought they'd stop doing that after the Github email embarrassment: https://github.com/blog/1440-github-enterprise-email-incident-today https://github.com/blog/1440-github-enterprise-email-inciden...
• bensedat 12y ago
  If you're applying a patch manually to Rails 4.0/4.1, there was a regression and new versions have been issued: https://groups.google.com/forum/#!topic/rubyonrails-security/8GtfeYd6qI4 https://groups.google.com/forum/#!topic/rubyonrails-security...
• thibaut_barrere 12y ago
  I use this now to make sure I review before updating: https://gist.github.com/thbar/7dc97d3f5f6a52e4fa00 https://gist.github.com/thbar/7dc97d3f5f6a52e4fa00 (obviously not to be used in a CI environment). Also, if you want to make sure you get push notification for security updates, check out this: http://thibautbarrere.com/how-to-get-push-notifications-for-rails-ruby-security-updates/ http://thibautbarrere.com/how-to-get-push-notifications-for-... (I get only critical stuff as pushes, and get notified even in the rare case that the rails security email goes to spam as it happened once previously).