Rails 6.0.0 beta1: Action Mailbox, Action Text, Multiple DBs, Parallel Testing, Webpacker by default

The first beta release of Rails 6 is here! It’s absolutely packed with amazing new stuff that we’re so excited to share. There are two major new frameworks – Action Mailbox and Action Text – and two important scalable-by-default upgrades in great multiple database support and parallel testing.

Action Mailbox routes incoming emails to controller-like mailboxes for processing in Rails. It ships with ingresses for Amazon SES, Mailgun, Mandrill, Postmark, and SendGrid. You can also handle inbound mails directly via the built-in Exim, Postfix, and Qmail ingresses. The foundational work on Action Mailbox was done by George Claghorn and yours truly.

Action Text brings rich text content and editing to Rails. It includes the Trix editor that handles everything from formatting to links to quotes to lists to embedded images and galleries. The rich text content generated by the Trix editor is saved in its own RichText model that’s associated with any existing Active Record model in the application. Any embedded images (or other attachments) are automatically stored using Active Storage and associated with the included RichText model. The foundational work on Action Text was done by Sam Stephenson, Javan Makhmali, and yours truly.

The new multiple database support makes it easy for a single application to connect to, well, multiple databases at the same time! You can either do this because you want to segment certain records into their own databases for scaling or isolation, or because you’re doing read/write splitting with replica databases for performance. Either way, there’s a new, simple API for making that happen without reaching inside the bowels of Active Record. The foundational work for multiple-database support was done by Eileen Uchitelle and Aaron Patterson.

With parallel testing support, you can finally take advantage of all those cores in your machine to run big test suites faster. Each testing worker gets its own database and runs in its own thread, so you’re not pegging one CPU to 100% while the other 9 sit idle by (y’all do have a 10-core iMac Pro, right 😂). Hurray! The foundational work for parallel-testing support was done by Eileen Uchitelle and Aaron Patterson.

Webpacker is now the default JavaScript bundler for Rails through the new app/javascript directory. We’re still using the asset pipeline with Sprockets for CSS and static assets, though. The two integrate very nicely and offer the best trade-off of advanced JavaScript features with an it-just-works approach to other assets.

Those are just some of the marque additions, but Rails 6.0 is also packed with minor changes, fixes, and upgrades. Just some I’d call out: Proper Action Cable testing, Action Cable JavaScript rewritten in ES6, protection against DNS rebinding attacks, and per-environment credentials. Also, Rails 6 will require Ruby 2.5.0+ now. You can check out everything in the individual framework CHANGELOG files for the nitty-gritty rundown.

Finally, you should pay attention to Xavier Noria’s new Zeitwerk code loader for Ruby. It didn’t make the integration cut for beta1, but starting with beta2, it’ll be the new autoloader for Rails. Be prepared to say goodbye to any lingering require or require_dependency calls in your code!

We are still roughly on track with our published timeline for the final Rails 6.0 release, so consult that plan for your migration planning, but please do help us already by testing your application on beta1! I’d also encourage anyone with a moderate level of Rails experience to start any new app using beta1, rather than the Rails 5.2.x series. Basecamp is already running Rails 6.0.0.beta1 in production, and both Shopify and GitHub and surely others will follow close thereafter. This isn’t some rickety-shack release.

This release, and all releases leading up to Rails 6.0 final, was shepherded by release manager Rafael França with support by Kasper Timm Hansen.

Thanks again to everyone who keeps working on making Rails better! It’s incredible that we’re still able to keep this intense rate of improvement going after all these years. Rails has never been in fitter shape to help the broadest number of web developers build excellent apps in a way they love. Let joy be sparked!

Timeline for the release of Rails 6.0

We’ve made enough progress towards the vision for Rails 6.0 that it makes sense to share our aspirational timeline for release. “Aspirational” being the key word, more so than “release” 😄. Software rarely ships on time, and we’ve had plenty of aspirational release dates that came and went in the past. But if optimism isn’t part of the fun of open source, then where would we be?

