Hi, everybody! This is Tim and Claudio reporting here from sunny Los Angeles. It’s been a week of intense weather here, and even more intense activity in the Rails community. Let’s take a look at the highlights…
The new versions are backward compatible, so if you are using any 4.2.x version, you can safely upgrade to 4.2.4. And if you are using 4.1.x, bump your Gemfile to 4.1.13.
This week 47 awesome people helped to make Rails even better, including 3 for the first time. If you are interested in becoming a contributor, you can have a look at the issues list.
Do you need to create asynchronous jobs without installing additional gems? Set
config.active_job.queue_adapter = :async and post your jobs to a concurrent-ruby thread pool.
params.require can now take multiple values as an array, allowing for more succinct code such as
In Rack 2, the
env hash will be changed to be actual request and response objects. This commit paves the way for Rails to be compatible when Rack 2 is released.
Pull requests that improve the performance of Rails are always welcome, especially when they come with benchmarks showing a speed increase of 9x!
RFC 7231 changed the list of HTTP status codes (dropping “418 I’m a Teapot” among others). Rails documentation has now been fixed to list the symbols that can be used to represent status codes.
One last thing that deserves a mention is that the new Code of Conduct has gone live on the main website. Hurrah!
That’s all for This week in Rails. As always, there are many more changes than we have room to cover here, but feel free to check them out yourself!
Have you been thinking about writing for us, but you’re scared of putting yourself out there? Don’t worry, you can help our editors improve their writing with thoughtful critique and general grammar policing.
You up for that? Tell Godfrey today.