Skip to content

chore(deps): update rust crate jsonschema to 0.60.0 - #265

Merged
lomigmegard merged 1 commit into
mainfrom
renovate/jsonschema-0.x
Oct 31, 2026
Merged

lomigmegard merged 1 commit into
mainfrom
renovate/jsonschema-0.x

Conversation

@rite-ly-bot

@rite-ly-bot rite-ly-bot commented Oct 25, 2026 •

Copy link
Copy Markdown
Collaborator

This PR contains the following updates:

Package Type Update Change
jsonschema workspace.dependencies minor 0.59.0 → 0.60.0

Release Notes

Stranger6667/jsonschema (jsonschema)

v0.60.2

Fixed
  • Stack overflow when building validators for unevaluated* schemas with $ref cycles across $id resources.

v0.60.1

Fixed
  • Panic on numbers past f64 in const, enum, minimum, maximum, exclusiveMinimum, exclusiveMaximum and type: integer when another crate in the build enables serde_json/arbitrary_precision while the arbitrary-precision feature is off. #​1790
  • #[jsonschema::validator] panicking during expansion, or generating code that panics, on schema numbers past f64 when another crate in the build enables serde_json/arbitrary_precision while the arbitrary-precision feature is off. Such numbers are compile errors, as without that serde_json feature. #​1790
  • const, enum and uniqueItems treating objects with the same members in a different key order as unequal when another crate in the build enables serde_json/preserve_order. #​1791
  • Wrong results in type: integer, const, enum, uniqueItems, multipleOf, minimum, maximum, exclusiveMinimum and exclusiveMaximum for numbers with exponents past one million, such as 1e-2000000, with the arbitrary-precision feature.
  • #[jsonschema::validator] rejecting multipleOf with a positive divisor below the smallest f64, such as 1e-400, with the arbitrary-precision feature.
Performance
  • Validation of numbers with many digits or large exponents in const, enum, uniqueItems, type: integer, multipleOf, minimum, maximum, exclusiveMinimum and exclusiveMaximum with the arbitrary-precision feature taking time growing faster than the square of the digit count, instead of at most the square.
  • Validation of numbers with more than ten thousand digits, written or implied by their exponent, with the arbitrary-precision feature taking time linear in their written length instead of quadratic in their digit count.

v0.60.0

Changed
  • ValidationErrorKind::Enum and ValidationErrorKind::Constant holding their values as Arc<Value> shared with the validator, instead of a copy per error. #​1777
Performance
  • Validation with unfinished regex matches running each such match once instead of once per run, and comparing errors across runs in linear time instead of quadratic. #​1784
  • items and additionalProperties looking up a single-keyword subschema once per array or object instead of once per value.
  • is_valid and validate reading fewer cache lines per subschema, by keeping error locations apart from validators.
  • is_valid on recursive schemas caching only $ref results that took many steps to compute, instead of every one.
  • Error evaluation paths taking memory linear in the $ref nesting depth, not quadratic. #​1778

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@rite-ly-bot
rite-ly-bot force-pushed the renovate/jsonschema-0.x branch 3 times, most recently from 4fe6a27 to ae0b2ac Compare October 27, 2026 21:52
@rite-ly-bot
rite-ly-bot force-pushed the renovate/jsonschema-0.x branch from ae0b2ac to ad1d751 Compare October 31, 2026 06:26
@lomigmegard
lomigmegard merged commit 0df53b5 into main Oct 31, 2026
15 checks passed
@lomigmegard
lomigmegard deleted the renovate/jsonschema-0.x branch October 31, 2026 08:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants