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.

@rails

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

github ↗

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

RAILS HARDENS MEMCACHESTORE AGAINST DALLI MISUSE

By RepoJournal · Filed 06:00 UTC on May 4, 2026 · About Rails

1 person shipped this

p8 @p8 1 cited

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.

Action items

→ Audit MemCacheStore initialization across your codebase for any direct Dalli::Client passes rails/rails [plan]
→ Update to latest Rails main if you maintain gems that wrap MemCacheStore rails/rails [monitor]

References

[1] Merge pull request #57289 from p8/activesupport/remove-dalli-class rails/rails
[2] Raise ArgumentError when MemCacheStore is created with Dalli::Client ↗ rails/rails

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.

RAILS 8 LAZY ROUTES NOW THREAD-SAFE, SOLID QUEUE ADDS MIGRATION GENERATOR

A race condition in Rails 8's deferred route loading could serve 404s on valid routes under concurrent requests, and a fix landed overnight.

ruby 18 shipped 1-min read

@rails 1 day ago

SOLID QUEUE 1.5.0 SHIPS WITH CRITICAL CONCURRENCY FIXES

Solid Queue v1.5.0 lands three separate fixes for a production bug that corrupts semaphore counts and lets concurrency-limited jobs run wild.

ruby 45 shipped 1-min read

@rails 2 days ago

Rails Strips Dead Code, Solid Queue Hardens Tests and Drops Ruby 3.1

Aaron Patterson is cleaning up Rails internals while Solid Queue fixes flaky CI and raises its minimum Ruby version to 3.2.

ruby 17 shipped 1-min read

@rails 3 days ago

RAILS CORE CLEANS HOUSE WITH FOUR DEPRECATION SWEEPS

Rails is systematically removing unused internals across Journey, RedisCacheStore, and test utilities, signaling a major cleanup push before the next major version.

ruby 74 shipped 1-min read

Elsewhere on the wire

AI Agents about 9 hours ago

CLAUDE OPUS 5 LANDS ACROSS THE STACK

The newest Anthropic model is now live in langchain, Cline, and llama-index, with native support for extended reasoning and 1M context windows.

ai-agents 28 shipped 1-min read

Local LLMs about 9 hours ago

OLLAMA LANDS LAGUNA SUPPORT AND CRUSHES MEMORY LEAKS WHILE SGLANG HITS V0.5.16 WITH CONFIDENCE-DRIVEN SPECULATIVE DECODING

Ollama shipped three critical performance and reliability fixes for Metal residency and concurrent access patterns, while SGL-Lang released 0.5.16 with a new speculative algorithm hitting 383.7 tok/s on DeepSeek-V4.