So. This is the timeline as we currently hope to see it:

  • January 15: Beta 1. We’ll merge the two new frameworks, Action Mailbox and Action Text, for this release.
  • February 1: Beta 2. We’ll make sure any other major improvements are included by then.
  • March 1: Release Candidate 1. We go feature complete by here.
  • April 1: Release Candidate 2. This should really be ready to ship, only new blockers will hold us back.
  • April 30: Final release. Ship and celebrate the release of Rails 6.0 at RailsConf 2019!

It always looks so nice and neat when laid out like that, right? Like some serious engineers did some serious engineering to figure this out. And not just a bunch of software writers plotting down their hopes and dreams. But yeah, it’s really the engineering part we went for (no it wasn’t).

Worth noting: Rails 6.0 will require Ruby 2.5+! So you can get ready by making sure you’re already running this version of Ruby. Also note that following the release of Rails 6.0, only Rails 6.x.y and Rails 5.2.x are guaranteed to receive both major and minor security fixes by Rails core. (As always, we may still choose to provide fixes further back, but there’s no guarantee).

As always, please help us make this a reality by running rails/master for new apps and existing ones, if you sport that High Adventure gene (aka no risk of getting fired if you hit a bug). Basecamp 3 is already running rails/master in production, so you know the main branch is at least in pretty good working order!

Our release manager for Rails 6.0 will be Rafael França with backup from Kasper Timm Hansen 🙏

To Rails Six Oh And Beyond! 🚀🚂

George joins Rails Core and Action Mailbox introduced

Hello. This is Wojtek with a short list of news from Rails world.

George joins Rails Core

George Claghorn is now a member of the Rails core team. Welcome George!

Introducing Action Mailbox for Rails 6

Action Mailbox is the brand new framework coming to Rails 6 extracted from Basecamp.

Add ActiveRecord::Base.connected_to?

Another handy method added to support multiple databases.

Fix numericality equality validation on floats

By casting values to BigDecimal comparision on validation is now more precise.

19 people contributed to Rails last week making lot of improvements.
Until next time!

Introducing Action Mailbox for Rails 6

Action Mailbox is the second brand new framework coming to Rails 6 (the first was Action Text). It serves to route incoming emails to controller-like mailboxes for processing in Rails. It ships with ingresses for Amazon SES, Mailgun, Mandrill, and SendGrid. You can also handle inbound mails directly via the Postfix ingress.

The inbound emails are turned into InboundEmail records using Active Record and feature lifecycle tracking, storage of the original email on cloud storage via Active Storage, and responsible data handling with on-by-default incineration. These inbound emails are routed asynchronously using Active Job to one or several dedicated mailboxes, which are capable of interacting directly with the rest of your domain model.

The framework was, like Action Text and Active Storage, extracted from Basecamp 3. We’ve been using a related approach to route everything from forwarded emails to email replies to messages and discussions. After extracting the ideas into Action Mailbox, we reintegrated the framework into Basecamp, and we’ve been running the code we’re sharing today for over a month in production.

Yes, Rails already had an anemic way of receiving emails using Action Mailer, but it was poorly flushed out, lacked cohesion with the task of sending emails, and offered no help on integrating with popular inbound email processing platforms. Action Mailbox supersedes the receiving part of Action Mailer, which will be deprecated in due course.

Rails 6 is getting closer, but it’s still a ways off – we’re hoping to start the beta process in early 2019. Action Mailbox is already in pretty decent shape, though, and you can even use it with Rails 5.2 applications, if you fancy dancing on the wild side. Just be prepared for things changing as we work our way through community review and towards merging it into rails/rails.

The Action Mailbox framework is based off ideas hatched by Jeremy Daer, and this particular implementation was done as a collaboration between yours truly and George Claghorn.

As part of the introduction of Action Mailbox, I plan to record a video showing off the basics in the near future. But the code is ready and somewhat documented for anyone to dive into already. So why sit on a good thing!

Between Action Text and Action Mailbox, Rails 6 is already shaping up to be one of the biggest releases in the history of the framework. And we’re not even done yet! Our plan is tentatively to have a release candidate version ready for RailsConf 2019 in Minneapolis. Please help us make that promise a reality by trying out Action Mailbox!

New Rails version, early new Ruby version fixes, and more!

Hello, hello! This is Tim here bringing you all the latest right from the Rails Edge.

