Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump jsonschema from 4.17.3 to 4.22.0 #1753

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 1, 2024

Bumps jsonschema from 4.17.3 to 4.22.0.

Release notes

Sourced from jsonschema's releases.

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

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

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

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.

Full Changelog: python-jsonschema/jsonschema@v4.19.1...v4.19.2

v4.19.1

... (truncated)

Changelog

Sourced from jsonschema's changelog.

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. This more closely matches the pre-referencing library behavior.

v4.18.6

  • Set a jsonschema specific user agent when automatically retrieving remote references (which is deprecated).

... (truncated)

Commits
  • 9882dbe Add / ignore the new specification test suite property.
  • ebc90bb Merge commit '8fcfc3a674a7188a4fcc822b7a91efb3e0422a20'
  • 8fcfc3a Squashed 'json/' changes from b41167c74..54f3784a8
  • 30b7537 Pin pyenchant to pre from below until pyenchant/pyenchant#302 is released.
  • c3729db Enable doctests for the rest of the referencing page.
  • 70a994c Remove a now-unneeded noqa since apparently this is fixed in new ruff.
  • e6d0ef1 Fix a minor typo in the referencing example docs.
  • bceaf41 Another placeholder benchmark for future optimization.
  • b20234e Consider errors from earlier indices (in instances) to be better matches
  • 41b49c6 Minor improvement to test failure message when a best match test fails.
  • 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 compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @edgarrmondragon.


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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot requested a review from cjohnhanson as a code owner May 1, 2024 12:33
@dependabot dependabot bot added the deps label May 1, 2024
@dependabot dependabot bot requested a review from a team May 1, 2024 12:33
Copy link

netlify bot commented May 1, 2024

Deploy Preview for meltano-hub ready!

Name Link
🔨 Latest commit 5b07014
🔍 Latest deploy log https://app.netlify.com/sites/meltano-hub/deploys/66860dc14896e3000763f3e6
😎 Deploy Preview https://deploy-preview-1753--meltano-hub.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

edgarrmondragon
edgarrmondragon approved these changes May 2, 2024
@edgarrmondragon edgarrmondragon self-requested a review May 2, 2024 02:54
@dependabot dependabot bot force-pushed the dependabot/pip/jsonschema-4.22.0 branch from 0d7aaaa to 20fa7d0 Compare May 21, 2024 15:05
Copy link
Contributor Author

dependabot bot commented on behalf of github May 21, 2024

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

@edgarrmondragon
Copy link
Collaborator

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/pip/jsonschema-4.22.0 branch from 20fa7d0 to 572d67a Compare May 21, 2024 22:48
@dependabot dependabot bot force-pushed the dependabot/pip/jsonschema-4.22.0 branch from 572d67a to 4410069 Compare May 22, 2024 14:30
@dependabot dependabot bot force-pushed the dependabot/pip/jsonschema-4.22.0 branch from 4410069 to 2fa5b77 Compare May 30, 2024 13:05
@edgarrmondragon
Copy link
Collaborator

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/pip/jsonschema-4.22.0 branch from 2fa5b77 to 35f62f1 Compare July 4, 2024 02:01
@edgarrmondragon
Copy link
Collaborator

@dependabot rebase

Bumps [jsonschema](https://github.com/python-jsonschema/jsonschema) from 4.17.3 to 4.22.0.
- [Release notes](https://github.com/python-jsonschema/jsonschema/releases)
- [Changelog](https://github.com/python-jsonschema/jsonschema/blob/main/CHANGELOG.rst)
- [Commits](python-jsonschema/jsonschema@v4.17.3...v4.22.0)

---
updated-dependencies:
- dependency-name: jsonschema
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/pip/jsonschema-4.22.0 branch from 35f62f1 to 5b07014 Compare July 4, 2024 02:49
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 15, 2024

Superseded by #1806.

@dependabot dependabot bot closed this Jul 15, 2024
@dependabot dependabot bot deleted the dependabot/pip/jsonschema-4.22.0 branch July 15, 2024 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant