chore(deps): update dependency jsonschema to v4.22.0 #10

Merged
realaravinth merged 1 commit from renovate/jsonschema-4.x into master 2024-06-08 01:44:09 +05:30
Member

This PR contains the following updates:

Package Update Change
jsonschema (changelog) minor ==4.19.1 -> ==4.22.0

Release Notes

python-jsonschema/jsonschema (jsonschema)

v4.22.0

Compare Source

=======

  • 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

Compare Source

=======

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

v4.21.0

Compare Source

=======

  • 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

Compare Source

=======

  • 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

Compare Source

=======

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

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

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [jsonschema](https://github.com/python-jsonschema/jsonschema) ([changelog](https://github.com/python-jsonschema/jsonschema/blob/main/CHANGELOG.rst)) | minor | `==4.19.1` -> `==4.22.0` | --- ### Release Notes <details> <summary>python-jsonschema/jsonschema (jsonschema)</summary> ### [`v4.22.0`](https://github.com/python-jsonschema/jsonschema/blob/HEAD/CHANGELOG.rst#v4220) [Compare Source](https://github.com/python-jsonschema/jsonschema/compare/v4.21.1...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 ([#&#8203;1250](https://github.com/python-jsonschema/jsonschema/issues/1250)). - (Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as `==` would. ### [`v4.21.1`](https://github.com/python-jsonschema/jsonschema/blob/HEAD/CHANGELOG.rst#v4211) [Compare Source](https://github.com/python-jsonschema/jsonschema/compare/v4.21.0...v4.21.1) \======= - Slightly speed up the `contains` keyword by removing some unnecessary validator (re-)creation. ### [`v4.21.0`](https://github.com/python-jsonschema/jsonschema/blob/HEAD/CHANGELOG.rst#v4210) [Compare Source](https://github.com/python-jsonschema/jsonschema/compare/v4.20.0...v4.21.0) \======= - Fix the behavior of `enum` in the presence of `0` or `1` to properly consider `True` and `False` unequal ([#&#8203;1208](https://github.com/python-jsonschema/jsonschema/issues/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`](https://github.com/python-jsonschema/jsonschema/blob/HEAD/CHANGELOG.rst#v4200) [Compare Source](https://github.com/python-jsonschema/jsonschema/compare/v4.19.2...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`](https://github.com/python-jsonschema/jsonschema/blob/HEAD/CHANGELOG.rst#v4192) [Compare Source](https://github.com/python-jsonschema/jsonschema/compare/v4.19.1...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`. </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zODUuMCIsInVwZGF0ZWRJblZlciI6IjM3LjM4OC4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbInJlbm92YXRlLWJvdCJdfQ==-->
renovate-bot added the
renovate-bot
label 2024-06-02 19:27:53 +05:30
renovate-bot added 1 commit 2024-06-02 19:27:54 +05:30
chore(deps): update dependency jsonschema to v4.22.0
All checks were successful
ci/woodpecker/manual/woodpecker Pipeline was successful
ci/woodpecker/pull_request_closed/woodpecker Pipeline was successful
5bcc7703ca
realaravinth merged commit 5aae4a6098 into master 2024-06-08 01:44:09 +05:30
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: ForgeFlux/nodeinfo-test#10
No description provided.