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-08
stories 27
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

RAILS ADDS ATOMIC CACHE READS, TIGHTENS FORM SECURITY

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

glaucocustodio tahsin352 justinlocsei
3 people shipped this
glaucocustodio @glaucocustodio 1 cited tahsin352 @tahsin352 1 cited justinlocsei @justinlocsei 1 cited

Rails merged support for one-shot cache deletions via Redis GETDEL while fixing a security guidance issue in the getting-started docs.

The headline feature is a new `delete: true` option for `Rails.cache.read` [1] that atomically reads and deletes a cache entry in RedisCacheStore, eliminating race conditions in one-time-read patterns. This lands the Redis GETDEL command directly in the cache API—useful for tokens, OTPs, and other single-use secrets you want guaranteed to vanish after consumption. On the forms side, Rails removed `autocomplete="off"` from the authenticity_token example in the getting-started guide [2], correcting guidance that contradicted browser security best practices. A separate PR added datalist support to FormBuilder [3], expanding form capabilities without breaking changes. Over in bootsnap, the team updated documentation to reflect recent header size optimizations [4], a housekeeping change that ensures developers get accurate benchmarking expectations. The Rails changelog itself got a URL fix [5] to clean up fallout from an earlier PR. These are solid, incremental improvements—nothing that demands immediate action, but the cache deletion feature is worth knowing about for your next OTP or session management implementation.

$ 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 8, 2026?
Rails merged support for one-shot cache deletions via Redis GETDEL while fixing a security guidance issue in the getting-started docs. In total, 16 commits and 11 pull requests landed.
Who contributed to Rails on May 8, 2026?
3 developers shipped this update, including glaucocustodio, tahsin352, and justinlocsei.
What were the notable Rails updates?
Rails.cache.read: add support to new option delete: true, Merge pull request #57304 from ryu/fix-getting-started-autocomplete-off, and Add datalist to FormBuilder.
♥

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