Skip to content

Commit a73f871

Browse files
chore(deps-rs): bump jsonschema from 0.33.0 to 0.35.0 (#2694)
Bumps [jsonschema](https://github.com/Stranger6667/jsonschema) from 0.33.0 to 0.35.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Stranger6667/jsonschema/releases">jsonschema's releases</a>.</em></p> <blockquote> <h2>[Python] Release 0.35.0</h2> <h3>Added</h3> <ul> <li>Support for custom meta-schemas. Schemas with custom <code>$schema</code> URIs can now be used by registering their meta-schemas via the <code>registry</code> parameter in <code>validator_for()</code>. <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/664">#664</a></li> <li><code>registry</code> parameter to <code>meta.is_valid()</code> and <code>meta.validate()</code> for validating schemas against custom meta-schemas.</li> <li>Type stubs for the <code>meta</code> module.</li> <li>PyPy 3.11 support. <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/309">#309</a></li> <li>Support for arbitrary-precision numbers, including large integers and high-precision decimals that exceed standard floating-point limits. <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/103">#103</a></li> <li>Support for HTTPS <code>$schema</code> URIs for drafts 04, 06, and 07 (e.g., <code>https://json-schema.org/draft-07/schema</code>). <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/802">#802</a></li> </ul> <h3>Changed</h3> <ul> <li><strong>BREAKING</strong>: <code>meta.is_valid()</code> and <code>meta.validate()</code> now raise <code>ReferencingError</code> for unknown <code>$schema</code> values instead of defaulting to Draft 2020-12. Use the <code>registry</code> parameter to validate against custom meta-schemas.</li> <li>Migrated to abi3, so a single wheel per platform works on all supported 3.10+ interpreters.</li> </ul> <h3>Removed</h3> <ul> <li>Support for Python 3.8 &amp; 3.9.</li> </ul> <h3>Performance</h3> <ul> <li><code>required</code>: short-circuit when the instance object has fewer properties than required keys.</li> <li>Arbitrary precision support is always enabled. Performance impact is negligible for most schemas, with ~2x slowdown only for number-heavy instances (e.g., GeoJSON).</li> </ul> <h2>[Rust] Release 0.35.0</h2> <h3>Added</h3> <ul> <li>Support for custom meta-schemas. Schemas with custom <code>$schema</code> URIs can now be used by registering their meta-schemas in the <code>Registry</code> via <code>jsonschema::options().with_registry()</code>. <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/664">#664</a></li> <li><code>arbitrary-precision</code> feature for exact numeric validation of large integers and decimals beyond standard floating-point limits. <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/103">#103</a></li> <li>Support for HTTPS <code>$schema</code> URIs for drafts 04, 06, and 07 (e.g., <code>https://json-schema.org/draft-07/schema</code>). <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/802">#802</a></li> </ul> <h3>Changed</h3> <ul> <li><strong>BREAKING</strong>: <code>meta::is_valid</code> now panics for unknown <code>$schema</code> values instead of defaulting to Draft 2020-12. <code>meta::validate</code> returns an error for unknown <code>$schema</code> values. Use <code>meta::options().with_registry()</code> to validate schemas against custom meta-schemas.</li> <li><strong>BREAKING</strong>: <code>Resource::from_contents</code> no longer returns <code>Result</code> and always succeeds, since draft detection no longer fails for unknown <code>$schema</code> values.</li> </ul> <h3>Removed</h3> <ul> <li><strong>BREAKING</strong>: <code>meta::try_is_valid</code> and <code>meta::try_validate</code>. Use <code>meta::is_valid</code> and <code>meta::validate</code> instead.</li> <li><strong>BREAKING</strong>: <code>primitive_type</code> module (deprecated since 0.30.0). Use <code>jsonschema::types</code> instead.</li> </ul> <h3>Performance</h3> <ul> <li><code>required</code>: short-circuit when the instance object has fewer properties than required keys.</li> </ul> <h2>[Python] Release 0.34.0</h2> <h3>Added</h3> <ul> <li>Python 3.14 support.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md">jsonschema's changelog</a>.</em></p> <blockquote> <h2>[0.35.0] - 2025-11-16</h2> <h3>Added</h3> <ul> <li>Support for custom meta-schemas. Schemas with custom <code>$schema</code> URIs can now be used by registering their meta-schemas in the <code>Registry</code> via <code>jsonschema::options().with_registry()</code>. <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/664">#664</a></li> <li><code>arbitrary-precision</code> feature for exact numeric validation of large integers and decimals beyond standard floating-point limits. <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/103">#103</a></li> <li>Support for HTTPS <code>$schema</code> URIs for drafts 04, 06, and 07 (e.g., <code>https://json-schema.org/draft-07/schema</code>). <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/802">#802</a></li> </ul> <h3>Changed</h3> <ul> <li><strong>BREAKING</strong>: <code>meta::is_valid</code> now panics for unknown <code>$schema</code> values instead of defaulting to Draft 2020-12. <code>meta::validate</code> returns an error for unknown <code>$schema</code> values. Use <code>meta::options().with_registry()</code> to validate schemas against custom meta-schemas.</li> <li><strong>BREAKING</strong>: <code>Resource::from_contents</code> no longer returns <code>Result</code> and always succeeds, since draft detection no longer fails for unknown <code>$schema</code> values.</li> </ul> <h3>Removed</h3> <ul> <li><strong>BREAKING</strong>: <code>meta::try_is_valid</code> and <code>meta::try_validate</code>. Use <code>meta::is_valid</code> and <code>meta::validate</code> instead.</li> <li><strong>BREAKING</strong>: <code>primitive_type</code> module (deprecated since 0.30.0). Use <code>jsonschema::types</code> instead.</li> </ul> <h3>Performance</h3> <ul> <li><code>required</code>: short-circuit when the instance object has fewer properties than required keys.</li> </ul> <h2>[0.34.0] - 2025-11-14</h2> <h3>Changed</h3> <ul> <li><strong>BREAKING</strong>: <code>BasicOutput</code> and <code>Annotations</code> no longer have lifetime parameters. Update type annotations from <code>BasicOutput&lt;'a&gt;</code> to <code>BasicOutput</code> and <code>Annotations&lt;'a&gt;</code> to <code>Annotations</code>.</li> <li><code>referencing</code>: URI caching now avoids hash collisions and reduces lock contention.</li> <li>Update <code>fluent-uri</code> to <code>0.4.1</code>.</li> <li>Bump MSRV to <code>1.83.0</code>.</li> <li>Drop the <code>Send + Sync</code> bounds from <code>Retrieve</code>/<code>AsyncRetrieve</code> on <code>wasm32</code>.</li> <li>Use the new <code>draftX::meta::validator()</code> helper so meta-schema validators lazy-init on <code>wasm32</code> while native targets keep borrowing the cached <code>jsonschema::meta::MetaValidator</code>.</li> </ul> <h3>Fixed</h3> <ul> <li>Hostname and IDN hostname formats now decode <code>xn--</code> labels, reject leading combining marks/uppercase prefixes, and enforce the latest JSON Schema punycode context rules.</li> <li>Restore <code>wasm32-unknown-unknown</code> support. <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/785">#785</a></li> </ul> <h3>Performance</h3> <ul> <li><code>apply</code> now reuses cached schema locations, URI fragments, and buffers for up to ~2.5x faster validation.</li> <li>Recursive and regular <code>$ref</code> compilation deduplicates validator nodes, which decreases the memory usage and improves performance.</li> <li>Validator compilation restores the regex cache for faster builds on regex-heavy schemas and precomputes absolute schema locations, trading a bit of compile time for faster <code>apply</code> on location-heavy workloads.</li> <li>Large schema compilation is significantly faster. <a href="https://redirect.github.com/Stranger6667/jsonschema/issues/755">#755</a></li> <li><code>unevaluatedProperties</code> validation is 25-35% faster through optimized property marking and early-exit paths.</li> <li><code>unevaluatedProperties</code> memory usage drastically reduced by eliminating redundant registry clones during compilation.</li> <li><code>unevaluatedItems</code> validation is ~10% faster through early-exit optimizations and eliminating redundant validations in combinators.</li> </ul> <h3>Removed</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Stranger6667/jsonschema/commit/bed4a9c9b1212940464342068a789e6f23139de5"><code>bed4a9c</code></a> chore(rust): Release 0.35.0</li> <li><a href="https://github.com/Stranger6667/jsonschema/commit/9384225ac4376d1f749ad5f67eb477b19362e909"><code>9384225</code></a> build: Update images for Python releases</li> <li><a href="https://github.com/Stranger6667/jsonschema/commit/46a2e8f348b7fe4881b62c8f92c34d1ff11c310c"><code>46a2e8f</code></a> build: Update macOS 13 images for Python releases</li> <li><a href="https://github.com/Stranger6667/jsonschema/commit/c61a526375065757bf2b64fcb542add3e47097c4"><code>c61a526</code></a> build: Update CI images excluding Python releases</li> <li><a href="https://github.com/Stranger6667/jsonschema/commit/2dbc8c933e02c06f1baab857a582a807dda35005"><code>2dbc8c9</code></a> chore: Fix clippy lints</li> <li><a href="https://github.com/Stranger6667/jsonschema/commit/5f2e61728916f448a78b8406fced0f34a0ea7f67"><code>5f2e617</code></a> test: Update tests</li> <li><a href="https://github.com/Stranger6667/jsonschema/commit/309dd47aa3fbf5a87bd443503da8c2215eb52f69"><code>309dd47</code></a> fix(referencing): accept https $schema for drafts 04/06/07 and add tests (<a href="https://redirect.github.com/Stranger6667/jsonschema/issues/803">#803</a>)</li> <li><a href="https://github.com/Stranger6667/jsonschema/commit/318fa68dc6f32a4ffa059d2c25d2b97032cff960"><code>318fa68</code></a> docs: Update migration guide</li> <li><a href="https://github.com/Stranger6667/jsonschema/commit/43a21e6710f44f2e4c5066af2511e5d85a453ffb"><code>43a21e6</code></a> docs: Update benchmarks</li> <li><a href="https://github.com/Stranger6667/jsonschema/commit/e1e47b7ee88c2ce7dcc4a4cfdbc4a9b1042629d3"><code>e1e47b7</code></a> feat: Arbitrary precision numbers</li> <li>Additional commits viewable in <a href="https://github.com/Stranger6667/jsonschema/compare/rust-v0.33.0...rust-v0.35.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=jsonschema&package-manager=cargo&previous-version=0.33.0&new-version=0.35.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
1 parent fcd1026 commit a73f871

File tree

2 files changed

+31
-21
lines changed

2 files changed

+31
-21
lines changed

Cargo.lock

Lines changed: 30 additions & 20 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ downcast-rs = "2.0.2"
5252
enum_dispatch = "0.3.11"
5353
html-escape = "0.2.13"
5454
itertools = "0.14.0"
55-
jsonschema = "0.33.0"
55+
jsonschema = "0.35.0"
5656
num-rational = "0.4.1"
5757
pastey = "0.1.1"
5858
proptest = "1.9.0"

0 commit comments

Comments
 (0)