Hey there, news attenuated people of planet Rails! It’s your trusty prudent editor / local dimwit Kasper here with This Week in Rails. As always we both cover and cower at the highlight reel of Rails’ past week.
Lets slow our roll a bit to pursue what’s meaningful not merely what’s expedient!
This week came the release candidate of the next Rails release. Bundle it, run your tests, boot a server — maybe even try it a bit in production. That’ll really help ensure 5.2.0 is solid gold.
If you’re not 5.2 ready yet, Rails 5.1.5.rc1 is also ready to test.
29 contributors crossed the tangled weave of the web this week to get their commits lobbed straight on to Rails’ master branch. That master branch, by the way, is now targeting Rails 6.0.
Rails 5.2 ships with a DSL to declare Content Security Policies. The default policy interfered with Rails’ UJS and required some extra that the team didn’t have time for to do now. So the aim is to have a default security policy in place for Rails 6.0.
Loading and dumping marshaled Active Record instances is now back to the speeds they were at in Rails 4.2. Peachy keen.
Apache X-Request-Id headers can contain @-signs. While I don’t wanna speak out of school, I do feel quite comfortable yelling: WHY SHOULD THEY HAVE ALL THE FUN! So now we can flaunt that ability too. don’t @ me, though.
That’s it for this week. Many more changes were introduced to Rails than were featured here, check out the full week of commit activity to learn more!
Until next time!