[Rust] Release 0.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.

[Ruby] Release 0.46.0

Added

• Accept JSON strings in validator_cls_for.
• Resolver and Resolved types for programmatic schema resolution.
• dereference function to recursively inline $ref references. #422
• ValidatorMap for validating instances against subschemas identified by URI-fragment JSON pointer. #1075

Performance

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

[Python] Release 0.46.0

Added

• Accept JSON strings in validator_cls_for.
• Resolver and Resolved types for programmatic schema resolution.
• dereference function to recursively inline $ref references. #422
• ValidatorMap for validating instances against subschemas identified by URI-fragment JSON pointer. #1075

Fixed

• Compilation error on wasm32 targets. #1093

Performance

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

[Rust] Release 0.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.

[Ruby] Release 0.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.

[Python] Release 0.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.

[Rust] Release 0.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.

[Ruby] Release 0.45.0

Added

• JSONSchema.bundle(schema, ...): produce a Compound Schema Document with all external $ref targets embedded in a draft-appropriate container (definitions for Draft 4/6/7, $defs for Draft 2019-09/2020-12; Appendix B). #791.
• ValidationError#absolute_keyword_location to get the absolute keyword location URI of the schema node that produced the error.

[Python] Release 0.45.0

Added

• bundle(schema, ...): produce a Compound Schema Document with all external $ref targets embedded in a draft-appropriate container (definitions for Draft 4/6/7, $defs for Draft 2019-09/2020-12; Appendix B). #791.
• ValidationError.absolute_keyword_location to get the absolute keyword location URI of the schema node that produced the error.

[Rust] Release 0.44.1

Fixed

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