Ruby on Rails: Ractor Safety and the Great Insert Cleanup
Today's merges cluster around making Rails safe to run across multiple Ractors and around simplifying how database inserts return primary keys, alongside a handful of correctness fixes in template rendering and encryption. No single change is release-critical on its own, but together they reduce risk in concurrency and database-adapter code paths.
Duration: PT2M42S
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-07-29T13:13:08Z
- Audio duration: PT2M42S
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 July 29th, and today's Rails activity has two clear centers of gravity: Ractor safety, and a cleanup of how inserts return primary keys.
On the Ractor front, three merges chip away at the same problem — making Rails usable from non-main Ractors. PR 57854, from Edouard-chin, makes controller middleware Ractor safe using a copy-on-write approach so shared state doesn't leak across isolation boundaries. PR 58108 fixes thread-local attribute readers and…
The second theme is Ryuta Kamizono's multi-PR push to simplify how the database layer handles inserts and returning values. PR 58283 consolidates the returning-column logic into the abstract adapter, removing duplicated code in PostgreSQL, SQLite, and MySQL. PR 58285 strips unused positional arguments like primary…
Elsewhere, watch for PR 58289, still open, which fixes transactions not rolling back when a before-commit callback raises — a correctness bug that could leave connections stuck mid-transaction. And PR 58237 fixes a 500 error from non-ASCII text in fragment cache digests.
What's next: the Ractor-safety PRs and the open transaction-rollback fix are worth tracking as they land, since they touch core…
Nearby episodes from Ruby on Rails
- Correctness Cleanup Across the Stack
- Cleaning Up the Schema Building Internals
- Weekly Recap - Route Loading Safety and the Great Dead Code Sweep
- Cleaning Up Legacy Keyword Argument Patterns
- Cleaning Up Old Debts
- Boot-Time Fixes and Startup Performance
- The Great Dead Code Purge
- The Great Dead Code Purge