Who contributed to Rails on July 7, 2026?

3 developers shipped this update, including andrewn617, Edouard-chin, and dependabot[bot].

What were the notable Rails updates?

Introduce ractorize, Deprecate the ActionController::Renderer::RENDERERS constant:, and Allow the DeprecatedObjectProxy to change target after initialization:.

Jul 7, 2026

$ the-wire · showcase

RAILS GOES RACTOR-SAFE WITH NEW APPLICATION SHAREABLE MODE

By RepoJournal · Filed 06:00 UTC on July 7, 2026 · About Rails · Composed from the cited sources · methodology

3 people shipped this

dependabot[bot] @dependabot[bot] 4 cited

andrewn617 @andrewn617 1 cited

Edouard-chin @Edouard-chin 1 cited

Rails is shipping the foundational work to make applications Ractor-safe, with a new `ractorize!` method that prepares your entire app for multi-threaded concurrency without the GIL.

The framework is systematically eliminating mutation patterns that block Ractor compatibility. The biggest move: a new `Rails::Application#ractorize!` method [1] that makes your app shareable across Ractor boundaries, though it comes with real constraints for now (eager loading required, no Action Cable, null cache). Three complementary commits land simultaneously to support this: deprecating the ActionController::Renderer::RENDERERS constant [2], allowing deprecated object proxies to change targets post-initialization [3], and stopping mutation of the renderers set itself [4]. This is the infrastructure layer. You're not forced to use Ractor yet, but if you've been waiting for framework-level support, this is it. The work also makes ActionController renderers Ractor-safe [5] by eliminating the object mutations that were blocking the entire pattern. Secondary updates across the ecosystem: Thor bumped its GitHub Actions dependencies [6] [7], concurrent-ruby shipped three security fixes [8], and Tailwind CSS updated to 4.3.1 [9].

Action items

→ Review Ractor constraints in your app (eager loading, caching strategy, Action Cable usage) rails/rails [plan]
→ Audit ActionController::Renderer::RENDERERS usage if you've added custom renderers rails/rails [plan]
→ Bump concurrent-ruby to 1.3.7 for security fixes rails/rails-html-sanitizer [monitor]

References

[1] Introduce ractorize ↗ rails/rails
[2] Deprecate the ActionController::Renderer::RENDERERS constant: rails/rails ↗
[3] Allow the DeprecatedObjectProxy to change target after initialization: rails/rails ↗
[4] Stop mutating ActionController Renderers: rails/rails ↗
[5] Make ActionController Renderers ractor safe ↗ rails/rails
[6] Bump rubygems/configure-rubygems-credentials from 2.0.0 to 2.1.0 ↗ rails/thor
[7] Bump actions/checkout from 6 to 7 ↗ rails/thor
[8] build(deps-dev): bump concurrent-ruby from 1.3.6 to 1.3.7 ↗ rails/rails-html-sanitizer
[9] build(deps): bump tailwindcss-ruby from 4.3.0 to 4.3.1 ↗ rails/tailwindcss-rails