RepoJournal
Rails

@rails

Ruby on Rails - Shopify, Basecamp, GitHub all run on it

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

One email a day. Unsubscribe in one click.

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

REDIS LISTENER RECONNECT BUGS FIXED ACROSS THREE CRITICAL PATCHES

By RepoJournal · Filed · About Rails

1 person shipped this

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.

One email a day. Unsubscribe in one click.

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

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.

More from @rails

Daily updates, in your inbox

Follow Rails

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

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.