* Improve ``best_match`` (and thereby error messages from ``jsonschema.validate``) in cases where there are multiple *sibling* errors from applying ``anyOf`` / ``allOf`` -- i.e. when multiple elements of a JSON array have errors, we now do prefer showing errors from earlier elements rather than simply showing an error for the full array (1250). * (Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as ``==`` would.
4.21.1
=======
* Slightly speed up the ``contains`` keyword by removing some unnecessary validator (re-)creation.
4.21.0
=======
* Fix the behavior of ``enum`` in the presence of ``0`` or ``1`` to properly consider ``True`` and ``False`` unequal (1208). * Special case the error message for ``{min,max}{Items,Length,Properties}`` when they're checking for emptiness rather than true length.
4.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 of ``jsonschema`` should never be mutating objects owned by the library.
4.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 by ``items``.
4.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.