<#1806 chore(deps): bump jsonschema from 4.17.3 to...
# hub-repo-activity
g
#1806 chore(deps): bump jsonschema from 4.17.3 to 4.23.0 Pull request opened by dependabot[bot] Bumps jsonschema from 4.17.3 to 4.23.0. Release notes Sourced from jsonschema's releases.
## v4.23.0
## What's Changed
• Add some typing to the
exceptions.py
module by `@​DanielNoord` in python-jsonschema/jsonschema#1019
• Declare support for 3.13 by `@​rominf` in python-jsonschema/jsonschema#1282
## New Contributors
• `@​rominf` made their first contribution in python-jsonschema/jsonschema#1282
Full Changelog: python-jsonschema/jsonschema@v4.22.0...v4.23.0
## v4.22.0
## What's Changed
• 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.
## New Contributors
• `@​shinnar` made their first contribution in python-jsonschema/jsonschema#1224
Full Changelog: python-jsonschema/jsonschema@v4.21.1...v4.22.0
## v4.21.1
• Slightly speed up the
contains
keyword by removing some unnecessary validator (re-)creation.
Full Changelog: python-jsonschema/jsonschema@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: python-jsonschema/jsonschema@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: python-jsonschema/jsonschema@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 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.
# 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.
# 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.
... (truncated) Commits • `cfe8a40` Document the other change, and call this 4.23.0. • `25127a1` Merge pull request #1282 from rominf/rominf-python3.13 • `40410c4` Declare support for 3.13 • `3a44b4b` Merge pull request #1276 from python-jsonschema/pre-commit-ci-update-config • `6a00e35` [pre-commit.ci] pre-commit autoupdate • `84fee43` Merge pull request #1273 from python-jsonschema/pre-commit-ci-update-config • `a90d6e2` [pre-commit.ci] pre-commit autoupdate • `c3a8641` Merge pull request #1272 from python-jsonschema/pre-commit-ci-update-config • <https://github.com/python-jsonschema/jsonschema/commit/deb53982d59d98f86ef18f50cd098066af70003e|`deb5398… meltano/hub