-
Notifications
You must be signed in to change notification settings - Fork 54
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
[PR #1295/853e209f backport][0.15] [noissue]: Update jsonschema requirement from <4.10,>=4.9 to >=4.9,<4.18 #1327
Merged
mdellweg
merged 1 commit into
0.15
from
patchback/backports/0.15/853e209f8900444fb8735ac10df17b4100a42682/pr-1295
Jan 20, 2023
Merged
[PR #1295/853e209f backport][0.15] [noissue]: Update jsonschema requirement from <4.10,>=4.9 to >=4.9,<4.18 #1327
mdellweg
merged 1 commit into
0.15
from
patchback/backports/0.15/853e209f8900444fb8735ac10df17b4100a42682/pr-1295
Jan 20, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
….18 (#1295) Updates the requirements on [jsonschema](https://github.com/python-jsonschema/jsonschema) to permit the latest version. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/python-jsonschema/jsonschema/releases">jsonschema's releases</a>.</em></p> <blockquote> <h2>v4.17.1</h2> <p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.17.0...v4.17.1">https://github.com/python-jsonschema/jsonschema/compare/v4.17.0...v4.17.1</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/python-jsonschema/jsonschema/blob/main/CHANGELOG.rst">jsonschema's changelog</a>.</em></p> <blockquote> <h1>v4.17.1</h1> <ul> <li>The error message when using <code>unevaluatedProperties</code> with a non-trivial schema value (i.e. something other than <code>false</code>) has been improved (<a href="https://github-redirect.dependabot.com/python-jsonschema/jsonschema/issues/996">#996</a>).</li> </ul> <h1>v4.17.0</h1> <ul> <li>The <code>check_schema</code> method on <code>jsonschema.protocols.Validator</code> instances now <em>enables</em> format validation by default when run. This can catch some additional invalid schemas (e.g. containing invalid regular expressions) where the issue is indeed uncovered by validating against the metaschema with format validation enabled as an assertion.</li> <li>The <code>jsonschema</code> CLI (along with <code>jsonschema.cli</code> the module) are now deprecated. Use <code>check-jsonschema</code> instead, which can be installed via <code>pip install check-jsonschema</code> and found <code>here <https://github.com/python-jsonschema/check-jsonschema></code>_.</li> </ul> <h1>v4.16.1</h1> <ul> <li>Make <code>ErrorTree</code> have a more grammatically correct <code>repr</code>.</li> </ul> <h1>v4.16.0</h1> <ul> <li>Improve the base URI behavior when resolving a <code>$ref</code> to a resolution URI which is different from the resolved schema's declared <code>$id</code>.</li> <li>Accessing <code>jsonschema.draftN_format_checker</code> is deprecated. Instead, if you want access to the format checker itself, it is exposed as <code>jsonschema.validators.DraftNValidator.FORMAT_CHECKER</code> on any <code>jsonschema.protocols.Validator</code>.</li> </ul> <h1>v4.15.0</h1> <ul> <li>A specific API Reference page is now present in the documentation.</li> <li><code>$ref</code> on earlier drafts (specifically draft 7 and 6) has been "fixed" to follow the specified behavior when present alongside a sibling <code>$id</code>. Specifically the ID is now properly ignored, and references are resolved against whatever resolution scope was previously relevant.</li> </ul> <h1>v4.14.0</h1> <ul> <li><code>FormatChecker.cls_checks</code> is deprecated. Use <code>FormatChecker.checks</code> on an instance of <code>FormatChecker</code> instead.</li> <li><code>unevaluatedItems</code> has been fixed for draft 2019. It's nonetheless discouraged to use draft 2019 for any schemas, new or old.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/46fdb982a26aac211bc4d20b2ef6d8089a520f77"><code>46fdb98</code></a> v4.17.1 -> CHANGELOG</li> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/000dd3d408ae79e4e1580faa4b6ec22f3097debd"><code>000dd3d</code></a> Remove making believe we are ReadTheDocs in CI builds.</li> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/556304495ca6202e3c7485a13d77fb5c8f3c593f"><code>5563044</code></a> Skip the rest of the docs builds on Windows in CI.</li> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/198d1af47baf3f04d28fbd4e6cade7916607ec95"><code>198d1af</code></a> Run more things with 3.11 in CI.</li> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/da355840a75f0b034ea80585c4d1141e5a7581b8"><code>da35584</code></a> Suppress epub warnings for duplicated ToC entries.</li> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/be86aad6329f3372702767eece28608d7b672d48"><code>be86aad</code></a> Temporarily evade <a href="https://github-redirect.dependabot.com/wpilibsuite/sphinxext-opengraph/issues/87">wpilibsuite/sphinxext-opengraph#87</a></li> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/90694843a7501692a83d987a60808cec14106129"><code>9069484</code></a> Update docs requirements.</li> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/4f8f346cc475439715833ac6bd6e5c5e3dc21ee3"><code>4f8f346</code></a> Un-bundle single-vocabulary meta-schemas.</li> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/7830605c1c4993df864d292c8555fa3cf414f6ca"><code>7830605</code></a> Emit a better error message for unevaluatedProperties with a subschema.</li> <li><a href="https://github.com/python-jsonschema/jsonschema/commit/75903d861e0497e4a3d38b8994601df1ecaa888b"><code>75903d8</code></a> Merge commit '62e69b2c3be9e30c50bea2e595eb2afcd13666ec'</li> <li>Additional commits viewable in <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.9.0...v4.17.1">compare view</a></li> </ul> </details> <br /> 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit 853e209)
mdellweg
approved these changes
Jan 20, 2023
mdellweg
deleted the
patchback/backports/0.15/853e209f8900444fb8735ac10df17b4100a42682/pr-1295
branch
January 20, 2023 09:06
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #1295 as merged into main (853e209).
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Updates the requirements on jsonschema to permit the latest version.
Release notes
Sourced from jsonschema's releases.
Changelog
Sourced from jsonschema's changelog.
... (truncated)
Commits
46fdb98
v4.17.1 -> CHANGELOG000dd3d
Remove making believe we are ReadTheDocs in CI builds.5563044
Skip the rest of the docs builds on Windows in CI.198d1af
Run more things with 3.11 in CI.da35584
Suppress epub warnings for duplicated ToC entries.be86aad
Temporarily evade wpilibsuite/sphinxext-opengraph#879069484
Update docs requirements.4f8f346
Un-bundle single-vocabulary meta-schemas.7830605
Emit a better error message for unevaluatedProperties with a subschema.75903d8
Merge commit '62e69b2c3be9e30c50bea2e595eb2afcd13666ec'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 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)