And now a Rails 🌩 News Flash 🌩! (Hint: we've got some big news this week, if you hadn't heard). We take you now, live, to our reporter on the scene, Tim, for all the latest and greatest this week.
5.2.0 is officially among us, a little bit ahead of RailsConf this year. If you can't wait until then to find out everything that this new release brings, do go read the original blog post that accompanied the release for all the details!

48 people contributed to Rails in the last two weeks, including an incredible 11 for the first time! A big thank you to all of you!

If you'd like to see yourself on that board, why not check out the list of open issues, or get involved in the core discussion list.
Though you may not need all these headers, there are specific instances where you may want them to enhance security, so it makes sense to have this configured on by default.

This nice little optimization eliminated some array allocations, that you may benefit from if you have a large number of connection pools.

By asking the mutation tracker for the list of changed attributes, some work can be skipped when generating the changes hash. This may be most noticeable for serialized attributes, for which calling #original_value can be significantly more expensive.

A regression was found whereby compressed items in the cache store were taking up more space than their original, uncompressed versions. That is now fixed thanks to the great detective work shown in this PR!
Wrapping Up
As always there were many more changes to the Rails codebase than we can cover here. But you can read all about them here! Until next week!
This Week in Rails · 30 N Racine #200 · Chicago IL 60607 · USA
Unsubscribe | View in browser