chore(deps): bump jsonschema from 0.46.10 to 0.51.0

[dependabot]

Bumps jsonschema from 0.46.10 to 0.51.0.

Release notes

Sourced from jsonschema's releases.

[CLI] Release 0.51.0

No release notes provided.

[Python] Release 0.51.0

Added

• vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

• The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
• The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
• A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
• The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
• A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
• A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
• The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
• The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
• The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
• Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

• Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Ruby] Release 0.51.0

Added

• vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

• The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
• The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
• A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
• The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
• A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
• A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
• The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
• The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
• The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
• Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

• Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.51.0] - 2026-08-23

Added

• ValidationOptions::with_vocabulary and the vocabularies attribute on jsonschema::validator, declaring support for a vocabulary this crate does not implement.
• The --vocabulary flag of jsonschema validate.

Changed

• Vocabulary gained the FormatAssertion variant, which its Draft 2020-12 URI parses to instead of Vocabulary::Custom, and is marked non_exhaustive.

Fixed

• The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
• The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
• A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected).
• The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
• A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
• A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
• The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
• The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
• The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
• Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

• Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[0.50.1] - 2026-08-22

Changed

• CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
• CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

• CanonicalSchema::negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
• CanonicalSchema::subtract dropping a Draft 4 array member an element demand partly takes.
• CanonicalSchema::covers answering Yes where a Draft 4 element demand refuses a member.
• A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

• not over a wide object schema costs its branch count instead of its square.
• not over an object schema is linear in its property count, not quadratic.
• not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

... (truncated)

Commits

• b7fd606 chore(rust): Release 0.51.0
• b225a20 fix: Stack overflow compiling unevaluatedProperties or unevaluatedItems b...
• df15d19 build(deps): bump crates/jsonschema/tests/suite
• df8b81c fix: Misc format fixes
• 38056c7 feat: ValidationOptions::with_vocabulary and the vocabularies attribute o...
• 31d52b2 fix: The uniqueItems length ceiling not reading an items or contains sc...
• 5993cf1 chore(ruby): Release 0.50.1
• e04ecc6 build(ruby): Exclude arm-linux-musl
• 1fc21b9 chore(python): Release 0.50.1
• 60a563d chore(rust): Release 0.50.1
• Additional commits viewable in compare view

[github-actions]

Thanks @dependabot[bot] for taking the time to contribute.

This repository is observing a maintainer-managed PR intake gate in dry-run mode, so this pull request is staying open. This note helps maintainers prepare the allowlist before any enforcement is considered.

Please read CONTRIBUTING.md for the expected contribution shape. A maintainer can grant recurring PR access by commenting /lgtm on a pull request.

[Hmbown]

Closing with thanks @dependabot — this is a policy decline, not a CI one.

The workspace pins jsonschema to the ^0.46 line on purpose. Root Cargo.toml:55-58 on main reads: "Pinned to the jsonschema line schemaui 0.12 requires (^0.46) so the graph carries one jsonschema/jsonschema-regex/referencing/fancy-regex stack. Move both together when schemaui catches up (dependabot: keep in step)." schemaui 0.12.4 (#5695) still requires ^0.46, so this PR's lock carries both jsonschema 0.46.10 and 0.51.0 plus duplicate jsonschema-regex/referencing and a fourth fancy-regex; cargo-deny only passed because multiple-versions = "warn". The code compiled and the full matrix passed on macOS and Windows; the Ubuntu telemetry_kill_switch_dispatch pair is unexplained (both tests pass on current main locally) but moot given the pin.

Re-open path: when schemaui moves to a jsonschema >= 0.51 line, bump both together. This closes 0.51.0 only — no ignore command — so 0.46.x patch releases keep flowing.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.