Ruby on Rails: The Great Ractor Hardening
A wave of Rails pull requests converted class-level configuration across Active Record, Action Pack, and Action View into shareable, instance-based state to make apps boot and run safely under Ractors, while a smaller set of fixes addressed connection leaks and data ordering bugs.
Duration: PT2M55S
Episode overview
This episode is a short developer briefing from Ruby on Rails.
It explains recent repository work in plain language.
- Show: Ruby on Rails
- Published: 2026-09-03T13:14:35Z
- Audio duration: PT2M55S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's September 3rd, and today's Rails activity has one dominant theme: getting the framework ready for Ractors.
The top pattern here is a coordinated push to make Rails configuration Ractor-safe. Multiple PRs from Etienne Barrie and Edouard-chin converted long-standing class variables and mutable settings into instance variables or frozen, shareable state. PR 58627 changed Action Pack settings like mime negotiation to…
A second, smaller theme is connection and data-integrity correctness. PR 58645 fixed Type Caster leaking a database connection by switching to with-connection instead of relying on executor cleanup. That fix is directly linked to PR 58648, which addresses Live actions running outside the application executor on the…
What's next: watch for more Ractor-safety patches landing quickly after merges, since this feed already shows two same-day follow-ups. Also worth tracking PR 58638, which lets you configure PostgreSQL error verbosity to keep sensitive data out of exception messages and logs.
That's the briefing for September 3rd. Back tomorrow with more from the Rails codebase.
Nearby episodes from Ruby on Rails
- Ractors Get Real, and a Data Integrity Bug Surfaces Three Times
- Trimming the Fat—A Day of Performance and Correctness Fixes
- When Data Gets Serialized Twice
- Weekly Recap - Concurrency Safety and Cache Store Cleanup
- Quiet Data, Loud Fixes
- Keeping Pace With Upstream Dependencies
- Fiber Isolation Takes Center Stage
- Chasing Down Regressions