RepoJournal
Rails @rails
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-05-25
stories 16
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Rails Fixes Composite Foreign Key Touch Bug, Solid Cable Drops Ruby 3.1

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

romulostorel
1 person shipped this
romulostorel @romulostorel 1 cited

Rails patched a silent failure in composite foreign key associations where touch: true would skip updating the old record when relationships changed.

The composite foreign key fix [1] [2] addresses a real production problem: when a belongs_to with touch: true and composite keys changed targets, only the new associated record got its updated_at timestamp. The old one was silently skipped because the touch_record method was doing a hash lookup with the entire array as key, but saved_changes tracks individual column names. Now each column is checked individually to reconstruct the old composite key. This is a solid catch for anyone using composite foreign keys in associations [3]. Separately, Rails test infrastructure improved with better database cleanup after bin/setup tests [4] [5], preventing stale app_development and app_test databases from polluting the test environment. On the Solid Cable desk, v4.0.0 shipped with breaking changes: Ruby 3.1 and 3.2 support dropped [6], and the library now eagerly initializes last_id to avoid skipping messages on reconnection [6]. If you're running Solid Cable on Ruby 3.1 or 3.2, you're locked to v3.x.

$ ls rails/reviews/ # the step-back reads

the week in review Ractor-ready Active Record and Active Job land in Rails the month in review Herb becomes Rails 8.2 default
Full archive → Weekly reviews →

Quick answers

What shipped in Rails on May 25, 2026?
Rails patched a silent failure in composite foreign key associations where touch: true would skip updating the old record when relationships changed. In total, 10 commits, 5 pull requests, and 1 releases landed.
Who contributed to Rails on May 25, 2026?
1 developer shipped this update, including romulostorel.
What were the notable Rails updates?
Merge pull request #57158 from romulostorel/fix-composite-fk-touch-record, Fix touching records via composite foreign keys, and Fix touch_record for composite foreign keys.
♥

$ log @rails --recent

Attribute-read regression fixed, decimal numericality corrected 79 shipped in_order_of double-serializes values, id_value alias restored 50 shipped Inlined attribute writers, leaner ActiveRecord::Key 31 shipped MySQL 5.6 falls off the support floor as Arel stops rebuilding literals 27 shipped

$ log --all # elsewhere on the wire

Alignment & Post-training verl standardizes low-precision rollout kernels on DeepGEMM Agent Security Guardrails exposes hooks over HTTP, certifi floor raised in agent-scan

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.