chore(deps): update rust crate jsonschema (0.49.9 → 0.58.1)

[atvik-renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
jsonschema	dependencies	minor	0.49 → 0.58	0.58.3 (+1)

---

Release Notes

Stranger6667/jsonschema (jsonschema)

v0.58.1

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.

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

v0.57.0

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.

v0.56.0

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

• BREAKING: canonical::CanonicalView::Raw carries a canonical::RawView in place of the document alone.
• Canonicalization of a oneOf whose branches share a region too wide to expand, which spent the document's whole intersection allowance on that choice and kept the document Raw.

Performance

• Preparing or building a schema that names no base URI parses the default one once for the process instead of once per schema.
• Canonicalizing several subschemas of one prepared document compiles each pattern once for the document instead of once per call.
• Canonicalization reads the facets no checker covers once per node instead of once per containment query.

v0.55.1

Changed

• Canonicalization of an anyOf over an allOf through a $ref to a union, which left that union nested inside the outer one.
• Canonicalization of an anyOf whose branch narrowing runs out of intersections, which left true as a branch inside the union.

v0.55.0

Changed

• BREAKING: canonical::ObjectViolationView gained the PatternValueFails variant, which negation records for a patternProperties entry.
• Canonicalization of not over patternProperties, which kept the entry under not instead of recording the demand a key breaks.
• Canonicalization of unevaluated* beside a conditional reaching no key or index the node already evaluates, which spent a case on it.
• Canonicalization of a conditional split outgrowing its per-node case budget, which kept documents like the Open API 3.2 meta-schema Raw.
• Canonicalization of an anyOf over objects sharing a properties key under patternProperties, which settled only on a second pass.
• Canonicalization of not over an allOf folded through a reference, which settled only on a second pass.
• Canonicalization of a multipleOf divisor past f64 precision, which was not taken to divide itself.
• Canonicalization of an anyOf over a value beside a window pinned to it, which settled only on a second pass.
• Canonicalization of minProperties: 1 beside a not that already demands a key, which settled only on a second pass.

Fixed

• absolute_keyword_location naming the sibling keyword whose validator carries the check: maxLength beside minLength, minItems, maxItems or type beside items, and a two-name required beside properties. #​1579
• schemaLocation in evaluate output naming minLength for a maxLength failure. #​1579

v0.54.0

Added

• backend = SerdeJson on #[jsonschema::validator], generating a validator that reads serde_json::Value.
• PreparedDocument::unsatisfiable_pointers, listing every subschema no value satisfies.

Changed

• Canonicalization of unevaluated* beside dependentSchemas or if/then/else, which kept the document Raw.
• Canonicalization of not over patternProperties, which kept the document Raw.

Performance

• validate and iter_errors check each assertion keyword with the is_valid path and build an error only for a failing one.
• evaluate holds its output tree in one allocation instead of one per node.
• A pattern of ^\S*$ scans bytes instead of decoding every character.
• validate on properties beside a two-name required confirms both names in the pass that checks the properties, instead of looking each up first.
• A string enum compares an option's length and first and last eight bytes before its full text.
• A JSON Pointer segment is scanned for ~ and / eight bytes at a time before it is copied.
• Canonicalization cloning leaves per intersection and the definition map per settled target.

Fixed

• type: array with items and minItems/maxItems checking the built-in length bound even when a custom keyword overrides minItems or maxItems, so the bound was evaluated twice.
• A custom keyword overriding type, required or maxLength not replacing the built-in check for that keyword.
• A custom keyword overriding items, minLength, properties or additionalProperties leaving its sibling keywords unchecked.
• #[jsonschema::validator] generated code that named serde_json directly, so it needed the consumer crate to depend on serde_json too.
• Canonicalization of not over an object with properties, patternProperties and additionalProperties, which applied additionalProperties to the keys listed in properties.

v0.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.
• 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.

v0.52.1

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.

v0.52.0

Added

• Evaluation::is_valid.
• Location::is_empty.
• Display for ErrorEntry.
• ValidationOptions::offline and canonical::CanonicalizeOptions::offline, refusing to fetch references outside the registry.
• idna Cargo feature, enabled by default, gating the idn-hostname and idn-email formats. #​1313
• CLI: the --offline flag of jsonschema validate, jsonschema bundle and jsonschema dereference.

Changed

• ValidationErrors' Display gained the instance path of each error.
• BREAKING: With default-features = false, the idn-hostname and idn-email formats now require the new idna feature. Without it they are unknown formats, which are accepted by default, or rejected at build time under should_ignore_unknown_formats(false). Add idna to the feature list to keep the previous behavior.

Fixed

• Canonicalization not idempotent where a patternProperties $ref matches a key properties names.
• is_valid disagreeing with validate, iter_errors, and evaluate on a schema that reaches its own $ref twice, one of them under not.
• format: email and format: idn-email rejecting an empty quoted string as the local part (it should be accepted).
• format: email and format: idn-email rejecting an address literal whose IPv6: tag is not written in that exact case (the tag is case-insensitive).
• format: email accepting a non-ASCII character in the local part (it should be rejected).
• ValidationOptions::with_draft gating keywords on the vocabularies of the $schema it overrides, so the validator accepted every instance.

Performance

• iter_errors collects into a single buffer instead of allocating and re-boxing an iterator at every schema node.

v0.51.0

Added

• ValidationOptions::with_vocabulary and the vocabularies attribute on jsonschema::validator, declaring support for a vocabulary this crate does not implement.
• The --vocabulary flag of jsonschema validate.

Changed

• Vocabulary gained the FormatAssertion variant, which its Draft 2020-12 URI parses to instead of Vocabulary::Custom, and is marked non_exhaustive.

Fixed

• The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
• The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
• A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected).
• The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
• A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
• A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
• The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
• The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
• The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
• Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

• Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

v0.50.1

Changed

• CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
• CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

• CanonicalSchema::negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
• CanonicalSchema::subtract dropping a Draft 4 array member an element demand partly takes.
• CanonicalSchema::covers answering Yes where a Draft 4 element demand refuses a member.
• A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

• not over a wide object schema costs its branch count instead of its square.
• not over an object schema is linear in its property count, not quadratic.
• not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

v0.50.0

Added

• CanonicalSchema::union and CanonicalSchema::subtract.
• CanonicalizationError::UnsupportedResult, reported where the canonical form does not support a set operation's result.
• OperandMismatch::DocumentRoots, reported where both operands read # and it names a different document on each side.
• CLI: jsonschema validate -i INSTANCE without a SCHEMA argument validates each instance against the schema named in its own $schema property. #​1470

Changed

• CanonicalSchema::is_satisfiable is now CanonicalSchema::satisfiability, answering Yes, No, or Unknown - Yes wherever a value can be exhibited, not only for the forms listing their members.
• CanonicalSchema::covers decides through the difference as well: No where the argument keeps values the receiver rejects, Yes where nothing is left over.
• CanonicalSchema::is_subset_of is now CanonicalSchema::covers, answering Yes, No, or Unknown for whether the receiver admits every value the argument admits.
• CanonicalSchema::negate returns Result rather than Option.
• CanonicalizationError::UnmodeledOperand is now CanonicalizationError::UnsupportedOperand, and means only that an operand is a Raw pass-through.
• A conjunction over a $ref folds through the body it names, so canonicalizing a document and combining its parts with the set operations reach one form; a document holding a reference cycle keeps the form it had.

Fixed

• Combining nodes of two different documents repointing a $ref to # at the combined result instead of the document it was written in, including one named by a definition the result keeps.
• Intersecting a $ref whose target is true or false, which panicked.
• A key constraint left un-narrowed once a run is out of intersections, which panicked on the next read of it.
• CanonicalSchema::covers answering Unknown for a schema against itself, where that schema is a $ref.
• CanonicalSchema::union keeping a $ref beside the schema it names, where the other three operations read through it.
• CanonicalSchema::covers and CanonicalSchema::subtract cancelling two nodes written the same way whose # names a different document.
• Two results accepting the same values comparing unequal over the part of their documents neither reads.
• additionalProperties reaching a key the pattern map matches when a finite key constraint closes the map, which dropped values both operands accept.
• A recursive definition stopping every other pointer in the document from being read through.
• One $defs entry read past a wider schema written out at every use, rather than kept as the pointer it was.
• Set operations rejecting one document canonicalized twice, and a pruned result rejected against the document it came from, where the maps resolve every shared reference the same way.
• Set operations comparing a $ref as a pointer instead of reading through it, so a schema written with a $ref did not cancel against the same schema written out.
• CanonicalSchema::subtract asking for a complement where the difference is one of the operands or empty, declining on schemas it can subtract.
• Set operations keeping $defs entries the result no longer references, which then showed up in the emitted schema.
• CanonicalSchema::union declining over an approximated intersection, where the union itself is exact.
• Resolving a reference against a base URI that carries a fragment, which happens when a Draft 4-7 $id contains one. #​1473
• unevaluatedProperties and unevaluatedItems ignoring an $id on a subschema they walk through, so a relative $ref inside it resolved against the enclosing resource.

Performance

• CLI: ~25% less CPU per run from compile-time meta-schema validators.

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[atvik-renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: crates/domarinn-core/Cargo.toml

Artifact update for jsonschema resolved to version 0.58.2, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.58.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/