[dependabot]

Bumps jsonschema from 0.18.3 to 0.58.5.

Release notes

Sourced from jsonschema's releases.

[CLI] Release 0.58.5

No release notes provided.

[Python] Release 0.58.5

Fixed

• canonicalize keeping a reference to a cycle of bare references under not or oneOf instead of treating it as accepting every value.
• Validator construction holding the GIL while it retrieves external resources over HTTP or from files.

[Ruby] Release 0.58.5

Fixed

• canonicalize keeping a reference to a cycle of bare references under not or oneOf instead of treating it as accepting every value.
• Validator construction holding the GVL while it retrieves external resources over HTTP or from files.

[Rust] Release 0.58.5

Fixed

• canonicalize keeping a reference to a cycle of bare references under not or oneOf instead of treating it as accepting every value.

[CLI] Release 0.58.4

No release notes provided.

[Python] Release 0.58.4

Fixed

• repr of a validator_for validator naming the default draft instead of the one $schema declares.
• unevaluatedProperties and unevaluatedItems beside a $recursiveRef ignoring what the reference target evaluates.
• unevaluatedProperties ignoring the configured regex engine and its limits for patternProperties.
• Absolute keyword location and schemaLocation of keywords a $ref JSON Pointer reaches through a subschema with its own $id.
• type, minItems and maxItems ignored beside items when the applicator vocabulary is disabled.
• Absolute keyword location and schemaLocation of keywords inside a nested $id resource counting from the document root.
• required beside properties ignored when the applicator vocabulary is disabled, and required, minContains and maxContains applied when the validation vocabulary is disabled.
• Absolute keyword location and evaluation output of type errors in a type-only items subschema pointing at items instead of the failing element's type.
• Absolute keyword location of patternProperties annotations missing its JSON Pointer fragment.
• Evaluation output of type: array beside schema-form items omitting passing type, minItems and maxItems units and nesting failing ones under items.
• Evaluation output schemaLocation and absolute keyword location of $ref, $dynamicRef and $recursiveRef nodes not pointing at the reference target.
• Evaluation output schemaLocation URIs not percent-encoding their fragment, such as a space in a property name.
• Absolute keyword location of errors and annotations from a whole subschema, such as false, missing its JSON Pointer fragment.
• Absolute keyword location of required, minContains and maxContains errors pointing at a sibling keyword.
• Evaluation annotations from $ref siblings in Draft 4, 6 and 7 schemas.
• Masked additionalItems messages counting allowed items instead of extra ones, and "1 items" in masked unevaluatedItems messages.
• $dynamicRef and $recursiveRef resolving in the dynamic scope of another path to the same schema, depending on property order.
• unevaluatedProperties and unevaluatedItems ignoring what then or else evaluates when if is true or false.
• Stack overflow when building validators for long $ref chains.
• format: "regex" and meta-schema validation rejecting escaped punctuation such as \- in patterns.
• Build errors for an invalid patternProperties regex reporting the subschema instead of the pattern and its location.

[Ruby] Release 0.58.4

Fixed

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.58.5] - 2026-10-02

Fixed

• canonicalize keeping a reference to a cycle of bare references under not or oneOf instead of treating it as accepting every value.

[0.58.4] - 2026-10-01

Fixed

• Validator::draft returning the default draft instead of the one $schema declares.
• unevaluatedProperties and unevaluatedItems beside a $recursiveRef ignoring what the reference target evaluates.
• unevaluatedProperties ignoring the configured regex engine and its limits for patternProperties.
• Absolute keyword location and schemaLocation of keywords a $ref JSON Pointer reaches through a subschema with its own $id.
• type, minItems and maxItems ignored beside items when the applicator vocabulary is disabled.
• Absolute keyword location and schemaLocation of keywords inside a nested $id resource counting from the document root.
• required beside properties ignored when the applicator vocabulary is disabled, and required, minContains and maxContains applied when the validation vocabulary is disabled.
• Absolute keyword location and evaluation output of type errors in a type-only items subschema pointing at items instead of the failing element's type.
• Absolute keyword location of patternProperties annotations missing its JSON Pointer fragment.
• Evaluation output of type: array beside schema-form items omitting passing type, minItems and maxItems units and nesting failing ones under items.
• Evaluation output schemaLocation and absolute keyword location of $ref, $dynamicRef and $recursiveRef nodes not pointing at the reference target.
• Evaluation output schemaLocation URIs not percent-encoding their fragment, such as a space in a property name.
• Absolute keyword location of errors and annotations from a whole subschema, such as false, missing its JSON Pointer fragment.
• Absolute keyword location of required, minContains and maxContains errors pointing at a sibling keyword.
• Evaluation annotations from $ref siblings in Draft 4, 6 and 7 schemas.
• Masked additionalItems messages counting allowed items instead of extra ones, and "1 items" in masked unevaluatedItems messages.
• $dynamicRef and $recursiveRef resolving in the dynamic scope of another path to the same schema, depending on property order.
• unevaluatedProperties and unevaluatedItems ignoring what then or else evaluates when if is true or false.
• Stack overflow when building validators for long $ref chains.
• format: "regex" and meta-schema validation rejecting escaped punctuation such as \- in patterns.
• Build errors for an invalid patternProperties regex reporting the subschema instead of the pattern and its location.

[0.58.3] - 2026-09-30

Fixed

• Keywords of a subschema declaring a Draft 2019-09+ $schema under a Draft 4, 6 or 7 root being ignored.
• Evaluation annotations including those from subschemas of a failing schema (a failing schema produces no annotations).
• Embedded resources declaring their own $schema being checked against the root's meta-schema.

[0.58.2] - 2026-09-28

Fixed

• $dynamicRef targets in another document resolving relative references and reporting absolute keyword locations against the referencing document.
• $ref to an $anchor or fragment $id validating against another anchor in the same document. #1668
• schema_path of errors under a $ref or $dynamicRef to a named schema pointing at the resource root instead of that schema.

[0.58.1] - 2026-09-26

... (truncated)

Commits

• 21a061d chore(rust): Release 0.58.5
• 6c28049 chore: Migrate to the Ruby::gc_* API of magnus 0.9
• 4cfb109 build(deps): update magnus requirement from 0.8 to 0.9
• c0799ca docs: Update readme files
• e9d1f7a build: Pin the gem documentation link to its release tag
• a91b882 docs: Document the offline option
• baa41b6 docs: Wrap long code lines in the Python README
• f21bb64 docs: Tighten the Ruby README
• fbe8de1 docs: Tighten the Python README
• 6f9e4e7 fix: Release the GIL and GVL while retrieving external resources
• Additional commits viewable in compare view

[e54-bot]

The Rust (stable) Quality gate fails on the jsonschema 0.58 API change — jsonschema::JSONSchema was removed (the entry points are now jsonschema::validator_for(&schema) → Validator, with .is_valid(&instance)/.validate(&instance)):

error[E0433]: cannot find `JSONSchema` in `jsonschema`
  --> crates/wright-cli/tests/diagnostics_schema.rs:72

Two test-side call sites need the mechanical update before the bump can land — crates/wright-cli/tests/agent_contract.rs (use jsonschema::JSONSchema) and crates/wright-cli/tests/diagnostics_schema.rs (JSONSchema::compile). Whoever takes the upgrade should patch them on the same PR.

[dependabot]

A newer version of jsonschema exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[e54-bot]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[e54-bot]

Superseded by #866, which ports the tests and keeps jsonschema's default features off.

[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.