1906752 - [wpt-sync] Sync PR 47040 - Bump jsonschema from 4.17.3 to 4.23.0 in /tools

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

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

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

Bump jsonschema from 4.17.3 to 4.23.0 in /tools

Bumps jsonschema from 4.17.3 to 4.23.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.23.0</h2>

<h2>What's Changed</h2>
<ul>
<li>Add some typing to the <code>exceptions.py</code> module by <a href="https://github.com/DanielNoord"><code>@DanielNoord</code></a> in <a href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1019">python-jsonschema/jsonschema#1019</a></li>
<li>Declare support for 3.13 by <a href="https://github.com/rominf"><code>@rominf</code></a> in <a href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1282">python-jsonschema/jsonschema#1282</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/rominf"><code>@rominf</code></a> made their first contribution in <a href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1282">python-jsonschema/jsonschema#1282</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.22.0...v4.23.0">https://github.com/python-jsonschema/jsonschema/compare/v4.22.0...v4.23.0</a></p>
<h2>v4.22.0</h2>

<h2>What's Changed</h2>
<ul>
<li>Improve <code>best_match</code> (and thereby error messages from <code>jsonschema.validate</code>) in cases where there are multiple <em>sibling</em> errors from applying <code>anyOf</code> / <code>allOf</code> -- 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 (<a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1250">#1250</a>).</li>
<li>(Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as <code>==</code> would.</li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/shinnar"><code>@shinnar</code></a> made their first contribution in <a href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1224">python-jsonschema/jsonschema#1224</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.21.1...v4.22.0">https://github.com/python-jsonschema/jsonschema/compare/v4.21.1...v4.22.0</a></p>
<h2>v4.21.1</h2>

<ul>
<li>Slightly speed up the <code>contains</code> keyword by removing some unnecessary validator (re-)creation.</li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.21.0...v4.21.1">https://github.com/python-jsonschema/jsonschema/compare/v4.21.0...v4.21.1</a></p>
<h2>v4.21.0</h2>

<h2>What's Changed</h2>
<ul>
<li>Fix the behavior of <code>enum</code> in the presence of <code>0</code> or <code>1</code> to properly consider <code>True</code> and <code>False</code> unequal (<a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1208">#1208</a>).</li>
<li>Special case the error message for <code>{min,max}{Items,Length,Properties}</code> when they're checking for emptiness rather than true length.</li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/otto-ifak"><code>@otto-ifak</code></a> made their first contribution in <a href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1208">python-jsonschema/jsonschema#1208</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.20.0...v4.21.0">https://github.com/python-jsonschema/jsonschema/compare/v4.20.0...v4.21.0</a></p>
<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>

</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.23.0</h1>
<ul>
<li>Do not reorder dictionaries (schemas, instances) that are printed as part of validation errors.</li>
<li>Declare support for Py3.13</li>
</ul>
<h1>v4.22.0</h1>
<ul>
<li>Improve <code>best_match</code> (and thereby error messages from <code>jsonschema.validate</code>) in cases where there are multiple <em>sibling</em> errors from applying <code>anyOf</code> / <code>allOf</code> -- 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 (<a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1250">#1250</a>).</li>
<li>(Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as <code>==</code> would.</li>
</ul>
<h1>v4.21.1</h1>
<ul>
<li>Slightly speed up the <code>contains</code> keyword by removing some unnecessary validator (re-)creation.</li>
</ul>
<h1>v4.21.0</h1>
<ul>
<li>Fix the behavior of <code>enum</code> in the presence of <code>0</code> or <code>1</code> to properly consider <code>True</code> and <code>False</code> unequal (<a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1208">#1208</a>).</li>
<li>Special case the error message for <code>{min,max}{Items,Length,Properties}</code> when they're checking for emptiness rather than true length.</li>
</ul>
<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.</li>
</ul>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/cfe8a4071672b9652c8f083faed1c4ffa7d67705"><code>cfe8a40</code></a> Document the other change, and call this 4.23.0.</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/25127a152475f37ea236d44f2a649d16cecc90e5"><code>25127a1</code></a> Merge pull request <a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1282">#1282</a> from rominf/rominf-python3.13</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/40410c45e7851816cc7f426aa6699530eb0d589e"><code>40410c4</code></a> Declare support for 3.13</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/3a44b4bd6596e58755a3af84d39b552bbb562dba"><code>3a44b4b</code></a> Merge pull request <a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1276">#1276</a> from python-jsonschema/pre-commit-ci-update-config</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/6a00e35d5d1e304c99308e57a5fb0d7da29508fe"><code>6a00e35</code></a> [pre-commit.ci] pre-commit autoupdate</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/84fee431b262643247cad58e2fd6eec186bbaedf"><code>84fee43</code></a> Merge pull request <a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1273">#1273</a> from python-jsonschema/pre-commit-ci-update-config</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/a90d6e29c65e661c22afef81d575e84a14e85cd4"><code>a90d6e2</code></a> [pre-commit.ci] pre-commit autoupdate</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/c3a8641bf2d2de2c6e5d54569ca44bee121e4504"><code>c3a8641</code></a> Merge pull request <a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1272">#1272</a> from python-jsonschema/pre-commit-ci-update-config</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/deb53982d59d98f86ef18f50cd098066af70003e"><code>deb5398</code></a> [pre-commit.ci] pre-commit autoupdate</li>
<li><a href="https://github.com/python-jsonschema/jsonschema/commit/7fd28c3936375deb1180a45624d37c58d1576cac"><code>7fd28c3</code></a> Update the (ancient draft3) color format for newer webcolors.</li>
<li>Additional commits viewable in <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.17.3...v4.23.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>

Bugzilla

[wpt-sync] Sync PR 47040 - Bump jsonschema from 4.17.3 to 4.23.0 in /tools

Categories

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

Tracking

(Not tracked)

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Crash Data

Security

(public)

User Story

Description