Closed Bug 1827302 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 39461 - Bump json-e from 4.5.1 to 4.5.2 in /tools

Categories

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

task

Tracking

(firefox114 fixed)

RESOLVED FIXED
114 Branch
Tracking Status
firefox114 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

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

Bump json-e from 4.5.1 to 4.5.2 in /tools

Bumps json-e from 4.5.1 to 4.5.2.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/json-e/json-e/blob/main/CHANGELOG.rst">json-e's changelog</a>.</em></p>
<blockquote>
<h1>Jsone 4.5.2 (2023-04-10)</h1>
<h2>Bugfixes</h2>
<ul>
<li>Fixed a bug that caused some examples in documentation not to be rendered on json-e.js.org (<a href="https://redirect.github.com/json-e/json-e/issues/461">#461</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/json-e/json-e/commit/0653c6b051c56aac8fd8fe639a8d34b3bd26ae94"><code>0653c6b</code></a> v4.5.2</li>
<li><a href="https://github.com/json-e/json-e/commit/3d44ee4d49e45fb6b013d4d8f9a18c90104d1c53"><code>3d44ee4</code></a> Merge pull request <a href="https://redirect.github.com/json-e/json-e/issues/463">#463</a> from Zacho2/fix-docs-newline</li>
<li><a href="https://github.com/json-e/json-e/commit/60fd2a882ffc313352d5410c176c2b68e046c585"><code>60fd2a8</code></a> docs: handle arbitrary newline placement in yaml</li>
<li>See full diff in <a href="https://github.com/json-e/json-e/compare/v4.5.1...v4.5.2">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 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>

Whiteboard: [wptsync downstream] → [wptsync downstream error]
PR 39461 applied with additional changes from upstream: e2f6c7e29618b7a597491c39a9e45b851843e641
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ad09940da630 [wpt PR 39461] - Bump json-e from 4.5.1 to 4.5.2 in /tools, a=testonly
Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
You need to log in before you can comment on or make changes to this bug.