RepoJournal
Rails

@rails

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

Pick a date

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

The Wire · Showcase

BOOTSNAP FIXES FROZEN STRING LITERALS AND COVERAGE CONFLICTS ON RUBY 4.0.4

By RepoJournal · Filed · About Rails

Bootsnap now plays nice with coverage tools and properly tracks ISeq compile option mutations, unblocking Ruby 4.0.4+ deployments.

The real story lives in Bootsnap [1][2][3], where a trio of fixes landed overnight to handle edge cases that break on newer Ruby versions. When `RubyVM::ISeq.compile_option` mutates at runtime, Bootsnap's custom compilers weren't updating — that's fixed [1]. More critical: `Bootsnap.enable_frozen_string_literal` now works even when coverage is enabled [2], but only on Ruby 4.0.4+, because coverage suspension (not full stop) breaks ISeq dumping [3]. This matters because until now, the coverage check during ISeq dumping was effectively a no-op on older Rubies.

Meanwhile, Rails itself is doing housekeeping. The QueAdapter reference was finally removed from ActiveJob [4][5], cleaning up stale code after the adapter was dropped. Docs across rails/rails and rails-dom-testing got formatting fixes [6][7][8][9][10] — proper indentation and <tt> tags so RDoc renders correctly. These are small wins but they matter for anyone reading the API docs on a fresh install.

Action items

References

  1. [1] Better support `RubyVM::ISeq.compile_option` being mutated ↗ rails/bootsnap
  2. [2] Make `Bootsnap.enable_frozen_string_literal` work even with coverage on ↗ rails/bootsnap
  3. [3] Handle Coverage being suspended ↗ rails/bootsnap
  4. [4] Merge pull request #57357 from p8/activejob/remove-reference-to-que rails/rails
  5. [5] Remove reference to removed Que adapter rails/rails
  6. [6] Fix docs formatting for `ActionController::Live` [ci skip] ↗ rails/rails
  7. [7] Merge pull request #57359 from p8/activestorage/fix-formatting-of-controller-docs rails/rails
  8. [8] Fix formatting in Active Storage controller docs rails/rails
  9. [9] Merge pull request #127 from drjayvee/fix-assert_dom-docs rails/rails-dom-testing
  10. [10] Fix documentation formatting in SelectorAssertions#assert_dom ↗ rails/rails-dom-testing

FAQ

What changed in Rails on May 14, 2026?
Bootsnap now plays nice with coverage tools and properly tracks ISeq compile option mutations, unblocking Ruby 4.0.4+ deployments.
What should Rails teams do about it?
Update Bootsnap if you're running Ruby 4.0.4+ with coverage enabled or frozen string literals • No action required for Rails core — docs-only fixes and stale code cleanup
Which Rails repositories shipped on May 14, 2026?
rails/bootsnap, rails/rails, rails/rails-dom-testing

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.