Bump jsonschema from 4.19.0 to 4.21.1

[dependabot[bot]]

Bumps jsonschema from 4.19.0 to 4.21.1.

Release notes

Sourced from jsonschema's releases.

v4.21.1

• Slightly speed up the contains keyword by removing some unnecessary validator (re-)creation.

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

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 python-jsonschema/jsonschema#1208

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

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

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

v4.19.1

What's Changed

• Allow single label hostname in format string by @​swaeberle in python-jsonschema/jsonschema#1164

New Contributors

• @​swaeberle made their first contribution in python-jsonschema/jsonschema#1164

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

Changelog

Sourced from jsonschema's changelog.

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

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 of jsonschema 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 by items.

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.

Commits

• aa53fd0 Slightly speed up the contains keyword.
• c9e2029 perf -> bench
• 31dec3d Update the CHANGELOG.
• 8875c2e Also improve min{Length,Properties}'s error message.
• 74dfd48 Squashed 'json/' changes from 217bf81b..544f7c3d
• 3e46f22 Merge pull request #1208 from otto-ifak/fix_enum
• e45be0b Update docs requirements.
• 6b4441e New ruff fixed some bugs.
• c7a37f2 Merge pull request #1209 from python-jsonschema/pre-commit-ci-update-config
• 1b72180 [pre-commit.ci] pre-commit autoupdate
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)