chore(deps): update dependency jsonschema to v4.17.3 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jsonschema (changelog)	==4.4.0 -> ==4.17.3

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

python-jsonschema/jsonschema

v4.17.3

Compare Source

=======

• Fix instantiating validators with cached refs to boolean schemas
  rather than objects (#​1018).

v4.17.1

Compare Source

=======

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

v4.17.0

Compare Source

=======

• 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>_.

v4.16.0

Compare Source

=======

• 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.

v4.15.0

Compare Source

=======

• A specific API Reference page is now present in the documentation.
• $ref on earlier drafts (specifically draft 7 and 6) has been "fixed" to
  follow the specified behavior when present alongside a sibling $id.
  Specifically the ID is now properly ignored, and references are resolved
  against whatever resolution scope was previously relevant.

v4.14.0

Compare Source

=======

• 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

v4.13.0

Compare Source

=======

• 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.

v4.12.1

Compare Source

=======

• Fix some stray comments in the README.

v4.12.0

Compare Source

=======

• 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.

v4.11.0

Compare Source

=======

• Make the rendered README in PyPI simpler and fancier. Thanks Hynek (#​983)!

v4.10.3

Compare Source

=======

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

v4.10.2

Compare Source

=======

• Fix a second place where subclasses may have added attrs attributes (#​982).

v4.10.1

Compare Source

=======

• 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).

v4.10.0

Compare Source

=======

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

v4.9.1

Compare Source

======

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

v4.9.0

Compare Source

======

• 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>_.

v4.8.0

Compare Source

======

• 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.

v4.7.2

Compare Source

======

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

v4.7.1

Compare Source

======

• Minor tweak of the PyPI hyperlink names

v4.7.0

Compare Source

======

• Enhance best_match to prefer errors from branches of the schema which
  match the instance's type (#​728)

v4.6.2

Compare Source

======

• Fix a number of minor typos in docstrings, mostly private ones (#​969)

v4.6.1

Compare Source

======

• Gut the (incomplete) implementation of recursiveRef on draft 2019. It
  needs completing, but for now can lead to recursion errors (e.g. #​847).

v4.6.0

Compare Source

======

• Fix unevaluatedProperties and unevaluatedItems for types they should
  ignore (#​949)
• jsonschema now uses hatch <https://hatch.pypa.io/>_ for its build
  process. This should be completely transparent to end-users (and only matters
  to contributors).

v4.5.1

Compare Source

======

• Revert changes to $dynamicRef which caused a performance regression
  in v4.5.0

v4.5.0

Compare Source

======

• Validator classes for each version now maintain references to the correct
  corresponding format checker (#​905)
• Development has moved to a GitHub organization <https://github.com/python-jsonschema/>_.
  No functional behavior changes are expected from the change.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.