Hop aboard fellow traveler! Here’s your friendly conductor Kasper revving up to give you a brand spanking new issue for the price of zilch.
We’re just about to roll into RailsConf proper. Several of your trusty editors are going including me, Eugene, Tim, and Vipul! Many people who are Rails committers and core will be there too. Feel free to say hi if you spot us — we don’t byte a bit 😄
Rails 6 is almost out the door. The first release candidate came out this week. This is the best time to get bug fixes in because we on the Rails core team will prioritize bugs found in rc1 and then ship an rc2 shortly. If no bugs are found after roughly 2-3 weeks, the real 6.0.0 is cut.
Now that 6.0.0.rc1 is out Rails 6.1 development has started too. And the first feature has already landed! Active Model validations has long had errors that were plain hashes, but in 6.1 they’ll be objects!
Rails 6’s new autoloader Zeitwerk got a new command to check if your app is compatible. Simply run bin/rails zeitwerk:check and it’ll print out potential problems.
One of the benefits of GitHub being on the latest Rails was seen this week as they could test 6.0. GitHub found a potential regression in Active Job rectified it. The fix is Le Git!
Due to some nifty code rearrangement accessing attributes of an Active Record model became 10% faster albeit with a slight maintenance cost. An additional 20% speed boost on id was also squeezed in.
34 people contributed to Rails in the last week. You can see the full list of changes here.
Until next time!