RepoJournal
Rails

@rails

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

Pick a date

  1. Mon 25 may
  2. Tue 26 may
  3. Wed 27 may
  4. Thu 28 may
  5. Fri 29 may
  6. Sat 30 may
  7. Sun 31 may
  8. Mon 1 jun
  9. Mon 8 jun
  10. Tue 9 jun
  11. Wed 10 jun
  12. Thu 11 jun
  13. Fri 12 jun
  14. Sat 13 jun
  15. Sun 14 jun
  16. Mon 15 jun
  17. Tue 16 jun
  18. Wed 17 jun
  19. Thu 18 jun
  20. Fri 19 jun
  21. Sat 27 jun
  22. Sun 28 jun
  23. Mon 29 jun
  24. Tue 30 jun
  25. Wed 1 jul
  26. Thu 2 jul
  27. Fri 3 jul
  28. Sat 4 jul
  29. Sun 5 jul
  30. Today 6 jul

The Wire · Showcase

RAILS FIXES STALE JOB ERRORS AND CACHE INSTRUMENTATION

By RepoJournal · Filed · About Rails

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

FAQ

What changed 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.
What should Rails teams do about it?
Upgrade to latest main if using perform_all_later with fallback job enqueueing • Review ActionMailer queue prefix tests if using queue_name_prefix • Update cache instrumentation dashboards if relying on MemoryStore metrics
Which Rails repositories shipped on July 6, 2026?
rails/rails

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.