$ the-wire · showcase
RAILS UNLOCKS RACTOR THREADING WITH SHAREABLE LOGGER AND PROXY LOGGER MERGES
By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology
Rails shipped three major concurrency features that let you safely pass loggers across Ractor boundaries, a critical step toward multi-threaded Rails applications.
The most significant work landed in rails/rails: a new ActiveSupport::ShareableLogger [1] that wraps TaggedLogging and can be safely shared across Ractors, plus an ActiveSupport::ProxyLogger [2] that lets you route library logs to your app logger with independent severity levels. Both solve the hard problem of thread-safe logging in Ractor-enabled code. Template handler registries also went Ractor-shareable [3], removing a critical blocker for rendering views in background threads. On the ops side, rails/spring tightened CI by pushing Dependabot automation for GitHub Actions [4], and rails/devcontainer picked up Ruby 3.4.10 [5]. Rails World 2026 now has Arely Rivera confirmed as co-presenter [6], and the website updated the Basecamp logo [7].
Action items
- → Review the ShareableLogger and ProxyLogger implementations if you're using Ractors in production or planning to rails/rails [plan]
- → Update devcontainer to Ruby 3.4.10 if you're shipping new Rails projects rails/devcontainer [monitor]
- → Merge Dependabot GitHub Actions updates on your fork of rails/spring if you maintain it rails/spring [plan]
References
- [1] Add a Ractor-shareable ActiveSupport::TaggedLogging.shareable_logger ↗ rails/rails
- [2] Implement ActiveSupport::ProxyLogger ↗ rails/rails
- [3] Make the Action View template handler registry Ractor-shareable ↗ rails/rails
- [4] CI: Tell dependabot to update GH Actions ↗ rails/spring
- [5] Add Ruby version: 3.4.10 ↗ rails/devcontainer
- [6] Add Arely Rivera as Rails World 2026 speaker ↗ rails/website
- [7] Update the Basecamp logo ↗ rails/website
