build(deps): Bump taskcluster from 25.3.0 to 25.4.0 in /tools

[dependabot-preview]

⚠️ Dependabot is rebasing this PR ⚠️

If you make any changes to it yourself then they will take precedence over the rebase.

---

Bumps taskcluster from 25.3.0 to 25.4.0.

Release notes

Sourced from taskcluster's releases.

v25.4.0

▶ [minor] bug 1608185 Taskcluster-worker-runner now passes --with-worker-runner to generic-worker when running it directly. When running generic-worker as a Windows service, this argument should be included in the service definition.

Only generic-worker versions 25.0.0 and higher support this argument. In general, we recommend running matching versions of taskcluster-worker-runner and generic-worker.

▶ [minor] bug 1522154 Matrix notifications are now supported if a deployment is configured with credentials for a homeserver. The three fields needed are:

notify.matrix_base_url: foo # The homeserver where your client is registered
notify.matrix_user_id: bar # The user that will act on behalf of taskcluster
notify.matrix_access_token: baz # An access token for this user

If you are using riot, you can get the access token by following this guide.

▶ [patch] bug 1600071 Avoid overprovisioning for instances that take a long time to boot.

▶ [patch] #2404 Fix worker type page when the latest task has no runs. Previously, an error panel was being displayed with text "t.run is null".

▶ [patch] bug 1616922 Generic-Worker documentation is now included in the Taskcluster documentation site, and the generic-worker task payload has been slightly tightened.

• task.payload.artifacts must contain unique items
• task.payload.onExitStatus.retry must contain unique items

▶ [patch] bug 1558240 Generic-worker now outputs a newline before === Task Finished ===, to ensure that line is separated from other output in the logs.

▶ [patch] bug 1433854 Task directories from previous task runs on Windows are now more aggressively purged.

This should reduce the amount of time spent trying to delete task directories between task runs, and also the amount of logging, in addition to freeing up more disk space.

This issue always existed on the Windows version of generic-worker. A similar issue existed on macOS and Linux but was fixed in bug 1615312 which was initially tagged for release in v25.0.0, but first appeared in release 25.3.0 due to some problems with the release process.

▶ [patch] #2004 The Task Details panel in the Task view now wraps the payload text in order to

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v25.4.0

▶ [minor] bug 1608185 Taskcluster-worker-runner now passes --with-worker-runner to generic-worker when running it directly. When running generic-worker as a Windows service, this argument should be included in the service definition.

Only generic-worker versions 25.0.0 and higher support this argument. In general, we recommend running matching versions of taskcluster-worker-runner and generic-worker.

▶ [minor] bug 1522154 Matrix notifications are now supported if a deployment is configured with credentials for a homeserver. The three fields needed are:

notify.matrix_base_url: foo # The homeserver where your client is registered
notify.matrix_user_id: bar # The user that will act on behalf of taskcluster
notify.matrix_access_token: baz # An access token for this user

If you are using riot, you can get the access token by following this guide.

▶ [patch] bug 1600071 Avoid overprovisioning for instances that take a long time to boot.

▶ [patch] #2404 Fix worker type page when the latest task has no runs. Previously, an error panel was being displayed with text "t.run is null".

▶ [patch] bug 1616922 Generic-Worker documentation is now included in the Taskcluster documentation site, and the generic-worker task payload has been slightly tightened.

• task.payload.artifacts must contain unique items
• task.payload.onExitStatus.retry must contain unique items

▶ [patch] bug 1558240 Generic-worker now outputs a newline before === Task Finished ===, to ensure that line is separated from other output in the logs.

▶ [patch] bug 1433854 Task directories from previous task runs on Windows are now more aggressively purged.

This should reduce the amount of time spent trying to delete task directories between task runs, and also the amount of logging, in addition to freeing up more disk space.

This issue always existed on the Windows version of generic-worker. A similar issue existed on macOS and Linux but was fixed in bug 1615312 which was initially tagged for release in v25.0.0, but first appeared in release 25.3.0 due to some problems with the release process.

▶ [patch] #2004

... (truncated)

Commits

• 1a3d150 v25.4.0
• 3b4d286 Merge pull request #2384 from milescrabill/bug-1616649-azure-provider-avoid-b...
• 4faa2c8 Merge pull request #2421 from taskcluster/bug1433854
• cb0cd17 use correct workerId char limit
• 568335a address review feedback
• c73a974 Merge pull request #2414 from djmitche/no-exposer-double-close
• 2e241f8 Merge branch 'master' of github.com:taskcluster/taskcluster into bug1433854
• 9ec198c Merge pull request #2417 from taskcluster/bug1616922-fixTestFileArtifactTwice...
• 1e88a79 Merge pull request #2420 from helfi92/index-search-push-rather-than-replace
• 419ddb4 Add silent changelog
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)