Skip to content

chore(deps): Bump jsonschema from 0.53.0 to 0.58.0 - #2012

Merged
gtema merged 1 commit into
mainfrom
dependabot/cargo/jsonschema-0.58.0
Sep 29, 2026
Merged

gtema merged 1 commit into
mainfrom
dependabot/cargo/jsonschema-0.58.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 28, 2026

Copy link
Copy Markdown
Contributor

Bumps jsonschema from 0.53.0 to 0.58.0.

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.58.0

Performance

  • oneOf and anyOf whose branches each require a property fixed to a distinct string validate only the branch matching the instance's value.
  • meta.is_valid and meta.validate check a schema against the bundled drafts without converting it first, about 2x faster on the benchmarked schemas.

Fixed

  • Crash on free-threaded Python when another thread resized a list or dict during validation.
  • find_unsatisfiable missing a oneOf over $ref branches beside a sibling none of them admits.

[Ruby] Release 0.58.0

Performance

  • oneOf and anyOf whose branches each require a property fixed to a distinct string validate only the branch matching the instance's value.
  • Meta.valid? and Meta.validate! check a schema against the bundled drafts without converting it first, 2 to 5x faster on the benchmarked schemas.

Fixed

  • Canonical.find_unsatisfiable missing a oneOf over $ref branches beside a sibling none of them admits.
  • A value with no JSON form nested under type: null failing validation silently (it should raise TypeError).

[Rust] Release 0.58.0

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.

[Python] Release 0.57.1

Fixed

  • Packaging issue.

[Ruby] Release 0.57.0

Added

... (truncated)

Changelog

Sourced from jsonschema's changelog.

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

[0.57.0] - 2026-09-22

Added

  • PreparedDocument::unsatisfiable, naming the keywords that leave each unsatisfiable subschema empty and where they are.

Changed

  • PreparedDocument::unsatisfiable_pointers is replaced by PreparedDocument::unsatisfiable.

Fixed

  • The instance path of a schema build error, which was empty instead of naming the keyword location that failed to compile.
  • PreparedDocument::unsatisfiable_pointers passed over a subschema that admits no value only once its references resolve, such as an allOf over two $refs.

Performance

  • Canonicalizing several subschemas of one prepared document parses each definition body once for the document instead of once per call.

[0.56.0] - 2026-09-10

Added

  • canonical::RawReason, what stopped a run from modeling a document, and canonical::RawView, carrying it beside the document and a pointer to the subschema the run stopped on.
  • ValidationOptions::is_known_format, whether a format of that name is checked under a draft.

Changed

... (truncated)

Commits
  • 894beed chore(ruby): Release 0.58.0
  • ad33f36 chore(rust): Release 0.58.0
  • 84ec127 docs: Update FHIR benchmark numbers
  • 91ac6fa perf: Validate only the matching branch of discriminated oneOf and anyOf
  • cb40352 perf: Reject undeclared properties before validating values
  • 6e9859f perf: Benchmarks for jsonb instances
  • 91fd2eb perf: Tune Ruby benchmark
  • fc7502e test: Run the JSON Schema Test Suite over jsonb instances
  • 1394de9 feat: Validating Postgres jsonb values in place
  • 87b9933 test: Postgres jsonb corpus and live differential tests
  • 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.53.0 to 0.58.0.
- [Release notes](https://github.com/Stranger6667/jsonschema/releases)
- [Changelog](https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md)
- [Commits](Stranger6667/jsonschema@ruby-v0.53.0...ruby-v0.58.0)

---
updated-dependencies:
- dependency-name: jsonschema
  dependency-version: 0.58.0
  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 Sep 28, 2026
@gtema
gtema merged commit f149c03 into main Sep 29, 2026
23 checks passed
@dependabot
dependabot Bot deleted the dependabot/cargo/jsonschema-0.58.0 branch September 29, 2026 14:42
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.

1 participant