Closed Bug 1865220 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 43216 - Bump jsonschema from 4.17.3 to 4.20.0 in /tools

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 43216 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/43216
Details from upstream follow.

dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> wrote:

Bump jsonschema from 4.17.3 to 4.20.0 in /tools

Bumps jsonschema from 4.17.3 to 4.20.0.
<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.20.0</h2>
<ul>
<li>Properly consider items (and properties) to be evaluated by <code>unevaluatedItems</code> (resp. <code>unevaluatedProperties</code>) when behind a <code>$dynamicRef</code> as specified by the 2020 and 2019 specifications.</li>
<li><code>jsonschema.exceptions.ErrorTree.__setitem__</code> is now deprecated. More broadly, in general users of <code>jsonschema</code> should never be mutating objects owned by the library.</li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.19.2...v4.20.0">https://github.com/python-jsonschema/jsonschema/compare/v4.19.2...v4.20.0</a></p>
<h2>v4.19.2</h2>
<!-- raw HTML omitted -->
<ul>
<li>Fix the error message for additional items when used with heterogeneous arrays.</li>
<li>Don't leak the <code>additionalItems</code> keyword into JSON Schema draft 2020-12, where it was replaced by <code>items</code>.</li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.19.1...v4.19.2">https://github.com/python-jsonschema/jsonschema/compare/v4.19.1...v4.19.2</a></p>
<h2>v4.19.1</h2>
<!-- raw HTML omitted -->
<h2>What's Changed</h2>
<ul>
<li>Allow single label hostname in format string by <a href="https://github.com/swaeberle"><code>@​swaeberle</code></a> in <a href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1164">python-jsonschema/jsonschema#1164</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/swaeberle"><code>@​swaeberle</code></a> made their first contribution in <a href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1164">python-jsonschema/jsonschema#1164</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.19.0...v4.19.1">https://github.com/python-jsonschema/jsonschema/compare/v4.19.0...v4.19.1</a></p>
<h2>v4.19.0</h2>
<!-- raw HTML omitted -->
<ul>
<li>Importing the <code>Validator</code> protocol directly from the package root is deprecated. Import it from <code>jsonschema.protocols.Validator</code> instead.</li>
<li>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-<code>referencing</code> library behavior.</li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.18.6...v4.19.0">https://github.com/python-jsonschema/jsonschema/compare/v4.18.6...v4.19.0</a></p>
<h2>v4.18.6</h2>
<!-- raw HTML omitted -->
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.18.5...v4.18.6">https://github.com/python-jsonschema/jsonschema/compare/v4.18.5...v4.18.6</a></p>
<h2>v4.18.5</h2>
<!-- raw HTML omitted -->
<ul>
<li>Declare support for Py3.12</li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.18.4...v4.18.5">https://github.com/python-jsonschema/jsonschema/compare/v4.18.4...v4.18.5</a></p>
<h2>v4.18.4</h2>
<!-- raw HTML omitted -->
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</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.20.0</h1>
<ul>
<li>Properly consider items (and properties) to be evaluated by <code>unevaluatedItems</code> (resp. <code>unevaluatedProperties</code>) when behind a <code>$dynamicRef</code> as specified by the 2020 and 2019 specifications.</li>
<li><code>jsonschema.exceptions.ErrorTree.__setitem__</code> is now deprecated.
More broadly, in general users of <code>jsonschema</code> should never be mutating objects owned by the library.</li>
</ul>
<h1>v4.19.2</h1>
<ul>
<li>Fix the error message for additional items when used with heterogeneous arrays.</li>
<li>Don't leak the <code>additionalItems</code> keyword into JSON Schema draft 2020-12, where it was replaced by <code>items</code>.</li>
</ul>
<h1>v4.19.1</h1>
<ul>
<li>Single label hostnames are now properly considered valid according to the <code>hostname</code> format.
This is the behavior specified by the relevant RFC (1123).
IDN hostname behavior was already correct.</li>
</ul>
<h1>v4.19.0</h1>
<ul>
<li>Importing the <code>Validator</code> protocol directly from the package root is deprecated.
Import it from <code>jsonschema.protocols.Validator</code> instead.</li>
<li>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.</li>
</ul>
<h1>v4.18.6</h1>
<ul>
<li>Set a <code>jsonschema</code> specific user agent when automatically retrieving remote references (which is deprecated).</li>
</ul>
<h1>v4.18.5</h1>
<ul>
<li>Declare support for Py3.12</li>
</ul>
<h1>v4.18.4</h1>
<ul>
<li>Improve the hashability of wrapped referencing exceptions when they contain hashable data.</li>
</ul>
<h1>v4.18.3</h1>
<ul>
<li>Properly preserve <code>applicable_validators</code> in extended validators.
Specifically, validators extending early drafts where siblings of <code>$ref</code> were ignored will properly ignore siblings in the extended validator.</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/5ff5999d50420251744bc49e758f3b15ad2f8569"><code>5ff5999</code></a> Consider properties evaluated when they're behind dynamic refs.</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/13bc188cff083b2e3f1383bfa7473bbab2338cbb"><code>13bc188</code></a> Squashed 'json/' changes from 95fe6ca2..d38ddd54</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/2ed7ad662ae7cf5fce5a059f7ceed2650b2f7fd7"><code>2ed7ad6</code></a> Merge pull request <a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1191">#1191</a> from python-jsonschema/pre-commit-ci-update-config</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/6db1bef4c7937beddf448356a404da9d834339cb"><code>6db1bef</code></a> [pre-commit.ci] pre-commit autoupdate</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/c563034a6018de6d33dde4ef8e7e8e6abdf13b65"><code>c563034</code></a> Merge pull request <a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1189">#1189</a> from python-jsonschema/pre-commit-ci-update-config</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/420a96cbdb7675266ecfcc2c060cd6c7a5293fed"><code>420a96c</code></a> [pre-commit.ci] pre-commit autoupdate</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/5b06df6db1630c13e35899fb9a1ed4a62f26d612"><code>5b06df6</code></a> Apparently this setting is now autodetected.</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/11e230219d130ac1a25b0b82203cff319564f0a0"><code>11e2302</code></a> Minor typing tweaks in the exceptions module.</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/65877a16269f00926486359c3f6c4731e4c28d69"><code>65877a1</code></a> Merge pull request <a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1185">#1185</a> from python-jsonschema/pre-commit-ci-update-config</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/a087ae608b1d963bcb4f03826f62feb74054a2a7"><code>a087ae6</code></a> [pre-commit.ci] pre-commit autoupdate</li>
<li>Additional commits viewable in <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.17.3...v4.20.0">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.

<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 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)

</details>

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.