Rails Daily: The JSON Gem Ripple Effect
A dependency upgrade to the JSON gem forced a chain of compatibility fixes across Rails' test suite and CI, while separate fixes addressed Ractor detection on JRuby and error page misattribution on GitHub. No single change stands out on its own, but the JSON upgrade shows how one dependency bump can cascade through a large codebase.
Duration: PT2M41S
Episode overview
This episode is a short developer briefing from Rails Daily.
It explains recent repository work in plain language.
- Show: Rails Daily
- Published: 2026-09-08T06:02:53Z
- Audio duration: PT2M41S
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, and this is Rails Daily.
The dominant story in today's activity isn't one big feature, it's the ripple effect of upgrading the JSON gem, and what that reveals about maintaining a project the size of Rails.
Jean Boussier, working under the byroot handle, opened PR 58690 to update JSON to version 3.0. That single move triggered a cascade. The new JSON version breaks argument handling that multi_json depends on, which broke the resque test suite, which meant PR 58688 had to temporarily lock JSON below version 3.0 while…
A second theme is defensive correctness. PR 58684 fixed Active Support loading on JRuby, which reports itself as Ruby 4.0 but doesn't implement Ractor, causing a hard failure on core extension loading. And PR 58678 swapped Regexp to underscore s for Regexp dot source when detecting deep parameter filters, avoiding…
Worth noting separately: PR 58686 makes exception backtraces build lazily, a modest performance win since backtraces are expensive and often unused. And PR 58693 addresses a real ecosystem annoyance, GitHub misclassifying Rails apps as HTML instead of Ruby due to generated error pages.
What's next: expect the JSON 3.0 rollout…