Pin jsonschema to latest version 4.21.1

[pyup-bot]

This PR pins jsonschema to the latest release 4.21.1.

Changelog

4.21.1

<!-- Release notes generated using configuration in .github/release.yml at v4.21.1 -->



**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.21.0...v4.21.1

4.21.0

<!-- Release notes generated using configuration in .github/release.yml at v4.21.0 -->

What's Changed
* 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.

New Contributors
* otto-ifak made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/1208

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.20.0...v4.21.0

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.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.19.2...v4.20.0

4.19.2

<!-- Release notes generated using configuration in .github/release.yml at 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 by `items`.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.19.1...v4.19.2

4.19.1

<!-- Release notes generated using configuration in .github/release.yml at v4.19.1 -->

What's Changed
* Allow single label hostname in format string by swaeberle in https://github.com/python-jsonschema/jsonschema/pull/1164

New Contributors
* swaeberle made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/1164

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.19.0...v4.19.1

4.19.0

<!-- Release notes generated using configuration in .github/release.yml at v4.19.0 -->

* Importing the `Validator` protocol directly from the package root is deprecated. Import it from `jsonschema.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.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.6...v4.19.0

4.18.6

<!-- Release notes generated using configuration in .github/release.yml at v4.18.6 -->



**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.5...v4.18.6

4.18.5

<!-- Release notes generated using configuration in .github/release.yml at v4.18.5 -->

* Declare support for Py3.12

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.4...v4.18.5

4.18.4

<!-- Release notes generated using configuration in .github/release.yml at v4.18.4 -->

* Improve the hashability of wrapped referencing exceptions when they contain hashable data.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.3...v4.18.4

4.18.3

<!-- Release notes generated using configuration in .github/release.yml at 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.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.2...v4.18.3

4.18.2

<!-- Release notes generated using configuration in .github/release.yml at v4.18.2 -->

* Fix an additional regression with the deprecated `jsonschema.RefResolver` and pointer resolution.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.1...v4.18.2

4.18.1

<!-- Release notes generated using configuration in .github/release.yml at v4.18.1 -->

* Fix a regression with jsonschema.RefResolver based resolution when used in combination with a custom validation dialect (via jsonschema.validators.create).

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0...v4.18.1

4.18.0

What's Changed

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 new [referencing 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 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`.
In particular, this referencing change includes a change concerning *automatic* retrieval of remote references (retrieving `http://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.
The `referencing` 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 receive `v4.17.3` when installing the library.
* 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.
* 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 via `jsonschema.exceptions.ErrorTree`
* importing `jsonschema.FormatError` -- instead import it via `jsonschema.exceptions.FormatError`

New Contributors
* DanielNoord made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/1021
* aryanA101a made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/1063
* jvtm made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/1076
* ikonst made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/1075

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.17.3...v4.18.0

4.18.0a10

<!-- Release notes generated using configuration in .github/release.yml at v4.18.0a10 -->



**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0a9...v4.18.0a10

4.18.0a9

<!-- Release notes generated using configuration in .github/release.yml at v4.18.0a9 -->



**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0a8...v4.18.0a9

4.18.0a8

<!-- Release notes generated using configuration in .github/release.yml at v4.18.0a8 -->



**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0a7...v4.18.0a8

4.18.0a7

<!-- Release notes generated using configuration in .github/release.yml at v4.18.0a7 -->



**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0a6...v4.18.0a7

4.18.0a6

<!-- Release notes generated using configuration in .github/release.yml at v4.18.0a6 -->



**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0a5...v4.18.0a6

4.18.0a5

<!-- Release notes generated using configuration in .github/release.yml at v4.18.0a5 -->



**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0a4...v4.18.0a5

4.18.0a4

<!-- Release notes generated using configuration in .github/release.yml at v4.18.0a4 -->



**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0a3...v4.18.0a4

4.18.0a3

<!-- Release notes generated using configuration in .github/release.yml at v4.18.0a3 -->

What's Changed
* fix: Python 3.11 date.fromisoformat() allows extra formats by jvtm in https://github.com/python-jsonschema/jsonschema/pull/1076
* Do not validate for unevaluatedProperties by ikonst in https://github.com/python-jsonschema/jsonschema/pull/1075

New Contributors
* jvtm made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/1076
* ikonst made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/1075

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0a2...v4.18.0a3

4.18.0a2

What's Changed
* documentation mistype fix by aryanA101a in https://github.com/python-jsonschema/jsonschema/pull/1063

New Contributors
* aryanA101a made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/1063

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.18.0a1...v4.18.0a2

4.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](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 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](https://python-jsonschema.readthedocs.io/en/latest/referencing/).

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 https://github.com/python-jsonschema/jsonschema/pull/1021

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.17.3...v4.18.0a1

4.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**: https://github.com/python-jsonschema/jsonschema/compare/v4.17.2...v4.17.3

4.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**: https://github.com/python-jsonschema/jsonschema/compare/v4.17.0...v4.17.1

4.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](https://github.com/python-jsonschema/check-jsonschema).
* Make ErrorTree have a more grammatically correct repr.


**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.16.0...v4.17.0

4.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**: https://github.com/python-jsonschema/jsonschema/compare/v4.15.0...v4.16.0

4.15.0

What's Changed
* Enable dedicated API documentation page(s) by Julian in https://github.com/python-jsonschema/jsonschema/pull/989


**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.14.0...v4.15.0

4.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**: https://github.com/python-jsonschema/jsonschema/compare/v4.13.0...v4.14.0

4.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**: https://github.com/python-jsonschema/jsonschema/compare/v4.12.1...v4.13.0

4.12.1

What's Changed
* Use rST markers in README by hynek in https://github.com/python-jsonschema/jsonschema/pull/987


**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.12.0...v4.12.1

4.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**: https://github.com/python-jsonschema/jsonschema/compare/v4.11.0...v4.12.0

4.11.0

What's Changed
* jsonschema deserves a ✨fancy✨ readme by hynek in https://github.com/python-jsonschema/jsonschema/pull/983


**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.10.3...v4.11.0

4.10.3

* ``jsonschema.validators.validator_for`` now properly uses the explicitly
provided default validator even if the ``$schema`` URI is not found.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.10.2...v4.10.3

4.10.2

* Fix a second place where subclasses may have added attrs attributes (982).

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.10.1...v4.10.2

4.10.1

* Fix Validator.evolve (and APIs like ``iter_errors`` which call it) for cases
where the validator class has been subclassed. Doing so wasn't intended to be
public API, but given it didn't warn or raise an error it's of course
understandable. The next release however will make it warn (and a future one
will make it error). If you need help migrating usage of inheriting from a
validator class feel free to open a discussion and I'll try to give some
guidance (982).


**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.10.0...v4.10.1

4.10.0

* Add support for referencing schemas with ``$ref`` across different versions
of the specification than the referrer's

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.9.1...v4.10.0

4.9.1

* Update some documentation examples to use newer validator releases in their
sample code.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.9.0...v4.9.1

4.9.0

* Fix relative ``$ref`` resolution when the base URI is a URN or other scheme
(544).
* ``pkgutil.resolve_name`` is now used to retrieve validators
provided on the command line. This function is only available on
3.9+, so 3.7 and 3.8 (which are still supported) now rely on the
`pkgutil_resolve_name <https://pypi.org/project/pkgutil_resolve_name/>`_
backport package. Note however that the CLI itself is due
to be deprecated shortly in favor of `check-jsonschema
<https://github.com/python-jsonschema/check-jsonschema>`_.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.8.0...v4.9.0

4.8.0

* ``best_match`` no longer traverses into ``anyOf`` and ``oneOf`` when all of
the errors within them seem equally applicable. This should lead to clearer
error messages in some cases where no branches were matched.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.7.2...v4.8.0

4.7.2

* Also have ``best_match`` handle cases where the ``type`` validator is an
array.

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.7.1...v4.7.2

4.7.1

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.7.0...v4.7.1

4.7.0

What's Changed
* Enhance best match to prefer errors from matching types. by Julian in https://github.com/python-jsonschema/jsonschema/pull/972


**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.6.2...v4.7.0

4.6.2

What's Changed
* docs: Fix a few typos by timgates42 in https://github.com/python-jsonschema/jsonschema/pull/969

New Contributors
* timgates42 made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/969

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.6.1...v4.6.2

4.6.1

What's Changed
* Type annotate format checker methods by sirosen in https://github.com/python-jsonschema/jsonschema/pull/958
* Fix fuzzer to include instrumentation by DavidKorczynski in https://github.com/python-jsonschema/jsonschema/pull/965
* [pre-commit.ci] pre-commit autoupdate by pre-commit-ci in https://github.com/python-jsonschema/jsonschema/pull/967


**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.6.0...v4.6.1

4.6.0

What's Changed
* Add package_url for changelog by fhightower in https://github.com/python-jsonschema/jsonschema/pull/950
* Only validate unevaluated properties/items on applicable types by EpicWink in https://github.com/python-jsonschema/jsonschema/pull/949
* Add v4.5.1 to changelog by sirosen in https://github.com/python-jsonschema/jsonschema/pull/956
* Modernize the packaging setup via PEP 621 and Hatch. by Julian in https://github.com/python-jsonschema/jsonschema/pull/957

New Contributors
* fhightower made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/950
* EpicWink made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/949

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.5.1...v4.6.0

4.5.1

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.5.0...v4.5.1

4.5.0

What's Changed
* Extend dynamicRef keyword by nezhar in https://github.com/python-jsonschema/jsonschema/pull/886
* Add FORMAT_CHECKER attribute for Validator by TiborVoelcker in https://github.com/python-jsonschema/jsonschema/pull/905
* Remove stray double-quote by lurch in https://github.com/python-jsonschema/jsonschema/pull/926
* Ensure proper sorting of list in error message by ssbarnea in https://github.com/python-jsonschema/jsonschema/pull/940

New Contributors
* TiborVoelcker made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/905
* lurch made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/926
* ssbarnea made their first contribution in https://github.com/python-jsonschema/jsonschema/pull/940

**Full Changelog**: https://github.com/python-jsonschema/jsonschema/compare/v4.4.0...v4.5.0

4.4.0

What's Changed
* Setup mypy in `tox -e typing` and get it to pass by sirosen in https://github.com/Julian/jsonschema/pull/892


**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.3.3...v4.4.0

4.3.3

What's Changed
* [pre-commit.ci] pre-commit autoupdate by pre-commit-ci in https://github.com/Julian/jsonschema/pull/897
* Move warnings to user context by Kojoley in https://github.com/Julian/jsonschema/pull/899

New Contributors
* Kojoley made their first contribution in https://github.com/Julian/jsonschema/pull/899

**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.3.2...v4.3.3

4.3.2

What's Changed
* perf: Cache subschemas by Stranger6667 in https://github.com/Julian/jsonschema/pull/896


**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.3.1...v4.3.2

4.3.1

What's Changed
* perf: Cache reference lookups for subschemas by Stranger6667 in https://github.com/Julian/jsonschema/pull/894


**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.3.0...v4.3.1

4.3.0

What's Changed
* perf: Undesired fallback to brute force container uniqueness check on certain input types by Stranger6667 in https://github.com/Julian/jsonschema/pull/893
* Add `jsonschema.protocols.IValidator` by sirosen in https://github.com/Julian/jsonschema/pull/890

New Contributors
* Stranger6667 made their first contribution in https://github.com/Julian/jsonschema/pull/893
* sirosen made their first contribution in https://github.com/Julian/jsonschema/pull/890

**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.2.1...v4.3.0

4.2.1

What's Changed
* Add version constraint to importlib_resources by sevein in https://github.com/Julian/jsonschema/pull/877


**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.2.0...v4.2.1

4.2.0

What's Changed
* Add release note about dropping support for Py 3.6 by sir-sigurd in https://github.com/Julian/jsonschema/pull/869
* Load schemas via importlib.resources by sevein in https://github.com/Julian/jsonschema/pull/873
* Ensure all elements of arrays are verified for uniqueness by DrGFreeman in https://github.com/Julian/jsonschema/pull/875

New Contributors
* sevein made their first contribution in https://github.com/Julian/jsonschema/pull/873
* DrGFreeman made their first contribution in https://github.com/Julian/jsonschema/pull/875

**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.1.2...v4.2.0

4.1.2

What's Changed
* validators: Fix dependentSchemas when instance is not an object by robherring in https://github.com/Julian/jsonschema/pull/850


**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.1.1...v4.1.2

4.1.1

What's Changed
* Fix prefixItems index reporting in ValidationError by jhashkes in https://github.com/Julian/jsonschema/pull/862

New Contributors
* jhashkes made their first contribution in https://github.com/Julian/jsonschema/pull/862

**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.1.0...v4.1.1

4.1.0

**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.0.1...v4.1.0

4.1.0a1

**Full Changelog**: https://github.com/Julian/jsonschema/compare/v4.0.1...v4.1.0a1

4.0.1

* Partial support for Draft 2020-12 (as well as 2019-09).
Thanks to Thomas Schmidt and Harald Nezbeda.
* ``False`` and ``0`` are now properly considered non-equal even
recursively within a container (686). As part of this change,
``uniqueItems`` validation may be *slower* in some cases. Please feel
free to report any significant performance regressions, though in
some cases they may be difficult to address given the specification
requirement.
* The CLI has been improved, and in particular now supports a ``--output``
option (with ``plain`` (default) or ``pretty`` arguments) to control the
output format. Future work may add additional machine-parsable output
formats.
* Code surrounding ``DEFAULT_TYPES`` and the legacy mechanism for
specifying types to validators have been removed, as per the deprecation
policy. Validators should use the ``TypeChecker`` object to customize
the set of Python types corresponding to JSON Schema types.
* Validation errors now have a ``json_path`` attribute, describing their
location in JSON path format
* Support for the IP address and domain name formats has been improved
* Support for Python 2 has been dropped, with ``python_requires`` properly
set.
* ``multipleOf`` could overflow when given sufficiently large numbers. Now,
when an overflow occurs, ``jsonschema`` will fall back to using fraction
division (746).
* ``jsonschema.__version__``, ``jsonschema.validators.validators``,
``jsonschema.validators.meta_schemas`` and
``jsonschema.RefResolver.in_scope`` have been deprecated, as has
passing a second-argument schema to ``Validator.iter_errors`` and
``Validator.is_valid``.

This patch release fixes an issue with the way `python_requires` was declared (i.e. with how the supported Python versions were declared).

4.0.0

* Partial support for Draft 2020-12 (as well as 2019-09).
Thanks to Thomas Schmidt and Harald Nezbeda.
* ``False`` and ``0`` are now properly considered non-equal even
recursively within a container (686). As part of this change,
``uniqueItems`` validation may be *slower* in some cases. Please feel
free to report any significant performance regressions, though in
some cases they may be difficult to address given the specification
requirement.
* The CLI has been improved, and in particular now supports a ``--output``
option (with ``plain`` (default) or ``pretty`` arguments) to control the
output format. Future work may add additional machine-parsable output
formats.
* Code surrounding ``DEFAULT_TYPES`` and the legacy mechanism for
specifying types to validators have been removed, as per the deprecation
policy. Validators should use the ``TypeChecker`` object to customize
the set of Python types corresponding to JSON Schema types.
* Validation errors now have a ``json_path`` attribute, describing their
location in JSON path format
* Support for the IP address and domain name formats has been improved
* Support for Python 2 has been dropped, with ``python_requires`` properly
set.
* ``multipleOf`` could overflow when given sufficiently large numbers. Now,
when an overflow occurs, ``jsonschema`` will fall back to using fraction
division (746).
* ``jsonschema.__version__``, ``jsonschema.validators.validators``,
``jsonschema.validators.meta_schemas`` and
``jsonschema.RefResolver.in_scope`` have been deprecated, as has
passing a second-argument schema to ``Validator.iter_errors`` and
``Validator.is_valid``.

0.27.3

- Update vendored schemas: bitbucket, gitlab-ci, readthedocs, renovate (2023-12-05)
- Limit the number of instance files which are opened simultaneously, which avoids reaching OS limits for open file descriptors. Thanks ianmackinnon! (352)
- Improve handling of schemafiles to ensure that they are only read once (363)

0.27.2

- Update vendored schemas: dependabot, github-workflows, renovate (2023-11-24)
- Add official support for Python 3.12
- Add Google Cloud Build schema and pre-commit hook. Thanks nikolaik! (339)
- Fix a bug in the custom `github-workflows-require-timeout` schema which forbade the use of GitHub expression syntax for the timeout value. (354)

0.27.1

- Update vendored schemas: buildkite, drone-ci, github-workflows, gitlab-ci, readthedocs, renovate (2023-11-03)

0.27.0

- Update vendored schemas: azure-pipelines, bitbucket-pipelines, gitlab-ci, renovate (2023-09-27)
- Add a `--validator-class` option for specifying a custom `jsonschema.protocols.Validator` class to use (327, 262)
- Instances and schemas may now be passed on stdin, using `-` (332, 251)
- Minor fix to hook regexes to explicitly match `.` chars. Thanks skwde! (325)

0.26.3

- Fix a minor bug with the verbose output introduced in v0.26.2

0.26.2

- When `-v/--verbose` is used, output will include a list of all files which were checked on success (312)

0.26.1

- Update vendored schemas: github-workflows, renovate (2023-08-25)

0.26.0

- The regex format check has been improved to support ECMAScript regexes by default. (302)
- The `--format-regex disabled` option has been removed. Users should use `--disable-formats regex` if they wish to disable regex format checking.
- The deprecated `--disable-format` flag has been removed. Users should use `--disable-formats "*"` if they wish to disable all format checking.

0.25.0

- Update vendored schemas: bamboo-spec, dependabot, drone-ci, github-actions, github-workflows, readthedocs, renovate, travis (2023-08-25)
- Add Drone-CI schema and pre-commit hook. Thanks s-weigand! (299)
- Add a `--base-uri` option for specifying an explicit base URI (305)

0.24.1

What's Changed
* Fix bugs related to the new `$ref` resolution behavior (https://github.com/python-jsonschema/check-jsonschema/pull/298)


**Full Changelog**: https://github.com/python-jsonschema/check-jsonschema/compare/0.24.0...0.24.1

0.24.0

<!-- Release notes generated using configuration in .github/release.yml at 0.24.0 -->

What's Changed

* Drop support for python3.7
* Update vendored schemas: github-actions, gitlab-ci, readthedocs, renovate, travis (2023-08-08)
* Use the new `referencing` implementation in `jsonschema` (https://github.com/python-jsonschema/check-jsonschema/pull/289)
* The minimum supported version of the jsonschema library is now 4.18.0, which introduces new $ref resolution behavior and fixes. That behavior is used in all cases, which should result in faster evaluation especially on large schemas.
* `$ref` usage may now refer to YAML, TOML, or JSON5 files, or any other non-JSON format supported by check-jsonschema. The file type is inferred only from the file extension in these cases and defaults to JSON if there is no recognizable extension.
* Remote schemafiles (http/s) now support YAML, TOML, and JSON5 formats, if the URL ends with the appropriate extension and the matching parser is available. Extensionless URLs are treated as JSON. (https://github.com/python-jsonschema/check-jsonschema/pull/295)


**Full Changelog**: https://github.com/python-jsonschema/check-jsonschema/compare/0.23.3...0.24.0

0.23.3

What's Changed
* Update vendored schemas: buildkite, dependabot, github-workflows, gitlab-ci, readthedocs, renovate
* Add Bitbucket Pipelines schema and pre-commit hook by djgoku in https://github.com/python-jsonschema/check-jsonschema/pull/282

New Contributors
* djgoku made their first contribution in https://github.com/python-jsonschema/check-jsonschema/pull/282

**Full Changelog**: https://github.com/python-jsonschema/check-jsonschema/compare/0.23.2...0.23.3

0.23.2

What's Changed

* Update vendored schemas: github-workflow, gitlab-ci, renovate
* Fix the handling of bad Last-Modified headers by sirosen in https://github.com/python-jsonschema/check-jsonschema/pull/277

**Full Changelog**: https://github.com/python-jsonschema/check-jsonschema/compare/0.23.1...0.23.2

0.23.1

What's Changed

- Updates to built-in schemas

**Full Changelog**: https://github.com/python-jsonschema/check-jsonschema/compare/0.23.0...0.23.1

0.23.0

What's Changed
* Update ruamel.yaml to latest by sirosen in https://github.com/python-jsonschema/check-jsonschema/pull/260
* Add new `--disable-formats` flag to replace `--disable-format` by sirosen in https://github.com/python-jsonschema/check-jsonschema/pull/261


**Full Changelog**: https://github.com/python-jsonschema/check-jsonschema/compare/0.22.0...0.23.0

0.22.0

What's Changed
* Add a check for tests which are always skipped by sirosen in https://github.com/python-jsonschema/check-jsonschema/pull/240
* Add support for dependabot.yaml file also by noorul in https://github.com/python-jsonschema/check-jsonschema/pull/243
* Fix the jsonschema lower bound in setup.cfg by sirosen in https://github.com/python-jsonschema/check-jsonschema/pull/244

New Contributors
* noorul made their first contribution in https://github.com/python-jsonschema/check-jsonschema/pull/243

**Full Changelog**: https://github.com/python-jsonschema/check-jsonschema/compare/0.21.0...0.22.0

Links

• PyPI: https://pypi.org/project/jsonschema
• Changelog: https://data.safetycli.com/changelogs/jsonschema/