Skip to content

build(deps): bump jsonschema from 0.57.0 to 0.58.3 - #28

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/jsonschema-0.58.3
Open

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps jsonschema from 0.57.0 to 0.58.3.

Release notes

Sourced from jsonschema's releases.

[CLI] Release 0.58.3

No release notes provided.

[Python] Release 0.58.3

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.

[Ruby] Release 0.58.3

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.

[Rust] Release 0.58.3

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.

[CLI] Release 0.58.2

No release notes provided.

[Python] Release 0.58.2

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.

[Ruby] Release 0.58.2

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.

[Rust] Release 0.58.2

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.

[CLI] Release 0.58.1

No release notes provided.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[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

Fixed

  • Crash in Pyo3 validators when an Enum member's value override emptied a list or dict holding the instance being read.

Performance

  • uri and uri-reference formats check the syntax directly instead of parsing each value into a URI.
  • Enum members read their stored value directly instead of calling the value property in Pyo3 validators.

[0.58.0] - 2026-09-25

Added

  • backend = Pyo3 on #[jsonschema::validator], generating a validator that reads Python objects in place.
  • backend = Magnus on #[jsonschema::validator], generating a validator that reads Ruby objects in place.
  • jsonschema::meta::pyo3, the bundled meta-schema validators for a schema held as a Python object.
  • jsonschema::meta::magnus, the bundled meta-schema validators for a schema held as a Ruby object.
  • methods = { ... } on #[jsonschema::validator], selecting which of is_valid, validate, and iter_errors are generated.
  • json::Jsonb, validating a Postgres jsonb value in place, behind the jsonb feature.

Performance

  • oneOf and anyOf whose branches each require a property fixed to a distinct string validate only the branch matching the instance's value.
  • Generated validate checks required in the same pass over an object as properties, instead of looking up each required name.

Fixed

  • A oneOf over $ref branches beside a sibling none of them admits, which canonicalized to an allOf instead of false.
  • multipleOf incorrectly accepted 1e-400 and other magnitudes below the smallest f64 subnormal with arbitrary-precision (they are not zero).
  • Numeric keywords panicked on a custom representation holding a number past f64 without arbitrary-precision.
Commits
  • a171a01 chore(rust): Release 0.58.3
  • b64f566 fix: Embedded resources declaring their own $schema being checked against t...
  • 8e6f96a fix: Annotations from subschemas of a failing schema in evaluation output
  • a379919 fix: Keywords of a subschema declaring a Draft 2019-09+ $schema under a Dra...
  • a11504a chore(python): Release 0.58.2
  • b839b37 chore(ruby): Release 0.58.2
  • 3d48b90 chore(rust): Release 0.58.2
  • fcf4fb3 build(deps): bump crates/jsonschema/tests/suite
  • b8d917d build(deps): update hegeltest requirement from 0.46 to 0.47
  • ed5d2ac build(deps): bump astral-sh/setup-uv from 10.1.0 to 10.2.0
  • 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.57.0 to 0.58.3.
- [Release notes](https://github.com/Stranger6667/jsonschema/releases)
- [Changelog](https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md)
- [Commits](Stranger6667/jsonschema@cli-v0.57.0...cli-v0.58.3)

---
updated-dependencies:
- dependency-name: jsonschema
  dependency-version: 0.58.3
  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 3, 2026

This branch has not been deployed

No deployments
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

Development

Successfully merging this pull request may close these issues.

0 participants