v4.18.0a4

Full Changelog: v4.18.0a3...v4.18.0a4

v4.18.0a3

What's Changed

• fix: Python 3.11 date.fromisoformat() allows extra formats by @jvtm in #1076
• Do not validate for unevaluatedProperties by @ikonst in #1075

New Contributors

• @jvtm made their first contribution in #1076
• @ikonst made their first contribution in #1075

Full Changelog: v4.18.0a2...v4.18.0a3

v4.18.0a2

What's Changed

• documentation mistype fix by @aryanA101a in #1063

New Contributors

• @aryanA101a made their first contribution in #1063

Full Changelog: v4.18.0a1...v4.18.0a2

v4.18.0a1

What's Changed

This release majorly rehaul's the way in which JSON Schema reference resolution is configured.
It does so in a way that should be backwards compatible, preserving old behavior whilst emitting deprecation warnings.

jsonschema.RefResolver is now deprecated in favor of the new referencing library.
referencing will begin in beta, but already is more compliant than the existing $ref support.
This change is a culmination of a meaningful chunk of work to make $ref resolution more flexible and more correct.
Backwards compatibility should be preserved for existing code which uses RefResolver, though doing so is again now deprecated, and all such use cases should be doable using the new APIs.
Please file issues on the referencing tracker if there is functionality missing from it, or here on the jsonschema issue tracker if you have issues with existing code not functioning the same, or with figuring out how to change it to use referencing.

For full details see the new referencing documentation.

Further changes

• Support for Python 3.7 has been dropped, as it is nearing end-of-life.
  This should not be a "visible" change in the sense that requires-python has been updated, so users using 3.7 should still receive v4.17.3 when installing the library.
• A small number of type annotations have been improved
• On draft 2019-09, unevaluatedItems now properly does not consider items to be evaluated by an additionalItems schema if items is missing from the schema, as the specification says in this case that additionalItems must be completely ignored.

Deprecations

• jsonschema.RefResolver -- see above for details on the replacement
• jsonschema.RefResolutionError -- see above for details on the replacement
• importing jsonschema.ErrorTree -- instead import it via jsonschema.exceptions.ErrorTree
• importing jsonschema.FormatError -- instead import it via jsonschema.exceptions.FormatError

New Contributors

• @DanielNoord made their first contribution in #1021

Full Changelog: v4.17.3...v4.18.0a1

v4.17.3

• Fix instantiating validators with cached refs to boolean schemas
  rather than objects (#1018).
• Empty strings are not valid relative JSON Pointers (aren't valid under the
  RJP format).
• Durations without (trailing) units are not valid durations (aren't
  valid under the duration format). This involves changing the dependency
  used for validating durations (from isoduration to isodate).

Full Changelog: v4.17.2...v4.17.3

v4.17.1

• The error message when using unevaluatedProperties with a non-trivial
  schema value (i.e. something other than false) has been improved (#996).

Full Changelog: v4.17.0...v4.17.1

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

• Enable dedicated API documentation page(s) by @Julian in #989

Full Changelog: v4.14.0...v4.15.0

v4.14.0

• FormatChecker.cls_checks is deprecated. Use FormatChecker.checks on
  an instance of FormatChecker 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