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): update dependency jsonschema to v4.19.0 #24

Merged
merged 6 commits into from
Aug 16, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 16, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

python-jsonschema/jsonschema (jsonschema)

v4.19.0

Compare Source

=======

  • 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

Compare Source

=======

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

v4.18.5

Compare Source

=======

  • Declare support for Py3.12

v4.18.4

Compare Source

=======

  • Improve the hashability of wrapped referencing exceptions when they contain hashable data.

v4.18.3

Compare Source

=======

  • Properly preserve applicable_validators in extended validators.
    Specifically, validators extending early drafts where siblings of $ref were ignored will properly ignore siblings in the extended validator.

v4.18.2

Compare Source

=======

  • Fix an additional regression with the deprecated jsonschema.RefResolver and pointer resolution.

v4.18.1

Compare Source

=======

  • Fix a regression with jsonschema.RefResolver based resolution when used in combination with a custom validation dialect (via jsonschema.validators.create).

v4.18.0

Compare Source

=======

This release majorly rehauls the way in which JSON Schema reference resolution is configured.
It does so in a way that should be backwards compatible, preserving old behavior whilst emitting deprecation warnings.

  • jsonschema.RefResolver is now deprecated in favor of the new referencing library <https://github.com/python-jsonschema/referencing/>_.
    referencing will begin in beta, but already is more compliant than the existing $ref support.
    This change is a culmination of a meaningful chunk of work to make $ref resolution more flexible and more correct.
    Backwards compatibility should be preserved for existing code which uses RefResolver, though doing so is again now deprecated, and all such use cases should be doable using the new APIs.
    Please file issues on the referencing tracker if there is functionality missing from it, or here on the jsonschema issue tracker if you have issues with existing code not functioning the same, or with figuring out how to change it to use referencing.
    In particular, this referencing change includes a change concerning automatic retrieval of remote references (retrieving http://foo/bar automatically within a schema).
    This behavior has always been a potential security risk and counter to the recommendations of the JSON Schema specifications; it has survived this long essentially only for backwards compatibility reasons, and now explicitly produces warnings.
    The referencing library itself will not automatically retrieve references if you interact directly with it, so the deprecated behavior is only triggered if you fully rely on the default $ref resolution behavior and also include remote references in your schema, which will still be retrieved during the deprecation period (after which they will become an error).
  • Support for Python 3.7 has been dropped, as it is nearing end-of-life.
    This should not be a "visible" change in the sense that requires-python has been updated, so users using 3.7 should still receive v4.17.3 when installing the library.
  • On draft 2019-09, unevaluatedItems now properly does not consider items to be evaluated by an additionalItems schema if items is missing from the schema, as the specification says in this case that additionalItems must be completely ignored.
  • Fix the date format checker on Python 3.11 (when format assertion behavior is enabled), where it was too liberal (#​1076).
  • Speed up validation of unevaluatedProperties (#​1075).

Deprecations

  • jsonschema.RefResolver -- see above for details on the replacement
  • jsonschema.RefResolutionError -- see above for details on the replacement
  • relying on automatic resolution of remote references -- see above for details on the replacement
  • importing jsonschema.ErrorTree -- instead import it via jsonschema.exceptions.ErrorTree
  • importing jsonschema.FormatError -- instead import it via jsonschema.exceptions.FormatError

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 Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner August 16, 2023 11:44
@renovate
Copy link
Contributor Author

renovate bot commented Aug 16, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

gtrkiller
gtrkiller previously approved these changes Aug 16, 2023
requirements.txt Outdated Show resolved Hide resolved
gtrkiller
gtrkiller previously approved these changes Aug 16, 2023
amandahla
amandahla previously approved these changes Aug 16, 2023
@arturo-seijas arturo-seijas dismissed stale reviews from amandahla and gtrkiller via c30bce7 August 16, 2023 15:26
@github-actions
Copy link
Contributor

Test coverage for bdcdc70

Name                            Stmts   Miss Branch BrPart  Cover   Missing
---------------------------------------------------------------------------
src/actions/__init__.py             3      0      0      0   100%
src/actions/register_user.py       20      0      2      0   100%
src/actions/reset_instance.py      21      3      2      1    83%   54-58
src/charm.py                       83      2      8      1    97%   139-140
src/charm_state.py                 45      2     10      2    93%   22, 79
src/charm_types.py                  8      0      0      0   100%
src/constants.py                   11      0      0      0   100%
src/database_client.py             53      1     10      3    94%   35, 47->exit, 69->exit
src/database_observer.py           54      4      6      0    93%   70-72, 96
src/exceptions.py                   4      0      0      0   100%
src/observability.py                9      0      0      0   100%
src/pebble.py                      47      0      0      0   100%
src/synapse/__init__.py             3      0      0      0   100%
src/synapse/api.py                 46      2      2      1    94%   126-127
src/synapse/workload.py            87      3     10      1    96%   147, 278-283
src/user.py                        23      0      4      0   100%
---------------------------------------------------------------------------
TOTAL                             517     17     54      9    95%

Static code analysis report

Run started:2023-08-16 15:54:02.134568

Test results:
  No issues identified.

Code scanned:
  Total lines of code: 2386
  Total lines skipped (#nosec): 1
  Total potential issues skipped due to specifically being disabled (e.g., #nosec BXXX): 0

Run metrics:
  Total issues (by severity):
  	Undefined: 0
  	Low: 0
  	Medium: 0
  	High: 0
  Total issues (by confidence):
  	Undefined: 0
  	Low: 0
  	Medium: 0
  	High: 0
Files skipped (0):

@arturo-seijas arturo-seijas merged commit e8821a6 into main Aug 16, 2023
19 checks passed
@arturo-seijas arturo-seijas deleted the renovate/jsonschema-4.x branch August 16, 2023 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants