Update dependency jsonschema-rs to ^0.56.0

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
jsonschema-rs (changelog)	^0.29.0 → ^0.56.0

---

Release Notes

Stranger6667/jsonschema (jsonschema-rs)

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.

v0.49.9

Added

• Canonicalization of a oneOf whose branches name object targets a required constant tells apart, which degrades to a union.

Changed

• CanonicalSchema::to_json_schema on a definition emits only the definitions that one names, not the whole document's.

Fixed

• Canonicalization running without end on a conjunction over unions; past a ceiling on the meets it takes, the document stays unmodeled.

v0.49.8

Performance

• Up to 380x faster canonicalization of a oneOf whose overlapping branches carry many properties, which no longer removes shared regions the exactly-one spelling discards.

Fixed

• Draft detection treating the version-less http://json-schema.org/schema meta-schema URI as a custom dialect, where it names the current draft.
• A patternProperties entry matching every key leaving additionalProperties: false spelled as a key constraint, where it forbids nothing.
• unevaluatedProperties/unevaluatedItems set to true forcing the whole document to stay unmodeled beside an unresolved applicator, where the keyword rejects nothing regardless of the evaluated set.
• unevaluatedProperties/unevaluatedItems beside a $ref forcing the whole document to stay unmodeled, where the reference's own evaluated properties or items are known once it is resolved.

v0.49.7

Added

• CanonicalizeOptions::with_retriever to fetch external resources absent from the registry.
• CanonicalizeOptions::with_base_uri to resolve relative references in the root schema.
• Canonicalization of a oneOf whose branches name disjoint targets, which degrades to a union.
• Canonicalization of a vacuous patternProperties entry beside schema-valued additionalProperties, where matching keys escape its value constraint.
• Canonicalization of a Draft 4 closed pattern map with a reference nested under a property.
• Canonicalization of Draft 4 closed pattern maps that meet through an applicator.
• The complement of a reference back to a target already being negated, which stays symbolic instead of declining.
• CanonicalSchema::definition resolving # to the document the handle was read against.

Performance

• Up to 150x faster canonicalization of not over a union of many branches.
• 2% faster emission of canonical schemas, which no longer formats copied string values.
• 5% faster emission of canonical schemas, which no longer formats object keys while copying them.
• Up to 12% faster canonicalization of schemas that repeatedly intersect the same branches.
• 13% faster canonicalization of a non-dynamic OpenAPI document, which no longer scans every schema object for dynamic references.
• Faster canonicalization of schemas with local $defs references, which avoid decoding unescaped definition names.
• 23% faster canonicalization of an object whose keys a finite property-name set spells.
• 3% faster intersection of schemas where one side constrains nothing.
• Up to 31x faster canonicalization of a oneOf whose many branches overlap.
• Up to 14x faster canonicalization of a union whose object branches share no values.
• 7% faster canonicalization of schemas that reach the same pair of nodes repeatedly.
• 5% faster canonicalization of objects, whose property maps no longer reach the allocator.
• Up to 8% faster canonicalization of schemas that reach true and false subschemas repeatedly.
• 2% faster canonicalization of schemas that assert known string formats.

Fixed

• CanonicalSchema::definition and CanonicalSchema::definitions handing out a target that names the document root without that document, where # points at the target instead.
• An items tail beyond an array's length ceiling surviving canonicalization, where it governs no element.
• CanonicalSchema::to_json_schema leaving the document root out of a node emitted below it, where # points at that node instead.

v0.49.6

Added

• Canonicalization of a negated uniqueItems, where the complement demands a repeated element under the length floor two elements imply.
• Canonicalization of a negated array tuple, where each position's complement stands under the length that reaches it.
• Canonicalization of contains demands sharing no value, where their counts add up into a length floor.
• CanonicalSchema::negate through references, where the complement of the resolved target takes the reference's place.
• Canonicalization of negated propertyNames and additionalProperties, where the complement spells the violating-key demand instead of a not residual.
• Canonicalization of negated additionalProperties under Draft 4, where the violating-key demand spells the closed property map.
• Canonicalization of not a reference, where the complement of the resolved target takes the pointer's place.
• Canonicalization of a negated oneOf, where the complement spells the values no branch admits beside the values two branches share.
• Canonicalization of negated items under Draft 4, where the violating-element demand spells the barred element schema.

Changed

• ArrayView reports distinctness in three states, so an array demanding a repeated element reads apart from one demanding distinct elements.

Fixed

• CanonicalSchema::negate keeping a root self-reference in the complement, where it points at the complement instead of the source.
• An additionalItems that tails no tuple keeping the whole document unmodeled under Draft 2020-12.

v0.49.5

Added

• Canonicalization of not an integer schema under Draft 4, which the number leaf carries as barred integers.
• Canonicalization of not a multipleOf, which numeric leaves carry as barred divisors.
• Canonicalization of not an integer schema, where a barred divisor of one spells the non-integer numbers.
• Canonicalization of not a pattern, which string leaves carry as barred patterns.
• Canonicalization of not a typed value set under Draft 4, such as {"type": "integer", "enum": [1, 2]}.
• CanonicalSchema::is_subset_of, whether the other schema admits every value this one admits.
• Canonicalization of a reference cycle carrying no assertion, which admits every value.

Fixed

• CanonicalSchema::is_subset_of failing to prove a union of array branches a subset of itself.
• CanonicalSchema::intersect admitting values one side rejects when its additionalProperties governs the keys the other side's patternProperties match.
• A satisfiable multipleOf schema collapsing to the empty set when f64 rounds its bounds together.
• Two spellings of one number canonicalizing to different texts under arbitrary-precision when the fraction exceeds the expansion cap.
• Numeric bounds and multipleOf comparing values through a lossy f64 conversion under arbitrary-precision, such as 1e-400 passing {"maximum": 0}.
• A union branch left unabsorbed when a sibling complement shed a conjunct from another branch.
• A union keeping an integer branch beside a number branch that admits every value of it.

v0.49.4

Added

• Canonicalization of not a string format, which the string leaf carries as barred formats.
• Canonicalization of not an existential demand, which an array fails exactly when no element matches.
• Canonicalization of not a string value set, which the string leaf carries as excluded values.
• Canonicalization of unevaluatedItems beside contains, where the elements it matches are evaluated and the tail admits either.
• Canonicalization of unevaluated* beside anyOf or oneOf, where every branch evaluating the same keys or indexes pins what is left over.
• Canonicalization of not an array element schema, which an array fails exactly when one element violates it.
• CanonicalSchema::intersect, the values both schemas admit.
• CanonicalSchema::negate, the values a schema rejects.
• CanonicalSchema::definition, one reference target by URI.

Fixed

• An integer past i64 admitted by a fractional bound f64 rounds it onto, such as -10000000000000000000000000 under {"maximum": -10000000000000000000000000.1}.
• An integer past 2^53 admitted by a bound f64 rounds onto it, such as 9007199254740992 under {"minimum": 9007199254740993}.
• A contains subschema beside both minContains and maxContains overwriting a sibling keyword of the same name, such as items.

Performance

• CanonicalSchema hashing and equality cost the node instead of the whole document.

v0.49.3

Added

• Canonicalization of a recursive schema with no finite witness, which now folds to false.
• Canonicalization of $dynamicRef and $recursiveRef, which resolve through the dynamic scope and stay symbolic like any other reference. A dangling $dynamicRef errors rather than staying Raw.
• Canonicalization of minContains under uniqueItems, where a demand asking for more matches than its own schema has distinct values now folds to false.
• Canonicalization of a Draft 4 patternProperties coverage closed by additionalProperties: false, spelled as the closed map it was parsed from.
• Canonicalization of a oneOf whose branches repeat, where a repeated branch can never contribute exactly one match.
• Canonicalization of a $ref whose target is an empty schema, which now folds to false.
• Canonicalization of unevaluatedItems beside allOf, where every branch must pass and so the indexes they evaluate are known without the instance.
• Canonicalization of unevaluatedProperties beside allOf, where every branch must pass and so what they evaluate is known without the instance.
• Canonicalization of a Draft 4 type list holding integer beside other types with enum, which previously modeled only when spelled as an allOf.
• Canonicalization of patternProperties patterns matching finitely many keys, such as ^a$ and ^(a|b)$.
• Canonicalization of unevaluatedProperties and unevaluatedItems when no in-place applicator sits beside them.

Fixed

• additionalItems values that are not schemas silently ignored beside an array-form items (they should fail the build like additionalProperties).
• additionalItems beside a boolean items rejecting every instance, such as {"additionalItems": false, "items": false}.
• additionalItems beside a non-array items value failing schema compilation with an error blaming additionalItems (the keyword should be ignored).
• Draft 4 rejecting a size bound at or past 2^64, such as {"maxItems": 18446744073709551616}.
• An integer past the f64 range admitted by a fractional bound it exceeds, such as 1e400 under {"exclusiveMaximum": 0.1}.
• A $ref at the root of an $id-bearing subresource dropped as a self-reference when its pointer matched the one that reached that subresource.
• Canonicalization reusing one definition's body for a same-named definition in another resource, when the name spells a canonical URI.
• unevaluatedItems counting prefixItems as evaluating elements before Draft 2020-12, where it is not a keyword.

Performance

• Up to 70% faster evaluate by building each location in a single allocation instead of two, reusing the instance location a node already built, and caching evaluation paths across instance nodes.

v0.49.2

Performance

• Faster serialization of canonicalized schemas.
• Faster macro code generation for subschemas with many keywords.
• Up to 70x faster canonicalization of multipleOf beside numeric bounds far from zero.

v0.49.1

Fixed

• jsonschema-value: Ruby builds on x64-mingw-ucrt.

v0.49.0

Added

• Generic JSON input: options_for builds a validator over any instance representation implementing json::Json, so instances validate without conversion to serde_json::Value. #​239
• meta::validate_for and meta::is_valid_for for checking a schema document held in any representation implementing json::Json against its meta-schema.
• EXPERIMENTAL: Schema canonicalization via jsonschema::canonicalize. It reduces a reasonable subset of JSON Schemas to their normal forms.

Fixed

• multipleOf incorrectly accepted integers past u64 that are not multiples of the divisor.

v0.48.5

Fixed

• Packaging issue again.

v0.48.2

Performance

• Faster validator compilation by pre-sizing internal caches.

v0.48.1

Fixed

• Missing required errors in evaluate() output for schemas with properties and a two-entry required array. #​1220
• contentEncoding errors for invalid UTF-8 after decoding incorrectly had empty instance_path and schema_path.

Performance

• Faster code generation for #[jsonschema::validator] (~5% across benchmarked schemas), via aliasing repeated paths in the emitted code.

v0.48.0

Added

• iter_errors for #[jsonschema::validator]-generated validators.

Fixed

• Per-branch context on generated anyOf and oneOf validation errors, matching runtime validators.
• $recursiveRef in generated validators incorrectly resolved to the innermost $recursiveAnchor (it should resolve to the outermost one).
• Integer instances just outside the i64/u64 range incorrectly compared against numeric bounds through lossy f64 rounding under arbitrary-precision (e.g. {"minimum": -9223372036854775808} accepted -9223372036854775809).

Changed

• One canonical number spelling from canonical::json::to_string under arbitrary-precision ("1e-2" becomes "0.01", "1.50" becomes "1.5") and correctly-rounded float parsing (serde_json's float_roundtrip).

Performance

• Faster multipleOf validation for integer instances with integer divisors, via integer arithmetic instead of floating-point modulo.

v0.47.0

Added

• #[jsonschema::validator] attribute macro (behind the macros feature) that compiles a JSON Schema into is_valid and validate implementations at build time.
• Keyword::iter_errors for reporting multiple validation errors from a single custom keyword. #​1071

Changed

• Bump MSRV to 1.85.0.

Performance

• Faster meta-schema validation and schema compilation with the macros feature, via compile-time meta-schema validators.

Fixed

• type under items asserted with the Validation vocabulary disabled.
• Disabled vocabularies ignored for $ref targets without their own $schema (e.g. $defs entries).

v0.46.10

Fixed

• Stack overflow with a self-referential $dynamicRef combined with unevaluatedProperties or unevaluatedItems.
• Incorrect unevaluatedProperties and unevaluatedItems results when a meta-schema disables the Applicator vocabulary.

v0.46.9

Fixed

• multipleOf incorrectly rounds integer instances above 2^53 to f64 before the divisibility check on builds without the arbitrary-precision feature.
• Stack overflow while preparing a registry containing deeply nested schema documents.

v0.46.8

Fixed

• idn-email format rejected non-ASCII characters in quoted local parts (e.g. "δοκιμή"@example.com).

v0.46.7

Fixed

• idn-hostname format accepted A-labels that decode to a disallowed code point (e.g. xn--7a).

v0.46.6

Added

• IntoRegistryResource for Arc<Value>. #​1129

Fixed

• prefixItems incorrectly recognised as a known keyword in Draft 2019-09 and earlier (it is 2020-12 only).
• pattern validation errors displayed the internally translated regex instead of the original schema pattern. #​1149

v0.46.5

Fixed

• Percent-encoded characters in $ref URI fragments (e.g. #/$defs/Request%20class) are now decoded when stored as schema_path.

v0.46.4

Fixed

• Panic in the regex engine when matching against patterns with very large {0,N} quantifiers.

v0.46.3

Fixed

• Memory not reclaimed when a Validator for a schema with recursive $ref or $dynamicRef is dropped. #​1125
• Compilation failure on wasm32-wasip1 and wasm32-unknown-emscripten targets.

v0.46.2

Fixed

• required not enforced when additionalProperties is a schema object and required lists exactly 2 keys.

v0.46.1

Fixed

• Stack overflow with a self-referential $dynamicRef combined with unevaluatedProperties or unevaluatedItems.
• Incorrect unevaluatedProperties and unevaluatedItems results when a meta-schema disables the Applicator vocabulary.

v0.46.0

Added

• ValidatorMap for validating instances against subschemas identified by URI-fragment JSON pointer. #​1075
• CLI: Accept multiple values after -i/--instance (e.g. jsonschema validate schema.json -i *.json). #​1085
• dereference function to recursively inline $ref references. #​422
• CLI: jsonschema dereference subcommand to dereference a schema from the command line.

Breaking Changes

• Registry construction now uses an explicit prepare step, and with_registry now borrows the prepared registry. ValidationOptions::with_resource and ValidationOptions::with_resources were removed in favor of building a Registry first. See the Migration Guide for the details.

Performance

• Avoid registry clones and document clones during validator construction. This improves real-world schema compilation by roughly 10-20% in internal benchmarks.

v0.45.1

Fixed

• Incorrect handling of multipleOf validation for negative numeric instances.
• Incorrect handling of duration format when hours and seconds appear without minutes, or years and days without months.

v0.45.0

Added

• bundle(schema) / async_bundle(schema) / ValidationOptions::bundle: produce a Compound Schema Document with external $ref targets embedded in a draft-appropriate container (definitions for Draft 4/6/7, $defs for Draft 2019-09/2020-12) while preserving $ref values. #​791.
• CLI: jsonschema validate and jsonschema bundle subcommands. Flat invocation (jsonschema schema.json -i …) is deprecated — use jsonschema validate instead. #​791.
• ValidationError::absolute_keyword_location() to get the absolute keyword location URI of the schema node that produced the error. #​737.

Changed

• ValidationError::into_parts() now returns ValidationErrorParts instead of a tuple.

v0.44.1

Fixed

• hostname format now applies legacy RFC 1034 semantics in Draft 4/6 and keeps IDNA A-label validation in Draft 7+.

v0.44.0

Added

• canonical::json::to_string(value) for canonical JSON serialization (stable key ordering and numeric normalization), useful for deduplicating equivalent JSON Schemas.

Fixed

• Do not produce annotations for non-string instances from contentMediaType, contentEncoding, and contentSchema keywords.

v0.43.0

Performance

• Optimize pattern and patternProperties for ^(a|b|c)$ alternations via linear array scan.
• Optimize ^\S*$ patterns by replacing regex with a direct ECMA-262 whitespace check.

Fixed

• anyOf, format, unevaluatedProperties, and unevaluatedItems now correctly collect annotations per spec.

v0.42.2

Fixed

• SWAR digit parser accepted bytes :–? (0x3A–0x3F) as valid digits during date, time, and date-time format validation, potentially allowing malformed values to pass.

Performance

• Extend pattern prefix optimization to handle escaped slashes (^\/) and exact-match patterns (^\$ref$).
• Specialize enum for cases when all variants are strings.

v0.42.1

Performance

• Reduce dynamic dispatch overhead for non-recursive $ref resolution.
• Cache ECMA regex transformations during format: "regex" validation.

v0.42.0

Added

• JsonType::as_str method for zero-allocation type name access.
• ValidationErrorKind::keyword is now public.
• tls-ring feature flag to opt into using ring as the TLS crypto provider instead of the default aws-lc-rs. #​997
• CLI: Support YAML (.yaml/.yml) instance files in text output mode. #​988

Changed

• BREAKING: Default TLS crypto provider switched back to aws-lc-rs. Users who need ring can opt in via the tls-ring feature flag. This resolves potential conflicts with other libraries using aws-lc-rs. #​997

Fixed

• Panic when validating $ref targets that resolve to boolean schemas.

Performance

• Cache formatted schema locations with OnceLock to avoid repeated formatting during evaluate().

v0.41.0

Performance

• Replace regex-based uri-template format validation with a hand-rolled RFC 6570 parser.
• Specialize items keyword for simple type schemas ({"type": "string"}, {"type": "number"}, etc.) to eliminate dynamic dispatch overhead.
• Precompute regex matches on known properties.
• Faster unevaluatedProperties validation via O(1) property lookup and short-circuit oneOf evaluation.
• Use HashMap for large set of properties.
• Lower HashMap threshold from 40 to 15 properties for faster property lookups.

v0.40.2

Changed

• Exclude internal tracker field from ValidationError Debug output.
• Switch HTTP client TLS crypto backend from aws-lc-rs to ring to simplify building from source on some Linux distributions. #​957

Fixed

• type: integer validation in Draft 4 now correctly accepts large integers outside the i64/u64 range when arbitrary-precision feature is enabled.

v0.40.1

Changed

• ValidationErrorKind::Custom now includes a keyword field containing the custom keyword name.

Performance

• Faster validation via cost-based keyword ordering.
• Faster patternProperties for simple prefix patterns (e.g., ^x-).

v0.40.0

Added

• HttpOptions and ValidationOptions::with_http_options() for configuring HTTP client behavior (timeouts, TLS verification, custom CA certificates) when fetching external schemas.
• CLI: --timeout, --connect-timeout, --insecure, and --cacert flags for HTTP configuration.

v0.39.0

Added

• ValidationError::evaluation_path() for the dynamic path including $ref traversals.

Changed

• BREAKING: Simplified custom keyword API - Keyword::validate no longer receives path parameters, and ValidationError::custom only takes a message.

Fixed

• schemaLocation in evaluation output now excludes $ref/$dynamicRef/$recursiveRef per JSON Schema spec.

Performance

• evaluate(): 4.5-30x faster on complex schemas, 12-89% faster overall.
• Recursive schemas with oneOf/anyOf: ~4000x faster via memoization. #​930

v0.38.1

Fixed

• multipleOf validation for integer values between 2^53 and i64::MAX with arbitrary-precision feature.

v0.38.0

Added

• EmailOptions for configuring email format validation. #​903

Fixed

• Use-after-free in async $ref resolution when multiple refs target the same external URL with different fragments. #​906
• multipleOf validation for large u64 values beyond i64::MAX with arbitrary-precision feature.
• Validator not being Send + Sync on WASM targets. #​915

v0.37.4

Fixed

• Stack overflow during validation of schemas with circular $ref chains (e.g., a -> b -> a).
• Local $ref resolution within fragment-extracted external resources. #​892

Removed

• Deprecated PrimitiveType & PrimitiveTypesBitMap.

v0.37.3

Fixed

• External resources not discovered within subresources of local $ref targets. #​892

v0.37.2

Added

• JsonTypeSet::len() and JsonTypeSet::remove() helpers for managing type sets.

Fixed

• External resources not discovered through chained local $ref references. #​892

v0.37.1

Fixed

• Stack overflow on empty $ref value. #​886

v0.37.0

Added

• evaluate() top-level function for convenient access to structured validation output.
• CLI: Schema-only validation now also validates all referenced schemas. #​804
• Support for additional contentEncoding values per RFC 4648: base64url, base32, base32hex, and base16. These encodings are now validated alongside the existing base64 support in Draft 6 and 7. #​26
• validator.iter_errors(instance).into_errors(). It returns a ValidationErrors type that collects validation errors and implements std::error::Error. #​451

Changed

• BREAKING: ValidationError fields are private; use instance(), kind(), instance_path(), and schema_path() instead of accessing struct fields directly.
• BREAKING: ErrorIterator is now a newtype wrapper instead of Box<dyn ValidationErrorIterator>.

Performance

• validate and other APIs returning Result<_, ValidationError> are 5–10% faster in some workloads due to the smaller error handle.
• evaluate: Avoiding deep clones of unmatched keyword values (e.g., title, description, examples) on every schema node evaluation by using Arc internally. Can be multiple times faster for schemas with large annotations.

v0.36.0

Added

• CLI: Structured --output flag|list|hierarchical modes now stream newline-delimited JSON records with schema/instance metadata plus JSON Schema Output v1 payloads (default text output remains human-readable).
• CLI: --errors-only flag to suppress successful validation output and only show failures.
• CLI: When invoked with only a schema file (no instances), validates the schema against its meta-schema. #​804
• New Validator::evaluate() API exposes JSON Schema Output v1 (flag/list/hierarchical) reports along with iterator helpers for annotations and errors.
• meta::validator_for() function to build validators for meta-schema validation with full Validator API access.
• Validator now implements Clone. #​809

Removed

• Validator::apply(), Output, and BasicOutput types have been removed in favor of the richer evaluate() API.

v0.35.0

Added

• Support for custom meta-schemas. Schemas with custom $schema URIs can now be used by registering their meta-schemas in the Registry via jsonschema::options().with_registry(). #​664
• arbitrary-precision feature for exact numeric validation of large integers and decimals beyond standard floating-point limits. #​103
• Support for HTTPS $schema URIs for drafts 04, 06, and 07 (e.g., https://json-schema.org/draft-07/schema). #​802

Changed

• BREAKING: meta::is_valid now panics for unknown $schema values instead of defaulting to Draft 2020-12. meta::validate returns an error for unknown $schema values. Use meta::options().with_registry() to validate schemas against custom meta-schemas.
• BREAKING: Resource::from_contents no longer returns Result and always succeeds, since draft detection no longer fails for unknown $schema values.

Removed

• BREAKING: meta::try_is_valid and meta::try_validate. Use meta::is_valid and meta::validate instead.
• BREAKING: primitive_type module (deprecated since 0.30.0). Use jsonschema::types instead.

Performance

• required: short-circuit when the instance object has fewer properties than required keys.

v0.34.0

Changed

• BREAKING: BasicOutput and Annotations no longer have lifetime parameters. Update type annotations from BasicOutput<'a> to BasicOutput and Annotations<'a> to Annotations.
• referencing: URI caching now avoids hash collisions and reduces lock contention.
• Update fluent-uri to 0.4.1.
• Bump MSRV to 1.83.0.
• Drop the Send + Sync bounds from Retrieve/AsyncRetrieve on wasm32.
• Use the new draftX::meta::validator() helper so meta-schema validators lazy-init on wasm32 while native targets keep borrowing the cached jsonschema::meta::MetaValidator.

Fixed

• Hostname and IDN hostname formats now decode xn-- labels, reject leading combining marks/uppercase prefixes, and enforce the latest JSON Schema punycode context rules.
• Restore wasm32-unknown-unknown support. #​785

Performance

• apply now reuses cached schema locations, URI fragments, and buffers for up to ~2.5x faster validation.
• Recursive and regular $ref compilation deduplicates validator nodes, which decreases the memory usage and improves performance.
• Validator compilation restores the regex cache for faster builds on regex-heavy schemas and precomputes absolute schema locations, trading a bit of compile time for faster apply on location-heavy workloads.
• Large schema compilation is significantly faster. #​755
• unevaluatedProperties validation is 25-35% faster through optimized property marking and early-exit paths.
• unevaluatedProperties memory usage drastically reduced by eliminating redundant registry clones during compilation.
• unevaluatedItems validation is ~10% faster through early-exit optimizations and eliminating redundant validations in combinators.

Removed

• BREAKING: Validator::config to reduce the memory footprint.
• BREAKING: Public DRAFT4_META_VALIDATOR, DRAFT6_META_VALIDATOR, DRAFT7_META_VALIDATOR, DRAFT201909_META_VALIDATOR, and DRAFT202012_META_VALIDATOR statics. Use draftX::meta::validator() helper functions instead (e.g., draft7::meta::validator()).

v0.33.0

Fixed

• BREAKING: instance_path segments are now unescaped when iterating. LocationSegment::Property now holds Cow<'_, str> and LocationSegment is no longer Copy. #​788

v0.32.1

Changed

• Bump fancy-regex to 0.16.

v0.32.0

Added

• Added missing context field to ValidationErrorKind::OneOfMultipleValid.

Changed

• Improved error message for enum.

v0.31.0

Added

• CLI: flag -d, --draft <4|6|7|2019|2020> to enforce a specific JSON Schema draft.
• CLI: flags --assert-format and --no-assert-format to toggle validation of format keywords.
• Added context for ValidationErrorKind::AnyOf and ValidationErrorKind::OneOfNotValid which contains errors for all subschemas, each inside a separate vector with an index matching subschema ID.

Fixed

• Improve the precision of multipleOf for float values.

Changed

• Bump fancy-regex to 0.15.

v0.30.0

Added

• Support for custom meta-schemas. Schemas with custom $schema URIs can now be used by registering their meta-schemas in the Registry via jsonschema::options().with_registry(). #​664
• arbitrary-precision feature for exact numeric validation of large integers and decimals beyond standard floating-point limits. #​103
• Support for HTTPS $schema URIs for drafts 04, 06, and 07 (e.g., https://json-schema.org/draft-07/schema). [#​802](https://redirect.github.com/Stranger6667/jsonsche

❗ Important

✂ PR body was truncated to here.

---

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 was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.