Releases: python-jsonschema/jsonschema
Releases · python-jsonschema/jsonschema
v4.17.0
- The check_schema method on jsonschema.protocols.Validator instances now enables format validation by default when run. This can catch some additional invalid schemas (e.g. containing invalid regular expressions) where the issue is indeed uncovered by validating against the metaschema with format validation enabled as an assertion.
- The jsonschema CLI (along with jsonschema.cli the module) are now deprecated. Use check-jsonschema instead, which can be installed via pip install check-jsonschema and found here.
- Make ErrorTree have a more grammatically correct repr.
Full Changelog: v4.16.0...v4.17.0
v4.16.0
- Improve the base URI behavior when resolving a
$ref
to a resolution URI
which is different from the resolved schema's declared$id
. - Accessing
jsonschema.draftN_format_checker
is deprecated. Instead, if you
want access to the format checker itself, it is exposed as
jsonschema.validators.DraftNValidator.FORMAT_CHECKER
on any
jsonschema.protocols.Validator
.
Full Changelog: v4.15.0...v4.16.0
v4.15.0
What's Changed
Full Changelog: v4.14.0...v4.15.0
v4.14.0
FormatChecker.cls_checks
is deprecated. UseFormatChecker.checks
on
an instance ofFormatChecker
instead.unevaluatedItems
has been fixed for draft 2019. It's nonetheless
discouraged to use draft 2019 for any schemas, new or old.- Fix a number of minor annotation issues in
protocols.Validator
Full Changelog: v4.13.0...v4.14.0
v4.13.0
- Add support for creating validator classes whose metaschema uses a different
dialect than its schemas. In other words, they may use draft2020-12 to define
which schemas are valid, but the schemas themselves use draft7 (or a custom
dialect, etc.) to define which instances are valid. Doing this is likely
not something most users, even metaschema authors, may need, but occasionally
will be useful for advanced use cases.
Full Changelog: v4.12.1...v4.13.0
v4.12.1
v4.12.0
- Warn at runtime when subclassing validator classes. Doing so was not
intended to be public API, though it seems some downstream libraries
do so. A future version will make this an error, as it is brittle and
better served by composing validator objects instead. Feel free to reach
out if there are any cases where changing existing code seems difficult
and I can try to provide guidance.
Full Changelog: v4.11.0...v4.12.0
v4.11.0
What's Changed
Full Changelog: v4.10.3...v4.11.0
v4.10.3
jsonschema.validators.validator_for
now properly uses the explicitly
provided default validator even if the$schema
URI is not found.
Full Changelog: v4.10.2...v4.10.3
v4.10.2
- Fix a second place where subclasses may have added attrs attributes (#982).
Full Changelog: v4.10.1...v4.10.2