Closed Bug 1823812 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 39127 - Bump taskcluster from 47.0.2 to 48.1.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 39127 into mozilla-central (this bug is closed when the sync is complete).

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

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

Bump taskcluster from 47.0.2 to 48.1.0 in /tools

Bumps taskcluster from 47.0.2 to 48.1.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/taskcluster/taskcluster/releases">taskcluster's releases</a>.</em></p>
<blockquote>
<h2>v48.1.0</h2>
<h3>GENERAL</h3>
<p>▶ [minor]
jsonschema2go: jsonschema default values are encoded into struct tags of generated go types for use with github.com/mcuadros/go-defaults.</p>
<p>In order to utilise this new features, callers should call <code>defaults.SetDefaults(&val)</code> before calling <code>json.Unmarshal(data, &val)</code>.</p>
<p>▶ [patch]
Go upgrade from 1.19.5 to 1.19.7. Also upgraded golangci-lint from 1.50.1 to 1.51.2.</p>
<p>Node.js upgrade from 18.14.1 to 18.15.0.</p>
<h3>USERS</h3>
<p>▶ [patch]
Dashboard displays worker manager provisioning stats separately. Values are being automatically reloaded every 30 seconds.</p>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6109">#6109</a>
The worker-manager methods <code>createWorker</code>, <code>listWorkersForWorkerGroup</code>,
<code>updateWorker</code>, and <code>worker</code> had an extraneous colon (<code>:</code>) character in their
URL path. This colon has been removed. The old paths (containing the colon)
will continue to work, but the new paths are preferred.</p>
<h2>v48.0.0</h2>
<h3>DEPLOYERS</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6067">#6067</a>
Worker-manager now considers <code>stoppingCapacity</code> when estimating the required number of workers to start, preventing failed to start workers from growing beyond <code>maxCapacity</code> and slowing down the scanner loop.</p>
<h3>USERS</h3>
<p>▶ [MAJOR] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6059">#6059</a>
It is now possible to seal a task group which is an operation to prevent additional tasks from being added.</p>
<p>New APIs:</p>
<ul>
<li>HTTP API <code>queue.sealTaskGroup</code> to seal task group and prevent addition of new tasks to it. This operation is irreversible.</li>
<li>HTTP API <code>queue.getTaskGroup</code> to return task group information without tasks (use <code>queue.listTaskGroup</code> to return information with tasks)</li>
<li>Pulse exchange <code>exchange/taskcluster-queue/v1/task-group-sealed</code> reports when a task group is sealed.</li>
</ul>
<p>Updated APIs:</p>
<ul>
<li>HTTP API <code>queue.createTask</code> returns HTTP <code>409</code> error if task group was sealed.</li>
<li>HTTP API <code>queue.listTaskGroup</code> returns extra fields <code>schedulerId</code>, <code>expires</code>, <code>sealed</code>.</li>
<li>Pulse exchange <code>exchange/taskcluster-queue/v1/task-group-resolved</code> publishes extra fields <code>schedulerId</code>, <code>expires</code>, <code>sealed</code>.</li>
</ul>
<p>UI updates:</p>
<ul>
<li>Task group view displays expiration and sealing time.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/taskcluster/taskcluster/blob/main/CHANGELOG.md">taskcluster's changelog</a>.</em></p>
<blockquote>
<h2>v48.1.0</h2>
<h3>GENERAL</h3>
<p>▶ [minor]
jsonschema2go: jsonschema default values are encoded into struct tags of generated go types for use with github.com/mcuadros/go-defaults.</p>
<p>In order to utilise this new features, callers should call <code>defaults.SetDefaults(&val)</code> before calling <code>json.Unmarshal(data, &val)</code>.</p>
<p>▶ [patch]
Go upgrade from 1.19.5 to 1.19.7. Also upgraded golangci-lint from 1.50.1 to 1.51.2.</p>
<p>Node.js upgrade from 18.14.1 to 18.15.0.</p>
<h3>USERS</h3>
<p>▶ [patch]
Dashboard displays worker manager provisioning stats separately. Values are being automatically reloaded every 30 seconds.</p>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6109">#6109</a>
The worker-manager methods <code>createWorker</code>, <code>listWorkersForWorkerGroup</code>,
<code>updateWorker</code>, and <code>worker</code> had an extraneous colon (<code>:</code>) character in their
URL path. This colon has been removed. The old paths (containing the colon)
will continue to work, but the new paths are preferred.</p>
<h2>v48.0.0</h2>
<h3>DEPLOYERS</h3>
<p>▶ [patch] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6067">#6067</a>
Worker-manager now considers <code>stoppingCapacity</code> when estimating the required number of workers to start, preventing failed to start workers from growing beyond <code>maxCapacity</code> and slowing down the scanner loop.</p>
<h3>USERS</h3>
<p>▶ [MAJOR] <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6059">#6059</a>
It is now possible to seal a task group which is an operation to prevent additional tasks from being added.</p>
<p>New APIs:</p>
<ul>
<li>HTTP API <code>queue.sealTaskGroup</code> to seal task group and prevent addition of new tasks to it. This operation is irreversible.</li>
<li>HTTP API <code>queue.getTaskGroup</code> to return task group information without tasks (use <code>queue.listTaskGroup</code> to return information with tasks)</li>
<li>Pulse exchange <code>exchange/taskcluster-queue/v1/task-group-sealed</code> reports when a task group is sealed.</li>
</ul>
<p>Updated APIs:</p>
<ul>
<li>HTTP API <code>queue.createTask</code> returns HTTP <code>409</code> error if task group was sealed.</li>
<li>HTTP API <code>queue.listTaskGroup</code> returns extra fields <code>schedulerId</code>, <code>expires</code>, <code>sealed</code>.</li>
<li>Pulse exchange <code>exchange/taskcluster-queue/v1/task-group-resolved</code> publishes extra fields <code>schedulerId</code>, <code>expires</code>, <code>sealed</code>.</li>
</ul>
<p>UI updates:</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/taskcluster/taskcluster/commit/fa6cdbdf9a2aa6616cb6997e5f91e14a33685c87"><code>fa6cdbd</code></a> v48.1.0</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/8f7733207dc5f313060179c4536d3e7b66542297"><code>8f77332</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6114">#6114</a> from taskcluster/feat/ui-dashboard-improvements</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/2ecc626ee037a36e2f9d8c2bb5ebf9434ac33712"><code>2ecc626</code></a> feat(ui): Reordered stats widget on dashboard.</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/4feb99d20d6331ead9a619b56bd1afa3454f452c"><code>4feb99d</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6113">#6113</a> from taskcluster/jsonschema2go-defaults</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/377a57b2bcb64a952bebfc6adb37f092361316f8"><code>377a57b</code></a> Remove blank line</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/2d2ec7c1621cff1c4231aa089fe911040d33714d"><code>2d2ec7c</code></a> jsonschema2go: Support default values for type:(boolean|string)</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/fd69f27b8aec150d342aa6f07b6beb259829df93"><code>fd69f27</code></a> Revert "feat(tools): Use *bool instead of bool in jsonschema in go"</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/8cb6216e44b66c2895644860c40910cde3f9ce17"><code>8cb6216</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6115">#6115</a> from taskcluster/revert-6112-dependabot/npm_and_yarn...</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/ef2f47a50c80bf83e8d3bd8a075e4b7fe898a4be"><code>ef2f47a</code></a> Revert "build(deps): bump matrix-js-sdk from 15.6.0 to 23.5.0"</li>
<li><a href="https://github.com/taskcluster/taskcluster/commit/d2d7ba79fc5040671efb1191cef725fbed478f45"><code>d2d7ba7</code></a> Merge pull request <a href="https://redirect.github.com/taskcluster/taskcluster/issues/6112">#6112</a> from taskcluster/dependabot/npm_and_yarn/matrix-js-s...</li>
<li>Additional commits viewable in <a href="https://github.com/taskcluster/taskcluster/compare/v47.0.2...v48.1.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 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]
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
Whiteboard: [wptsync downstream error] → [wptsync downstream]
You need to log in before you can comment on or make changes to this bug.