159 wires and counting

$ follow Rails

Keep up with Rails in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-10-17
stories 37

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Association keys resolved once per class pair, Ractor proxy moves state to the main Ractor

By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology

Active Record's association key handling collapses into a single Route object per concrete owner and target class pair, while the Ractor proxy adapter stops managing its own connection from the worker side.

AssociationRoute: consolidate how association keys are read and written rails/rails

by matthewd

Association keys are now resolved once for each pair of concrete owner and target classes as a Route, and queries, in-memory matching, and writes all run through it. Matthew Draper notes the refactor surfaced edge-case bugs (59073, 59074, 59075, 59076, 59079) plus others fixed incidentally "just because everything's going through the same implementation."

Keep Ractor-proxied connection state on the main Ractor rails/rails

by matthewd

The Ractor proxy adapter used to force an eager `connect!` at checkout and hand-crank verification and reconnects from the worker side; the main-side connection now tracks the worker's transactions and manages itself. The old approach could restore a transaction that had already been written to, losing that write.

Resolve association reads through routes rails/rails

by Matthew Draper

Reads now resolve through the Route too, so keys, aliases, and polymorphic names come from the models involved rather than from the association declaration. Anything depending on declaration-time key resolution should be re-tested against this.

Run Active Record sqlite3_ractor test profile when available rails/buildkite-config

by Gannon McGibbon

Buildkite now runs Active Record's sqlite3_ractor profile when the Rails version provides it, enabling tests with ractor proxy connection handling backed by sqlite3. The merge gates that profile to Rails 8.2a and newer.

This Week in Rails: October 16, 2026 (#761) rails/website

by Vipul A M

The October 16 edition of This Week in Rails covers Active Record performance and streaming isolation updates, and clarifies that the extension schema fix follows earlier coverage.

Quick answers

What shipped in Rails on October 17, 2026?
Active Record's association key handling collapses into a single Route object per concrete owner and target class pair, while the Ractor proxy adapter stops managing its own connection from the worker side. In total, 25 commits and 12 pull requests landed.
Who contributed to Rails on October 17, 2026?
4 developers shipped this update, including Gannon McGibbon, matthewd, fatkodima, and Vipul A M.
What were the notable Rails updates?
AssociationRoute: consolidate how association keys are read and written, Keep Ractor-proxied connection state on the main Ractor, and Resolve association reads through routes.