fix: Upgrade jsonschema from <4.18.0 to >=4.18.0#1217
Merged
Conversation
The performance regression that caused the original pin (filed as referencing#178) has been resolved in newer versions. Migrate from the deprecated jsonschema.RefResolver API to the referencing.Registry API. Bundled sub-schemas with extended enums are correctly prioritized over standalone versions by comparing content size. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
A single validation triggers 40,000+ $ref resolutions with only ~17 unique URIs. Cache resolved schemas by (base_uri, ref) to avoid repeated URL parsing and pointer navigation. Brings performance to parity with jsonschema 4.17.3. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
stephenworlow
approved these changes
Jun 2, 2026
nathan-stender
added a commit
that referenced
this pull request
Jun 2, 2026
### Fixed - Upgrade jsonschema from <4.18.0 to >=4.18.0 (#1217)
nathan-stender
added a commit
that referenced
this pull request
Jun 10, 2026
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.
Summary
< 4.18.0version pin onjsonschemathat was added 2 years ago due to a performance regression in thereferencinglibrary (issue fix: Fix Quantstudio well calculated documents #178)jsonschema.RefResolverAPI toreferencing.RegistryAPIContext
The performance regression has been resolved upstream. Benchmarking confirmed jsonschema 4.26.0 performs equally or better than the pinned 4.17.3 for both cold-start and large-file validation scenarios.
Test plan
test_table_contentsfailure unrelated to this change)nM)🤖 Generated with Claude Code