Skip to content

Bump jsonschema from 0.26.2 to 0.58.5 in /rust - #47

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/rust/jsonschema-0.58.5
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/rust/jsonschema-0.58.5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 8, 2026

Copy link
Copy Markdown

Bumps jsonschema from 0.26.2 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

Dependabot compatibility score

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 commands and options

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 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)

Bumps [jsonschema](https://github.com/Stranger6667/jsonschema) from 0.26.2 to 0.58.5.
- [Release notes](https://github.com/Stranger6667/jsonschema/releases)
- [Changelog](https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md)
- [Commits](Stranger6667/jsonschema@rust-v0.26.2...cli-v0.58.5)

---
updated-dependencies:
- dependency-name: jsonschema
  dependency-version: 0.58.5
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Oct 8, 2026
@dependabot @github

dependabot Bot commented on behalf of github Oct 15, 2026

Copy link
Copy Markdown
Author

Superseded by #48.

@dependabot dependabot Bot closed this Oct 15, 2026
@dependabot
dependabot Bot deleted the dependabot/cargo/rust/jsonschema-0.58.5 branch October 15, 2026 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants