RepoJournal
Rails

@rails

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

Pick a date

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

The Wire · Showcase

RAILS FIXES SILENT ROUTING FAILURES AND DATABASE LEAK CONDITIONS

By RepoJournal · Filed · About Rails

Rails shipped two critical fixes overnight that address a routing bug silencing boolean options and an async database maintenance leak that could corrupt test suites.

The routing fix [1] corrects a long-standing issue where falsy values like `format: false` and `anchor: false` passed through the deprecated positional-hash form were dropped entirely without warning, producing routes that behaved differently than their keyword-form equivalents. This wasn't just a deprecation miss; it was a silent correctness failure that could change application behavior during upgrades. The second fix [2] tackles a database connection leak in async executor scenarios where maintenance work was queued under lock but never properly awaited, causing the leak checker to miss outstanding checkouts and corrupt subsequent tests. Both landed as targeted patches to the main rail, not version bumps. On the CI side, the buildkite-config team wrapped docker compose operations with automatic retries [3] and upgraded to Docker Compose v2 across the board [4], addressing intermittent image pull timeouts that were flaking test runs.

Action items

References

  1. [1] Honor falsy values in routing's deprecated positional-hash options rails/rails
  2. [2] Wait for any asynchronous connection maintenance work before leak check ↗ rails/rails
  3. [3] Separately pull compose dependencies so they can be retried ↗ rails/buildkite-config
  4. [4] Use Docker Compose v2 everywhere ↗ rails/buildkite-config

FAQ

What changed in Rails on June 17, 2026?
Rails shipped two critical fixes overnight that address a routing bug silencing boolean options and an async database maintenance leak that could corrupt test suites.
What should Rails teams do about it?
Review routes using deprecated positional-hash format with boolean options • Pull latest rails/rails if running async executor in test suite • Verify Docker Compose v2 readiness in CI if running custom buildkite config
Which Rails repositories shipped on June 17, 2026?
rails/rails, rails/buildkite-config

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.