chore: bump jsonschema from 0.52.0 to 0.53.0

[dependabot]

Bumps jsonschema from 0.52.0 to 0.53.0.

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.53.0

Fixed

• Draft 4 type: integer matching a float or not depending on its repr; a float is never a draft 4 integer.
• Draft 4 type: integer accepting Decimal("1E+2").
• uniqueItems accepting 0 alongside -0.0 in arrays of more than 15 items.

Performance

• Canonicalizing an allOf of object schemas walks their property maps once instead of looking every key up.
• properties and required compare short names without memcmp.
• type: integer, and type sets containing it, are up to 67x faster on float-heavy instances.
• Draft 4 type: integer is up to 20x faster on float-heavy instances.
• Raising ValidationError is up to 38% faster.
• evaluate is up to 30% faster, from rendering each node's locations once.
• Building a schema resolves each $ref target once instead of per reference site.
• Building a schema with an $id encodes each absolute location once instead of re-validating it.
• enum listing strings or integers, with or without null, matches against a set instead of comparing each candidate.

[Ruby] Release 0.53.0

Fixed

• Draft 4 type: integer matching a Float or not depending on its formatting; a Float is never a draft 4 integer.
• uniqueItems accepting 0 alongside -0.0 in arrays of more than 15 items.

Performance

• Canonicalizing an allOf of object schemas walks their property maps once instead of looking every key up.
• properties and required compare short names without memcmp.
• Draft 4 type: integer is up to 6x faster on float-heavy instances.
• evaluate renders each node's locations once instead of rebuilding them.
• Building a schema resolves each $ref target once instead of per reference site.
• Building a schema with an $id encodes each absolute location once instead of re-validating it.
• enum listing strings or integers, with or without null, matches against a set instead of comparing each candidate.

[Rust] Release 0.53.0

Added

• Location::segments, iterating the segments without collecting them.
• CanonicalizeOptions::prepare, canonicalizing any number of a document's subschemas by JSON Pointer, with the document indexed once.
• CLI: the --at POINTER flag of jsonschema canonicalize, canonicalizing only the subschema at that pointer without breaking its references into the rest of the document.
• CLI: jsonschema canonicalize reads YAML schemas (.yaml/.yml) as well as JSON.
• canonical::{ArrayView, IntegerView, NumberView, ObjectView, StringView, TypedGroupView}, the payload types of CanonicalView, so consumers can name them in signatures.

Fixed

• jsonschema-value failing to build with default-features = false.
• jsonschema-value failing to build for wasm32-unknown-unknown, which needs getrandom's wasm_js backend.
• Draft 4 type: integer accepting numbers written with an exponent, like 1e2.
• Draft 4 type: integer answering differently for the same number across representations.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.53.0] - 2026-09-02

Added

• Location::segments, iterating the segments without collecting them.
• CanonicalizeOptions::prepare, canonicalizing any number of a document's subschemas by JSON Pointer, with the document indexed once.
• CLI: the --at POINTER flag of jsonschema canonicalize, canonicalizing only the subschema at that pointer without breaking its references into the rest of the document.
• CLI: jsonschema canonicalize reads YAML schemas (.yaml/.yml) as well as JSON.
• canonical::{ArrayView, IntegerView, NumberView, ObjectView, StringView, TypedGroupView}, the payload types of CanonicalView, so consumers can name them in signatures.

Fixed

• jsonschema-value failing to build with default-features = false.
• jsonschema-value failing to build for wasm32-unknown-unknown, which needs getrandom's wasm_js backend.
• Draft 4 type: integer accepting numbers written with an exponent, like 1e2.
• Draft 4 type: integer answering differently for the same number across representations.
• uniqueItems accepting 0 alongside -0.0 in arrays of more than 15 items.

Performance

• Canonicalizing an allOf of object schemas walks their property maps once instead of looking every key up.
• properties and required compare short names without memcmp.
• Building a schema is up to 5% faster, from cheaper cache sharing and resolving each $ref target once.
• Building a schema with an $id is up to 15% faster, from encoding each absolute location once.
• required scans small objects once instead of looking up each key.
• enum listing strings or integers, with or without null, matches against a set instead of comparing each candidate.
• evaluate is up to 33% faster, from rendering each node's locations once.
• CLI: 1.4-1.5x faster on large schemas, from reading files before parsing them.
• Draft 4 type: integer with arbitrary-precision no longer allocates a string per number.
• type: integer, and type sets containing it, are up to 54x faster on float-heavy instances with arbitrary-precision.
• Draft 4 type: integer is up to 20x faster for the Pyo3 and Magnus representations.

[0.52.1] - 2026-08-30

Fixed

• multipleOf rejecting valid values like 1070468.14 for 0.01 without arbitrary-precision.

Performance

• minLength and maxLength together now scan the string once.
• multipleOf with a fractional divisor is 8-16x faster.
• unevaluatedProperties is up to 2.9x faster.
• evaluate is up to 27% faster on reference-heavy schemas.

Commits

• a1479a9 chore(ruby): Release 0.53.0
• 9d09cf5 chore(python): Release 0.53.0
• 6af37d8 chore(rust): Release 0.53.0
• 8067365 perf: Canonicalizing an allOf of object schemas walks their property maps o...
• bf325f2 perf: properties and required compare short names without memcmp
• 1d637f4 fix: uniqueItems accepting 0 alongside -0.0 in arrays of more than 15 i...
• 09c497d chore: `canonical::{ArrayView, IntegerView, NumberView, ObjectView, StringVie...
• c38c4e6 build(deps): bump taiki-e/install-action from 2.87.1 to 2.87.2
• f80fe92 perf: Special casing for nullable enums
• 84f5570 docs: Update changelogs
• Additional commits viewable in compare view

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)