In the northern hemisphere, daylight is getting scarce, driving certain folks in the Pacific Northwest to drastic measures. But the holiday season is upon us! We got an early pressie in the form of a new Rails release this week. Ans we can all look forward to Ruby release day!

On with the show….

Rails 5.2.2 has been released!

This week saw the release of a new patch version of Rails! Too numerous to list here, check out the official blog post for the full changelog.

This Week’s Contributors

This week 23 people gave back to Rails. For 7 of these folks it was their first time contributing! If you’d like to see yourself in a future edition of this newsletter, or alternatively just want to give back in a purely altruistic gesture, a great place to start can be checking out the list of open issues.

Ruby 2.6.0 fixes

As you may know, the release of Ruby 2.6.0 is right around the corner! We are very grateful to the folks who are already testing Rails on the release candidates and submitting patches ahead of time.

Non-primary mouse button clicks no longer trigger click events

This PR addresses an issue where certain browsers will fire a click event for non-primary mouse button clicks where others will not. They will all now behave uniformly thanks to this fix!

Unpermitted params log message now colorized

More colorized log messages for improved readability!

#delete_all on collection proxy returns count

This makes #delete_all behave uniformly across relations and collection proxies by returning the count of affected rows.

Test helpers docs added to guides

This PR documents some good practices for breaking test helpers out into separate files. Check it out!

ActiveJob::Base#enqueue to return false on failure

This makes the enqueue mechanism more consistent with the ActiveSupport::Callbacks design where if the callback chain is halted, it will return false. You can now use this feedback to determine if your job was in fact enqueued. Hurrah!

As always, there were way too many things to cover in full this week, but you can read about them all here. That’s all folks!

Rails 5.2.2 has been released!

Hi everyone,

I am happy to announce that Rails 5.2.2 has been released.

CHANGES since 5.2.1

To view the changes for each gem, please read the changelogs on GitHub:

To see a summary of changes, please read the release on GitHub:


Full listing

To see the full list of changes, check out all the commits on GitHub.


If you’d like to verify that your gem is the same as the one I’ve uploaded, please use these SHA-256 hashes.

Here are the checksums for 5.2.2:

$ shasum -a 256 *-5.2.2.gem
1d996c7e148dfb9f0587ca520022263f0db0a34ac6f7997d7203500059994620  actioncable-5.2.2.gem
b6e028994d5fabc71977d3d6ca34a52597921162e2fae5d3bdb3b292345ad769  actionmailer-5.2.2.gem
9a73648c98e8b322c72c97f2efe7989832ef18c23c0202704ba33260315e9047  actionpack-5.2.2.gem
1fe90c7eec75f8833b5459099069a40514b72e09d94ab436ece087b87223e0d3  actionview-5.2.2.gem
390a81080e800691131d0f26943216790bc40404f5e6d44b79f92ad185a153ca  activejob-5.2.2.gem
71777d3482c10b3531bcf192a6db624c963c541667c2b9e5829a3cc4eb88bcf6  activemodel-5.2.2.gem
1e8c0fabfd6618e167d125d8d074a1392f4a760b8b16513d179f1765b4d540a5  activerecord-5.2.2.gem
615cc276b090dc96b8367345cb35e97ce073c5cab599b9091a5ca304ce40e230  activestorage-5.2.2.gem
ff393e485ba5e9bad8b8f1d7b89b2addd697420f9faca3c9c9da778efb3ecac7  activesupport-5.2.2.gem
d9ff5d9be16ee277dfc8f3c760bf171aa497d8685ec5c8988fba21a3dbd72cd5  rails-5.2.2.gem
34648d2794966bd330681706edcc73cdd234208a1dd2c27b358491bf2af5f602  railties-5.2.2.gem

As always, huge thanks to the many contributors who helped with this release.

Safety checks to prevent database writes, cache performance boost and more

Cheers for the first day of December! This is Kir bringing you the latest news from the Rails world.

Use raw time string from DB to generate ActiveRecord#cache_version

The PR skips unnecessary attribute casting when generating cache version, which gives a great performance boost for apps that rely on caching.

Add ability to block writes to a database

A brand new while_preventing_writes method on Active Record connection allows you to add safety checks for code that’s not supposed to write to a database.

