Bump taskcluster from 96.4.0 to 97.0.1

[dependabot]

Bumps taskcluster from 96.4.0 to 97.0.1.

Release notes

Sourced from taskcluster's releases.

v97.0.1

No changes

v96.7.1

WORKER-DEPLOYERS

▶ [patch] D2G: avoids unnecessary I/O of copying cached docker image to task user's directory.

▶ [patch] #8326 Generic Worker: when running with worker-runner, the worker now checks with Worker Manager before shutting down due to idle timeout. If Worker Manager says the worker is still needed (e.g., to satisfy minCapacity), the idle timer resets instead of shutting down. Workers not running with worker-runner are unaffected.

▶ [patch] #8328 Worker Manager: the worker scanner now uses a dedicated target capacity formula for termination decisions based on pending tasks, claimed tasks, and minCapacity/maxCapacity. Previously, the provisioning formula was reused, which inflated the target by existing worker counts, so idle workers were never terminated even when minCapacity was lowered to 0.

USERS

▶ [patch] #8323 Fixes queue.listTaskGroup endpoint that in some cases didn't return full list of tasks in the given group.

Automated Package Updates

• build(deps-dev): bump ruff (4a2992b6dd)
• build(deps): bump the client-rust-deps group (6daeb5a345)
• build(deps): bump the go-deps group with 4 updates (a27fd5c923)
• build(deps): bump minimatch from 3.1.3 to 3.1.5 (6f9f3a29cb)
• build(deps): bump minimatch from 3.1.3 to 3.1.5 in /clients/client-web (f4b5f3dfef)

v96.7.0

WORKER-DEPLOYERS

▶ [minor] #7652 Generic Worker & Livelog: fix livelog temporary streaming files not being cleaned up. The livelog process creates a temp directory per stream, but since the generic worker kills it with SIGKILL, the process never has a chance to clean up. Fixed by having the generic worker create a dedicated temp directory for each livelog process (via the new LIVELOG_TEMP_DIR env var) and removing it after the process is killed.

▶ [patch] #8318 Generic Worker & Livelog: fix intermittent "address already in use" error on livelog ports. When a livelog process failed to start, an orphaned goroutine would keep polling the port and later send a duplicate PUT request to the next task's livelog process, causing its GET server to fail binding. Fixed by cancelling the goroutine on early process exit, killing orphaned livelog processes on connection failure, and fixing the livelog binary's duplicate PUT request guard which was checked but never set.

USERS

▶ [minor] #8101 Queue artifact creation (createArtifact) now accepts an optional contentLength field for S3 and object artifacts. When provided, the artifact size in bytes is stored and returned in listArtifacts, artifactInfo, and related endpoints.

Automated Package Updates

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v97.0.1

No changes

v97.0.0

WORKER-DEPLOYERS

▶ [MAJOR] #8101 Generic worker now reports artifact file sizes to the queue via the optional contentLength parameter when creating artifacts. This applies to all file-based artifacts (S3 and object) as well as log artifacts. The reported size is the original file size on disk, before any encoding such as gzip compression. This feature relies on the API changes introduced in v96.7.0 and will fail schema validation if services are not upgraded.

▶ [patch] #8339 Worker Manager: provides worker-manager:should-worker-terminate:<workerPoolId>/<workerGroup>/<workerId> scope to worker during (re)registration so the worker can properly call out to the ShouldWorkerTerminate API.

v96.7.1

WORKER-DEPLOYERS

▶ [patch] D2G: avoids unnecessary I/O of copying cached docker image to task user's directory.

▶ [patch] #8326 Generic Worker: when running with worker-runner, the worker now checks with Worker Manager before shutting down due to idle timeout. If Worker Manager says the worker is still needed (e.g., to satisfy minCapacity), the idle timer resets instead of shutting down. Workers not running with worker-runner are unaffected.

▶ [patch] #8328 Worker Manager: the worker scanner now uses a dedicated target capacity formula for termination decisions based on pending tasks, claimed tasks, and minCapacity/maxCapacity. Previously, the provisioning formula was reused, which inflated the target by existing worker counts, so idle workers were never terminated even when minCapacity was lowered to 0.

USERS

▶ [patch] #8323 Fixes queue.listTaskGroup endpoint that in some cases didn't return full list of tasks in the given group.

Automated Package Updates

• build(deps-dev): bump ruff (4a2992b6dd)
• build(deps): bump the client-rust-deps group (6daeb5a345)
• build(deps): bump the go-deps group with 4 updates (a27fd5c923)
• build(deps): bump minimatch from 3.1.3 to 3.1.5 (6f9f3a29cb)
• build(deps): bump minimatch from 3.1.3 to 3.1.5 in /clients/client-web (f4b5f3dfef)

v96.7.0

WORKER-DEPLOYERS

... (truncated)

Commits

• 6519c12 v97.0.1
• 9edf735 v97.0.0
• 67acc22 Merge pull request #8322 from taskcluster/feat/8101-artifact-sizes
• ca2d791 feat(g-w): reporting artifact size at creation time
• 89ec40f Merge pull request #8340 from taskcluster/matt-boris/wmMissingShouldWorkerTer...
• f90312d fix(worker-manager): add missing worker scope for ShouldWorkerTerminate
• 941f702 v96.7.1
• d8ff1bf Merge pull request #8327 from taskcluster/matt-boris/gwCheckWithWmBeforeIdleT...
• 3d2f5d4 address PR comments
• 4859fb5 chore(tests): add idle timeout wm shoud I terminate test
• 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 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)