build(deps): Bump taskcluster from 29.4.1 to 29.6.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 29.4.1 to 29.6.0.

Release notes

Sourced from taskcluster's releases.

v29.6.0

USERS

▶ [minor] bug 1638002 The Azure, AWS, and Google worker provisioners now use an instance's region or location as workerGroup, instead of the worker pool's providerId.

DEVELOPERS

▶ [minor] #2811 The Queue schema now allows for ssh:// source urls.

▶ [patch] An issue with building external urls with traceId'd clients has been fixed

OTHER

▶ Additional change not described here: bug 1637982.

v29.5.2

No changes

v29.5.1

No Changes

v29.5.0

NOTE Release automation for this release failed, so there are no docker images, binaries, or released client libraries.

GENERAL

▶ [patch] bug 1633582 Fixes an issue in the worker-manager google provider where improperly configured disk tagging caused worker creation to fail.

DEPLOYERS

▶ [minor] bug 1619652 Taskcluster logs now include traceId and requestId fields on messages that have these in context. A requestId is per http request and a traceId follows a request chain along as far as it goes so for example a graphql request to web-server -> queue -> auth.authenticateHawk are all correlatable as part of one trace.

As part of this change, by default in Kubernetes, requests between services are now routed directly using Kubernetes dns service discovery. To disable this, you can set the top-level useKubernetesDnsServiceDiscovery to false in your helm values.

▶ [patch] bug 1637104 The livelog, taskcluster-proxy, and websocktunnel Docker images now use statically-linked binaries, meaning they will not fail on startup.

▶ [patch] bug 1636189 The websocktunnel, livelog, and taskcluster-proxy images now have an /app/version.json as required by DockerFlow, and websocktunnel correctly services all three DockerFlow endpoints. In additional, all ver sion.json files including that in the main taskcluster/taskcluster image now have a correct build URL.

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v29.6.0

USERS

▶ [minor] bug 1638002 The Azure, AWS, and Google worker provisioners now use an instance's region or location as workerGroup, instead of the worker pool's providerId.

DEVELOPERS

▶ [minor] #2811 The Queue schema now allows for ssh:// source urls.

▶ [patch] An issue with building external urls with traceId'd clients has been fixed

OTHER

▶ Additional change not described here: bug 1637982.

v29.5.2

v29.5.1

No changes

v29.5.0

GENERAL

▶ [patch] bug 1633582 Fixes an issue in the worker-manager google provider where improperly configured disk tagging caused worker creation to fail.

DEPLOYERS

▶ [minor] bug 1619652 Taskcluster logs now include traceId and requestId fields on messages that have these in context. A requestId is per http request and a traceId follows a request chain along as far as it goes so for example a graphql request to web-server -> queue -> auth.authenticateHawk are all correlatable as part of one trace.

As part of this change, by default in Kubernetes, requests between services are now routed directly using Kubernetes dns service discovery. To disable this, you can set the top-level useKubernetesDnsServiceDiscovery to false in your helm values.

▶ [patch] bug 1637104 The livelog, taskcluster-proxy, and websocktunnel Docker images now use statically-linked binaries, meaning they will not fail on startup.

▶ [patch] bug 1636189

... (truncated)

Commits

• 73c6e98 v29.6.0
• c339781 Merge pull request #2834 from vnzongzna/update/golangci-lint
• cb721d6 Merge pull request #2833 from taskcluster/fix-public-redirects
• 64f3668 upgrade golangci-lint
• 8762c1d Fix perRequestInstance service discovery interaction
• 47bec89 Fixing all golangci-lint error before update
• 52ef2b6 Merge pull request #2824 from djmitche/bug1638002
• 7e85787 changelog
• 4b616fc Bug 1638002 - use region as workerGroup in Google
• 5565743 Merge pull request #2825 from djmitche/bug1637982
• 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)