Bump taskcluster from 96.3.1 to 96.6.1 in /tools

[dependabot]

Bumps taskcluster from 96.3.1 to 96.6.1.

Release notes

Sourced from taskcluster's releases.

v96.6.1

DEPLOYERS

▶ [patch] #7472 The queue service's workerRemovedResolver now also listens for workerStopped events from worker-manager, in addition to workerRemoved events. This ensures claimed tasks are resolved as exception/worker-shutdown as early as possible when a worker disappears. Both events are handled idempotently, so receiving both for the same worker is safe.

v96.6.0

DEPLOYERS

▶ [minor] #7472 The queue service now listens for workerRemoved events from worker-manager and immediately resolves any tasks claimed by that worker as exception/worker-shutdown, triggering an automatic retry. Previously, when a worker disappeared (due to VM preemption, crash, or manual termination), its claimed tasks would wait up to 20 minutes for the claim to expire before being retried. This new workerRemovedResolver background process runs alongside the existing claim-resolver and requires no configuration changes.

USERS

▶ [patch] #8300 Task log profiler optimizations for parsing large task logs, more memory and cpu efficient.

Automated Package Updates

• build(deps): bump flask from 3.1.2 to 3.1.3 in /clients/client-py (dd48e7e794)
• build(deps): bump werkzeug from 3.1.5 to 3.1.6 in /clients/client-py (d0511a0c8a)

v96.5.2

WORKER-DEPLOYERS

▶ [patch] #8083 Generic Worker (windows): waits for the User Profile Service (ProfSvc) to be running before performing profile operations on first boot, and fixes a bug where LoadUserProfile retry logic for "device not ready" errors never actually retried due to an incorrect error type assertion.

v96.5.1

DEPLOYERS

▶ [patch] #8292 Claim-resolver and deadline-resolver expose metrics.

v96.5.0

GENERAL

▶ [patch] Upgrades to go1.26.0

Release notes here.

WORKER-DEPLOYERS

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v96.6.1

DEPLOYERS

▶ [patch] #7472 The queue service's workerRemovedResolver now also listens for workerStopped events from worker-manager, in addition to workerRemoved events. This ensures claimed tasks are resolved as exception/worker-shutdown as early as possible when a worker disappears. Both events are handled idempotently, so receiving both for the same worker is safe.

v96.6.0

DEPLOYERS

▶ [minor] #7472 The queue service now listens for workerRemoved events from worker-manager and immediately resolves any tasks claimed by that worker as exception/worker-shutdown, triggering an automatic retry. Previously, when a worker disappeared (due to VM preemption, crash, or manual termination), its claimed tasks would wait up to 20 minutes for the claim to expire before being retried. This new workerRemovedResolver background process runs alongside the existing claim-resolver and requires no configuration changes.

USERS

▶ [patch] #8300 Task log profiler optimizations for parsing large task logs, more memory and cpu efficient.

Automated Package Updates

• build(deps): bump flask from 3.1.2 to 3.1.3 in /clients/client-py (dd48e7e794)
• build(deps): bump werkzeug from 3.1.5 to 3.1.6 in /clients/client-py (d0511a0c8a)

v96.5.2

WORKER-DEPLOYERS

▶ [patch] #8083 Generic Worker (windows): waits for the User Profile Service (ProfSvc) to be running before performing profile operations on first boot, and fixes a bug where LoadUserProfile retry logic for "device not ready" errors never actually retried due to an incorrect error type assertion.

v96.5.1

DEPLOYERS

▶ [patch] #8292 Claim-resolver and deadline-resolver expose metrics.

v96.5.0

GENERAL

▶ [patch]

... (truncated)

Commits

• 2633d8e v96.6.1
• 200ae9b Merge pull request #8308 from taskcluster/matt-boris/queueListenToWorkerStopp...
• 7d57f30 feat(queue): listen to workerStopped events
• 1914bb5 v96.6.0
• d569d38 Task log profiler optimizations (#8303)
• 667ca2a Merge pull request #8304 from taskcluster/matt-boris/queueListenToWorkerRemovals
• 7af4657 address PR review comments
• 74c162c add changelog
• e9473b9 chore: regenerate after adding get_claimed_tasks_by_worker and worker-removed...
• c039e6c feat(queue): wire WorkerRemovedResolver into queue loader
• 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)

[dependabot]

Superseded by #65.