Ruby on Rails: Dependency Cleanup and Cross-Platform Fixes
Rails merged a cluster of dependency housekeeping changes, led by an upgrade to JSON 3.0 and Rubocop, alongside targeted fixes for JRuby compatibility and Active Job's retry behavior. The dependency upgrades required a follow-up test fix, a reminder that version bumps ripple further than expected.
Duration: PT2M22S
Episode overview
This episode is a short developer briefing from Ruby on Rails.
It explains recent repository work in plain language.
- Show: Ruby on Rails
- Published: 2026-09-08T13:14:14Z
- Audio duration: PT2M22S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's September 8th, twenty twenty-six, and this is your Ruby on Rails briefing.
The clearest signal today: Rails is tightening up its dependency chain, and that work isn't free of friction.
Byroot landed two connected changes: upgrading Rubocop in PR 58688, and updating the JSON gem to version 3.0 in PR 58690. That json upgrade was previously blocked by a compatibility issue in the Resque test suite's use of multi-json, which threw an argument error during parsing. The fix shipped anyway, but it…
Second theme: platform and environment edge cases. PR 58684 from nicolasva fixes a real breakage on JRuby 10, which reports its Ruby version as 4.0.0 but doesn't actually define the Ractor constant. Active Support was picking its concurrency implementation based purely on version string, causing a hard failure…
On the Active Job side, PR 57198 from Saidbek fixes retry_job so it respects enqueue options when the enqueue itself is deferred until after a transaction commits. This closes a gap where retry behavior could silently ignore queue settings, closing issue 55141.
Worth a quick mention: PR 58693 stops Rails' generated error pages from being counted as HTML in GitHub's…
Nearby episodes from Ruby on Rails
- Performance Cleanup and Release Damage Control
- Weekly Recap - Getting Rails Ready for Ractors
- Docker Boot Fix and a Documentation Overhaul
- The Ractor Safety Push
- Ractor Safety Takes Center Stage
- The Great Ractor Hardening
- Ractors Get Real, and a Data Integrity Bug Surfaces Three Times
- Trimming the Fat—A Day of Performance and Correctness Fixes