Rails Daily: Ractor Safety and Composite Key Fixes

Rails saw a coordinated push to make core objects safe to share across Ractors, alongside a cluster of fixes for how belongs_to associations track composite and aliased foreign keys.

Duration: PT2M42S

Episode overview

This episode is a short developer briefing from Rails Daily.

It explains recent repository work in plain language.

  • Show: Rails Daily
  • Published: 2026-08-04T06:01:37Z
  • 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 August 4th, 2026, and this is Rails Daily.

Today's codebase activity centers on two clear efforts: preparing Rails internals for Ractor use, and closing gaps in how associations track foreign keys that aren't simple, single columns.

Let's start with Ractors. Half a dozen pull requests this cycle chase down objects that quietly break Ractor isolation. Nicolas Vahlas fixed a logger level lookup in PR 58355 that could crash on Ruby debug builds because it relied on Fiber-keyed state from another Ractor. Edouard Chin tackled attribute types in PR…

The second theme is foreign key handling in associations. Kamipo's PR 58364 fixed counter caches, autosave, and has_many-through nullify operations that silently no-op'd when foreign keys were composite or aliased. A follow-up, PR 58368, refactors BelongsToAssociation to use a unified key abstraction instead of…

Two smaller but notable items: PR 58367 raises the minimum Rack requirement to 3.1, dropping support for older Rack 3 lines. And PR 58350 changes MySQL's default sql_mode to include zero-date and division-by-zero checks that RDS and Aurora often lack.

What's next: if you maintain gems interacting with loggers,…

Nearby episodes from Rails Daily

  1. Weekly Recap - Ractor Readiness and the Slow Cleanup of Legacy Interfaces
  2. Old Shortcuts Come Due
  3. Ractor Freezing Cracks and a Wave of Coverage Fixes
  4. Anonymous Classes Break Things
  5. SQL Internals Get a Cleanup
  6. Ractor Safety and Insert Internals
  7. Ractor Safety and the Great Database Cleanup
  8. SQL Building Gets a Cleanup, Hot Paths Get Leaner