Bump the minimum version of PostgreSQL to 9.3

PostgreSQL 9.1 and 9.2 have been declared EOL more than a year ago.

28 peoplecontributed to Rails last week. If you want to be part of that, check out the issues list.
Until next time!

Rails 5.2.2.rc1 has been released

Hi everyone,

I am happy to announce that Rails 5.2.2.rc1 has been released.

If no regressions are found, expect the final release on Monday, December 3, 2018. If you find one, please open an issue on GitHub and mention me (@rafaelfranca) on it, so that we can fix it before the final release.

CHANGES since 5.2.1

To view the changes for each gem, please read the changelogs on GitHub:

Full listing

To see the full list of changes, check out all the commits on GitHub.


If you’d like to verify that your gem is the same as the one I’ve uploaded, please use these SHA-256 hashes.

Here are the checksums for 5.2.2.rc1:

$ shasum -a 256 *-5.2.2.rc1.gem
c412268c40fc61c16480952c801261d4901c2b0ca81518c6b8ed1c619e38cbe4  actioncable-5.2.2.rc1.gem
33dcd916c7097823a598e02ee27af657f452c9e1ca5b56d5e8d33871870e84d5  actionmailer-5.2.2.rc1.gem
ad0178b8e4115eb7b6447f536c24f7725a6022a615a0d9dca1fca055856a6bba  actionpack-5.2.2.rc1.gem
f0202029b41eeda234e52136191604a52adda23445722172ec2398efe830efd1  actionview-5.2.2.rc1.gem
56102eeb75e9a29d400a648334f2f7e16f21948a608abd448c4663235752a7ea  activejob-5.2.2.rc1.gem
cca50c361514be3e901b695cece93ae5230a9018305d336b683fd35a1e97832e  activemodel-5.2.2.rc1.gem
7bded9a0bfe31eca3df543e59945cf16e3d0d1b32908d879fa1f9469a9cbd3e3  activerecord-5.2.2.rc1.gem
5cd7d2938d615637201326083edcb5b832254dec3a64638440777c34f1ad030c  activestorage-5.2.2.rc1.gem
bcd01d80cd4863368d3c3c8914527170b488b354611eeecd6e57553019c776ef  activesupport-5.2.2.rc1.gem
8e1fdbabab9eae02fc76078eea1dc1d975a9be8cbcfeda4395137503da3f1bf7  rails-5.2.2.rc1.gem
1d9950a611acb8fef50ba1477efa3e4730d713db55f834bdccd12fd950f2de51  railties-5.2.2.rc1.gem

As always, huge thanks to the many contributors who helped with this release.

Rails 4.2.11,, and have been released!

Hello everyone and happy Tuesday!

Rails 4.2.11,, and have been released! These contain the following important security fixes, and it is recommended that users upgrade as soon as possible:

RAils also includes the following security fix:

The released versions can be found in the usual locations, and you can find a list of changes on GitHub:

We’ve done our best to minimize any impact to your applications, but if you run in to any issues, please file a ticket and we’ll do our best to help!

Again, as always, if you run in to any bugs, please file them on the Rails issue tracker which is located here. If you run in to security issues, please follow the reporting process which can be found here.


If you’d like to verify that your gem is the same as the one I’ve uploaded, please use these SHA-256 hashes.

