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-04
stories 2

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

RAILS HARDENS MEMCACHESTORE AGAINST DALLI MISUSE

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

1 person shipped this

Rails now raises ArgumentError when MemCacheStore receives a Dalli::Client directly, closing a deprecated pathway that was supposed to die.

The change [1] enforces what was already promised: MemCacheStore stopped accepting Dalli::Client instances in a prior removal [2], but now it actively rejects them with a clear error rather than silently failing downstream. This is a defensive move for anyone who missed the deprecation warning and shipped code that still passes Dalli clients directly. The error message now correctly states that only "empty array, address, or array of addresses" are allowed, bringing the actual validation in line with the documentation. If you're bootstrapping MemCacheStore in initialization or test fixtures, this will catch mistakes at boot time instead of in production cache misses.

Quick answers

What shipped in Rails on May 4, 2026?
Rails now raises ArgumentError when MemCacheStore receives a Dalli::Client directly, closing a deprecated pathway that was supposed to die. In total, 1 commits and 1 pull requests landed.
Who contributed to Rails on May 4, 2026?
1 developer shipped this update, including p8.
What were the notable Rails updates?
Merge pull request #57289 from p8/activesupport/remove-dalli-class and Raise ArgumentError when MemCacheStore is created with Dalli::Client.