Skip to content
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.

chore(deps): update dependency jsonschema to v4.23.0 #5

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 23, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jsonschema (changelog) ==4.19.1 -> ==4.23.0 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

python-jsonschema/jsonschema (jsonschema)

v4.23.0

Compare Source

=======

  • Do not reorder dictionaries (schemas, instances) that are printed as part of validation errors.
  • Declare support for Py3.13

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

Rebasing: Whenever PR is behind base branch, 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 Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Feb 23, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/jsonschema-4.x branch 3 times, most recently from 208f444 to 5851e76 Compare March 19, 2024 04:57
@renovate renovate bot force-pushed the renovate/jsonschema-4.x branch 3 times, most recently from de2e4ce to 8927977 Compare March 28, 2024 19:34
@renovate renovate bot force-pushed the renovate/jsonschema-4.x branch 3 times, most recently from 5589ef8 to fa25e71 Compare April 5, 2024 07:41
@renovate renovate bot changed the title chore(deps): update dependency jsonschema to v4.21.1 chore(deps): update dependency jsonschema to v4.22.0 Apr 30, 2024
@renovate renovate bot force-pushed the renovate/jsonschema-4.x branch from fa25e71 to 1ed71c0 Compare April 30, 2024 21:37
@renovate renovate bot changed the title chore(deps): update dependency jsonschema to v4.22.0 chore(deps): update dependency jsonschema to v4.23.0 Jul 9, 2024
@renovate renovate bot force-pushed the renovate/jsonschema-4.x branch from 1ed71c0 to fb85861 Compare July 9, 2024 17:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants