#2028 chore(deps): update jsonschema requirement from <4.18,>=4.17.3 to >=4.17.3,<4.25 Pull request opened by dependabot[bot] Updates the requirements on jsonschema to permit the latest version. Release notes Sourced from jsonschema's releases.

## v4.24.0

## What's Changed

• Fix calculation of evaluated properties by `@​V02460` in python-jsonschema/jsonschema#1351

• Support for Python 3.8 has been dropped, as it is end-of-life.

## New Contributors

• `@​bkueng` made their first contribution in python-jsonschema/jsonschema#1326

• `@​V02460` made their first contribution in python-jsonschema/jsonschema#1351

Full Changelog: python-jsonschema/jsonschema@v4.23.0...v4.24.0

Changelog Sourced from jsonschema's changelog.

# v4.24.0

• Fix improper handling of

unevaluatedProperties

in the presence of

additionalProperties

(#1351).

• Support for Python 3.8 has been dropped, as it is end-of-life.

# 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

... (truncated) Commits • `3e23ee5` Add the bugfix to the changelog. • `8917e85` Stop running CIFuzz. • `737e5ed` Rely on ruff in pre-commit. • `57e5e03` Test via PyPy 3.11. • `d6c2ad7` Add the zizmor setup here as well. • `af9a857` Drop a dead pyproject section. • `c64ef84` This is less true than it once was... • `9ff926f` Merge branch 'additional-evaluated' • `8290667` We still need to ditch pip-licenses... • `6d973b5` Update pre-commit hooks. • Additional commits viewable in compare view Most Recent Ignore Conditions Applied to This Pull Request | Dependency Name | Ignore Conditions | | --------------- | ------------------- | | jsonschema | [>= 4.19.a, < 4.20] | 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) meltano/hub