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

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

RAILS FIXES STALE JOB ERRORS AND CACHE INSTRUMENTATION

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

Five targeted fixes landed overnight to clean up job enqueueing bugs, cache tracking issues, and form field range support.

The Rails core team merged a batch of precision fixes aimed at jobs, caching, and forms. Most critical: a fix for `perform_all_later` that was leaving stale `enqueue_error` values on successfully re-enqueued jobs [1], creating a silent correctness bug where `successfully_enqueued?` would return true while the job still carried an old error state. Related, `assert_enqueued_email_with` now correctly accounts for `queue_name_prefix` in test assertions [2], so your ActionMailer job tests won't fail mysteriously when you use prefixed queues. On the caching front, `MemoryStore#increment` and `#decrement` now instrument the normalized cache key rather than the raw input [3], fixing observability gaps when you're tracking cache performance. Form builders gained support for endless and beginless ranges in `number_field` and `range_field` [4], expanding what you can express in HTML number inputs without awkward workarounds.

Action items

References

  1. [1] Clear a stale `enqueue_error` when `perform_all_later` re-enqueues a job rails/rails ↗
  2. [2] Merge pull request #58009 from 55728/fix-assert-enqueued-email-with-queue-prefix rails/rails ↗
  3. [3] Merge pull request #58007 from 55728/fix-memory-store-increment-instrument-key rails/rails ↗
  4. [4] Merge pull request #58010 from 55728/fix-number-field-endless-range rails/rails ↗

$ 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 July 6, 2026?
Five targeted fixes landed overnight to clean up job enqueueing bugs, cache tracking issues, and form field range support. In total, 18 commits and 9 pull requests landed.
What were the notable Rails updates?
Clear a stale `enqueue_error` when `perform_all_later` re-enqueues a job, Merge pull request #58009 from 55728/fix-assert-enqueued-email-with-queue-prefix, and Merge pull request #58007 from 55728/fix-memory-store-increment-instrument-key.
♥

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