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-06-13
stories 40
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

REDIS LISTENER RECONNECT BUGS FIXED ACROSS THREE CRITICAL PATCHES

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

matthewd
1 person shipped this
matthewd @matthewd 2 cited

Rails killed off three separate gotchas in its pub/sub and database layers that could silently drop subscriptions, lose pending callbacks, and mutate caller data during reconnects.

The Redis listener thread was exiting permanently whenever the last channel got unsubscribed [1], which tanks any single-channel app or low-traffic service during deploy drains. That same listener was also torching pending subscribe callbacks on reconnect [2], leaving clients hanging indefinitely after connection drops. Separately, the `Time#advance` method was mutating the caller's options hash as a side effect [4], a nasty footgun for any code reusing the same options across multiple calls. On the database side, Rails now surfaces Postgres FATAL exceptions more clearly [3], distinguishing server-initiated disconnects from general statement errors so broken connections get caught immediately instead of silently on the next query. The Node.js build pipeline is jumping to v24 [5] after discovering downstream libraries already require it, leaving v22 (which is itself EOL) only as a stepping stone.

Action items

References

  1. [1] Keep the Redis listener alive when the last channel is unsubscribed rails/rails ↗
  2. [2] Keep pending subscribe confirmations across a Redis reconnect rails/rails ↗
  3. [3] Report Postgres FATAL exceptions more clearly ↗ rails/rails
  4. [4] Merge pull request #57672 from 55728/fix-advance-mutates-options-hash rails/rails ↗
  5. [5] Bump to Node.js v24 ↗ rails/buildkite-config

$ 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 June 13, 2026?
Rails killed off three separate gotchas in its pub/sub and database layers that could silently drop subscriptions, lose pending callbacks, and mutate caller data during reconnects. In total, 26 commits and 14 pull requests landed.
Who contributed to Rails on June 13, 2026?
1 developer shipped this update, including matthewd.
What were the notable Rails updates?
Keep the Redis listener alive when the last channel is unsubscribed, Keep pending subscribe confirmations across a Redis reconnect, and Report Postgres FATAL exceptions more clearly.
♥

$ 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.