Bump jsonschema from 3.2.0 to 4.23.0
Bumps jsonschema from 3.2.0 to 4.23.0.
Release notes
Sourced from jsonschema's releases.
v4.23.0
What's Changed
- Add some typing to the
exceptions.pymodule by@DanielNoordin python-jsonschema/jsonschema#1019- Declare support for 3.13 by
@rominfin python-jsonschema/jsonschema#1282New Contributors
@rominfmade their first contribution in python-jsonschema/jsonschema#1282Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.22.0...v4.23.0
v4.22.0
What's Changed
- Improve
best_match(and thereby error messages fromjsonschema.validate) in cases where there are multiple sibling errors from applyinganyOf/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.New Contributors
@shinnarmade their first contribution in python-jsonschema/jsonschema#1224Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.21.1...v4.22.0
v4.21.1
- Slightly speed up the
containskeyword 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
enumin the presence of0or1to properly considerTrueandFalseunequal (#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-ifakmade their first contribution in python-jsonschema/jsonschema#1208Full 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$dynamicRefas specified by the 2020 and 2019 specifications.jsonschema.exceptions.ErrorTree.__setitem__is now deprecated. More broadly, in general users ofjsonschemashould never be mutating objects owned by the library.Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.19.2...v4.20.0
... (truncated)
Changelog
Sourced from jsonschema's changelog.
v4.23.0
- Do not reorder dictionaries (schemas, instances) that are printed as part of validation errors.
- Declare support for Py3.13
v4.22.0
- Improve
best_match(and thereby error messages fromjsonschema.validate) in cases where there are multiple sibling errors from applyinganyOf/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.v4.21.1
- Slightly speed up the
containskeyword by removing some unnecessary validator (re-)creation.v4.21.0
- Fix the behavior of
enumin the presence of0or1to properly considerTrueandFalseunequal (#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$dynamicRefas specified by the 2020 and 2019 specifications.jsonschema.exceptions.ErrorTree.__setitem__is now deprecated. More broadly, in general users ofjsonschemashould 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
additionalItemskeyword 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
hostnameformat. This is the behavior specified by the relevant RFC (1123). IDN hostname behavior was already correct.v4.19.0
- Importing the
Validatorprotocol directly from the package root is deprecated. Import it fromjsonschema.protocols.Validatorinstead.- 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.
... (truncated)
Commits
cfe8a40Document the other change, and call this 4.23.0.25127a1Merge pull request #1282 from rominf/rominf-python3.1340410c4Declare support for 3.133a44b4bMerge pull request #1276 from python-jsonschema/pre-commit-ci-update-config6a00e35[pre-commit.ci] pre-commit autoupdate84fee43Merge pull request #1273 from python-jsonschema/pre-commit-ci-update-configa90d6e2[pre-commit.ci] pre-commit autoupdatec3a8641Merge pull request #1272 from python-jsonschema/pre-commit-ci-update-configdeb5398[pre-commit.ci] pre-commit autoupdate7fd28c3Update the (ancient draft3) color format for newer webcolors.- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.