Bump taskcluster from 44.22.1 to 48.0.0

[dependabot]

Bumps taskcluster from 44.22.1 to 48.0.0.

Release notes

Sourced from taskcluster's releases.

v48.0.0

DEPLOYERS

▶ [patch] #6067 Worker-manager now considers stoppingCapacity when estimating the required number of workers to start, preventing failed to start workers from growing beyond maxCapacity and slowing down the scanner loop.

USERS

▶ [MAJOR] #6059 It is now possible to seal a task group which is an operation to prevent additional tasks from being added.

New APIs:

• HTTP API queue.sealTaskGroup to seal task group and prevent addition of new tasks to it. This operation is irreversible.
• HTTP API queue.getTaskGroup to return task group information without tasks (use queue.listTaskGroup to return information with tasks)
• Pulse exchange exchange/taskcluster-queue/v1/task-group-sealed reports when a task group is sealed.

Updated APIs:

• HTTP API queue.createTask returns HTTP 409 error if task group was sealed.
• HTTP API queue.listTaskGroup returns extra fields schedulerId, expires, sealed.
• Pulse exchange exchange/taskcluster-queue/v1/task-group-resolved publishes extra fields schedulerId, expires, sealed.

UI updates:

• Task group view displays expiration and sealing time.
• Task group view actions includes seal task group action.

OTHER

▶ Additional change not described here: #6052.

v47.1.2

GENERAL

▶ [patch] Add error handling for docker image release process.

v47.1.0

GENERAL

▶ [minor] This upgrades Node.js to the latest LTS version available, v18.13.0. Previous version was v16.19.0 and it was scheduled to hit EoL later this year.

View the release schedule here.

▶ [patch] Docker worker json schema payload has been tweaked for cleaner go code generation. No functional impact anticipated.

▶ [patch]

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v48.0.0

DEPLOYERS

▶ [patch] #6067 Worker-manager now considers stoppingCapacity when estimating the required number of workers to start, preventing failed to start workers from growing beyond maxCapacity and slowing down the scanner loop.

USERS

▶ [MAJOR] #6059 It is now possible to seal a task group which is an operation to prevent additional tasks from being added.

New APIs:

• HTTP API queue.sealTaskGroup to seal task group and prevent addition of new tasks to it. This operation is irreversible.
• HTTP API queue.getTaskGroup to return task group information without tasks (use queue.listTaskGroup to return information with tasks)
• Pulse exchange exchange/taskcluster-queue/v1/task-group-sealed reports when a task group is sealed.

Updated APIs:

• HTTP API queue.createTask returns HTTP 409 error if task group was sealed.
• HTTP API queue.listTaskGroup returns extra fields schedulerId, expires, sealed.
• Pulse exchange exchange/taskcluster-queue/v1/task-group-resolved publishes extra fields schedulerId, expires, sealed.

UI updates:

• Task group view displays expiration and sealing time.
• Task group view actions includes seal task group action.

OTHER

▶ Additional change not described here: #6052.

v47.1.2

GENERAL

▶ [patch] Add error handling for docker image release process.

v47.1.1

GENERAL

▶ [patch] This upgrades Node.js to the latest LTS version available, v18.14.1. This is a security release.

DEVELOPERS

▶ [patch]

... (truncated)

Commits

• 622aeb1 v48.0.0
• bbbb677 Merge pull request #6103 from taskcluster/feat/worker-manager-error-handling
• 57ac521 Merge pull request #6089 from taskcluster/dependabot/go_modules/golang.org/x/...
• 58cd87f build(deps): bump golang.org/x/tools from 0.5.0 to 0.6.0
• 933d2ef feat(w-m): Consider stoppingCapacity in estimator
• 90f1577 Merge pull request #6100 from taskcluster/renovate/apollo-graphql-packages
• 23df750 Update Apollo GraphQL packages to v3.12.0
• abd1cce Merge pull request #6099 from taskcluster/all-contributors/add-AmineVolk
• 24f97d4 update .all-contributorsrc [skip ci]
• 266ae2c update README.md [skip ci]
• Additional commits viewable in compare view

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)

[dependabot]

Superseded by #604.