Ruby on Rails: The Ractor Safety Push

Rails merged three separate fixes to make boot procs, view path caches, and class-level state safe to use inside Ractors, part of a coordinated effort toward Ractor compatibility. Separately, fixes landed for grouped relation cache keys, composite primary key nullification, and a broken Docker entrypoint check.

Duration: PT2M31S

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-05T13:12:06Z
  • Audio duration: PT2M31S

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 5th, and today's Rails activity centers on one clear priority: getting the framework ready for Ractors.

Three merged pull requests all attack the same problem from different angles. Ractors in Ruby require shareable state, and a lot of Rails' internals weren't built with that in mind. Etienne Barrie's PR 58659 fixes unshareable procs captured at boot time, extracting only the values that are actually needed so the…

Outside that theme, a handful of independent fixes are worth flagging. Ousama Ben Younes opened PR 58674 to fix cache key and cache version calculation on grouped relations — previously a "group by" query could report the wrong count and timestamp, which matters for anyone relying on Active Record's HTTP caching…

What's next: expect more Ractor-safety follow-ups, and if you're on composite primary keys or grouped relations, check whether these fixes change behavior you depended on.

That's the briefing for today.

Nearby episodes from Ruby on Rails

  1. Ractor Safety Takes Center Stage
  2. The Great Ractor Hardening
  3. Ractors Get Real, and a Data Integrity Bug Surfaces Three Times
  4. Trimming the Fat—A Day of Performance and Correctness Fixes
  5. When Data Gets Serialized Twice
  6. Weekly Recap - Concurrency Safety and Cache Store Cleanup
  7. Quiet Data, Loud Fixes
  8. Keeping Pace With Upstream Dependencies