$ shasum -a 256 *4.2.11.gem*
951c7ddd998b25f51ac01e3da5b552acb4341af325bb744b6d1b567fa0a6737e  actionmailer-4.2.11.gem
f97004512791f29220b08e0fb3394fa6235049d48a043f490552bee3078db38f  actionpack-4.2.11.gem
8bb47c377295f91a685afb993d78d5a628b3afa04739047bd71af6fe3ac07c27  actionview-4.2.11.gem
d35b4027c2a07f6637a480db50da7576dc11239c59cb66b805e253e284d0d88b  activejob-4.2.11.gem
b89604b0252e1b5eea47de4c5e3ff4b3d713c3c5ab3802c87a37b0e296da5885  activemodel-4.2.11.gem
258e61c64256c024d703d90d259dd183b526a10083eda518c94b2bcb52a880eb  activerecord-4.2.11.gem
c49aa608ef07ae6164211b4208292386947c58b925aeb3157a746f587911195f  activesupport-4.2.11.gem
dd12ffea8f548accec41ae1ef6add3cf9f1e00275744f92da60a713a0b0d1766  rails-4.2.11.gem
2186005ddf9e48fcbc98bb37c8bf127d0681826938cb053c896e03dde717a327  railties-4.2.11.gem
$ shasum -a 256 **
2befb790e89ca0573f2f25d7458aee45aff694a4a9b3ee2049ec7b13a8628390  actioncable-
1556a928f279ede0a98b41f5bd44b641d5a966acf50e93916619048a9e2fef1c  actionmailer-
3cd3bd78fd02ab186da87b8c331dda4dc74904a5aa40b2d834347c65037fc3fe  actionpack-
41258b51f5ac18bc55e77442eb93bde161781fbff7c45d913a0bfb45530e7f14  actionview-
9b1e8f49b09d3aa28c0c7ad3eae0bf7deecbc03c557d49fd4c49159ff0d53971  activejob-
0ce4d73d02392f835b11c138dc61af36388663fc9636313d055d90621f4500c5  activemodel-
8c1cd39637c8810d8fac7948a9dacf06075e6007b39400d48f34abb4db3e6ae3  activerecord-
eba9b4423a433535f7ddf320a0d1590695a24b69b9525bea5f32fe3d2babb609  activesupport-
3ce11ed1acf1eea4b4b35b4516251e81a5cbbd889227432b232409cb9c658a2e  rails-
d92aaa635282faad3feb3aab75ea34587f05f142dc65e02044b253e56414d0b1  railties-
$ shasum -a 256 **
3f011a9732531f6e00f213910a66b5d1ec5f9c8cd0b208c32ed9a014008e517f  actioncable-
e89c2f24e1fb82b16927c9c7140a09d405e54d35ebb964c4a199843683559d29  actionmailer-
3e3875f18e1548e413f5a48d695e6e77646f5b687d9d4e149c75285c1ece26a7  actionpack-
5783dc24973b15cb33e48341b268c6b3ad2e5750f536d36eb9d489274846dc1c  actionview-
8875a51226f5a4f75ba2be209c0b801bae602d1f9471db495b0a67f10e8158e7  activejob-
00ccdcd6003c11640e813d8511ad7362ad823e0db95637bf2239f1e1196489d8  activemodel-
4946ae8a770d9a58fecfa16791769dff6e837c8e8970a04b9c2854d584580947  activerecord-
fa78e56360106d5e508818a4f0b5d234ea1f2183c755134b6276aba1101c3831  activesupport-
f64f110ff439f10616e87e35dee23aeb0932e77869c64b3e2239b1332db5c863  rails-
ac32ff49acd522522bbb87cc69d37a448e6e856b72bccee098c80a0d565d2640  railties-
$ shasum -a 256 **
8dc3251fb9dc898a693243d0f5488ef5bbfaefc92c2fd744db4554b0b739ce9c  actioncable-
f932baa262e1309ee0a4b5784e63a91cc9808a68fa3475f4469718c80d6a9d5f  actionmailer-
731c5a5b31811d530623f4bf35aade7a9bc7b76da72a006a4eedd2359efb62b3  actionpack-
9c449f59f03890dceb8bb05f53c2b6b331a37180258a605e27e48982114feebb  actionview-
b9bbb83cc41e2bff53f6cc1f5a57c6edcefca0e63084621bcad43c6aca37edfc  activejob-
c2627b30d7be62d3849943e86e1df34d2275f75e4f478b550ce77d84c3f61a96  activemodel-
46b27c575c9e2c6810c2b9223f0034b54e9d061c2b8c72f3dd4226947debee58  activerecord-
451b837320e6c2da51974d1b844d120718c726b5e13e905b0ba83e2759991c92  activestorage-
6e055f81d0ec158475faed1bb4e00c8030b67ecc2b7aee83be24c995a5d1a1dc  activesupport-
b5e1fe216d108d6908e23aaaed563dcf8fae7ec92c4ea776607732785bad8f10  rails-
1030556e9bb07d192429659cbe5561339bbe845f9d78194a34bbc040653c7685  railties-