Draft: Update dependency jsonschema to v4.21.1
This MR contains the following updates:
Package | Update | Change |
---|---|---|
jsonschema (changelog) | minor |
==4.17.3 -> ==4.21.1
|
All Renovate MRs are tracked by #222 (closed).
Release Notes
python-jsonschema/jsonschema (jsonschema)
v4.21.1
=======
- Slightly speed up the
contains
keyword by removing some unnecessary validator (re-)creation.
v4.21.0
=======
- Fix the behavior of
enum
in the presence of0
or1
to properly considerTrue
andFalse
unequal (#1208). - Special case the error message for
{min,max}{Items,Length,Properties}
when they're checking for emptiness rather than true length.
v4.20.0
=======
- Properly consider items (and properties) to be evaluated by
unevaluatedItems
(resp.unevaluatedProperties
) when behind a$dynamicRef
as specified by the 2020 and 2019 specifications. -
jsonschema.exceptions.ErrorTree.__setitem__
is now deprecated. More broadly, in general users ofjsonschema
should never be mutating objects owned by the library.
v4.19.2
=======
- Fix the error message for additional items when used with heterogeneous arrays.
- Don't leak the
additionalItems
keyword into JSON Schema draft 2020-12, where it was replaced byitems
.
v4.19.1
=======
- Single label hostnames are now properly considered valid according to the
hostname
format. This is the behavior specified by the relevant RFC (1123). IDN hostname behavior was already correct.
v4.19.0
=======
- Importing the
Validator
protocol directly from the package root is deprecated. Import it fromjsonschema.protocols.Validator
instead. - Automatic retrieval of remote references (which is still deprecated) now properly succeeds even if the retrieved resource does not declare which version of JSON Schema it uses. Such resources are assumed to be 2020-12 schemas. This more closely matches the pre-referencing library behavior.
v4.18.6
=======
- Set a
jsonschema
specific user agent when automatically retrieving remote references (which is deprecated).
v4.18.5
=======
- Declare support for Py3.12
v4.18.4
=======
- Improve the hashability of wrapped referencing exceptions when they contain hashable data.
v4.18.3
=======
- Properly preserve
applicable_validators
in extended validators. Specifically, validators extending early drafts where siblings of$ref
were ignored will properly ignore siblings in the extended validator.
v4.18.2
=======
- Fix an additional regression with the deprecated
jsonschema.RefResolver
and pointer resolution.
v4.18.1
=======
- Fix a regression with
jsonschema.RefResolver
based resolution when used in combination with a custom validation dialect (viajsonschema.validators.create
).
v4.18.0
=======
This release majorly rehauls 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 newreferencing library <https://github.com/python-jsonschema/referencing/>
_.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 usesRefResolver
, though doing so is again now deprecated, and all such use cases should be doable using the new APIs. Please file issues on thereferencing
tracker if there is functionality missing from it, or here on thejsonschema
issue tracker if you have issues with existing code not functioning the same, or with figuring out how to change it to usereferencing
. In particular, this referencing change includes a change concerning automatic retrieval of remote references (retrievinghttp://foo/bar
automatically within a schema). This behavior has always been a potential security risk and counter to the recommendations of the JSON Schema specifications; it has survived this long essentially only for backwards compatibility reasons, and now explicitly produces warnings. Thereferencing
library itself will not automatically retrieve references if you interact directly with it, so the deprecated behavior is only triggered if you fully rely on the default$ref
resolution behavior and also include remote references in your schema, which will still be retrieved during the deprecation period (after which they will become an error). - 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 receivev4.17.3
when installing the library. - On draft 2019-09,
unevaluatedItems
now properly does not consider items to be evaluated by anadditionalItems
schema ifitems
is missing from the schema, as the specification says in this case thatadditionalItems
must be completely ignored. - Fix the
date
format checker on Python 3.11 (when format assertion behavior is enabled), where it was too liberal (#1076). - Speed up validation of
unevaluatedProperties
(#1075).
Deprecations
-
jsonschema.RefResolver
-- see above for details on the replacement -
jsonschema.RefResolutionError
-- see above for details on the replacement - relying on automatic resolution of remote references -- see above for details on the replacement
- importing
jsonschema.ErrorTree
-- instead import it viajsonschema.exceptions.ErrorTree
- importing
jsonschema.FormatError
-- instead import it viajsonschema.exceptions.FormatError
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.