Support JSON 3 in JSON index generation - #1773
Merged
Merged
Conversation
JSON 3 interprets the third argument as options, causing index generation to fail when it receives the previous integer depth limit.
nobu
requested a deployment
to
fork-preview-protection
August 11, 2026 13:30 — with 
GitHub Actions
Waiting
GitHub Actions
Waiting
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JSON 3 interprets the third argument as options, causing index generation to fail when it receives the previous integer depth limit.
In ruby/ruby, all test-bundled-gems tasks are failing due to this failure since merger of json 3.0.0.rc1.