Bump taskcluster from 68.0.4 to 82.0.0 in /tools

[dependabot]

Bumps taskcluster from 68.0.4 to 82.0.0.

Release notes

Sourced from taskcluster's releases.

v82.0.0

WORKER-DEPLOYERS

▶ [MAJOR] #7086 Worker Manager introduces launchConfigId and schema changes:

• New workerManager configuration object in launch configs that includes:
  • launchConfigId - unique identifier for tracking and error attribution
  • capacityPerInstance - specify worker capacity per instance (old top-level propert is supported but is deprecated)
  • initialWeight - control provisioning probability (0-1)
  • maxCapacity - hard limit on number of instances per config

The provisioner distributes load across configs by:

• Dynamically adjusting weights based on error rates and capacity limits
• Temporarily reducing usage of configs experiencing errors
• Maintaining error history in a 1-hour sliding window

v81.0.3

GENERAL

▶ [patch] #7532 Generic Worker (windows): fix cache ownership issues. Clean up ACLs so prior task users aren't referenced anymore.

USERS

▶ [patch] #7527 Fixes an issue introduced in Generic Worker 81.0.0 where the Chain of Trust certificate would not contain all of the additional data specified in the task-provided chain-of-trust-additional-data.json file.

Generic Worker 81.0.0 enhanced the Chain of Trust task payload feature to support adding arbitrary additional data to the public/chain-of-trust.json artifact. This was implemented in [PR #7507](taskcluster/taskcluster#7507) by allowing the task to write additional data to the file chain-of-trust-additional-data.json in the task directory. The feature was meant to merge the content of this file with the generated chain-of-trust.json file before publishing it as an artifact. However, the merge of the two json objects was broken if they contained common ancestors. For example, the generated chain-of-trust.json file contains a top level object property environment. If the task-provided chain-of-trust-additional-data.json file also contained a top level object property environment containing further properties, they would be omitted from the resulting environment property in the published Chain of Trust certificate.

▶ [patch] #7014 Generic Worker now adds environment.imageHash (always), and environment.imageArtifactHash (when present) to public/chain-of-trust.json when running Docker Worker Chain of Trust tasks, to match Docker Worker behaviour.

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v82.0.0

WORKER-DEPLOYERS

▶ [MAJOR] #7086 Worker Manager introduces launchConfigId and schema changes:

• New workerManager configuration object in launch configs that includes:
  • launchConfigId - unique identifier for tracking and error attribution
  • capacityPerInstance - specify worker capacity per instance (old top-level propert is supported but is deprecated)
  • initialWeight - control provisioning probability (0-1)
  • maxCapacity - hard limit on number of instances per config

The provisioner distributes load across configs by:

• Dynamically adjusting weights based on error rates and capacity limits
• Temporarily reducing usage of configs experiencing errors
• Maintaining error history in a 1-hour sliding window

v81.0.3

GENERAL

▶ [patch] #7532 Generic Worker (windows): fix cache ownership issues. Clean up ACLs so prior task users aren't referenced anymore.

USERS

▶ [patch] #7527 Fixes an issue introduced in Generic Worker 81.0.0 where the Chain of Trust certificate would not contain all of the additional data specified in the task-provided chain-of-trust-additional-data.json file.

Generic Worker 81.0.0 enhanced the Chain of Trust task payload feature to support adding arbitrary additional data to the public/chain-of-trust.json artifact. This was implemented in [PR #7507](taskcluster/taskcluster#7507) by allowing the task to write additional data to the file chain-of-trust-additional-data.json in the task directory. The feature was meant to merge the content of this file with the generated chain-of-trust.json file before publishing it as an artifact. However, the merge of the two json objects was broken if they contained common ancestors. For example, the generated chain-of-trust.json file contains a top level object property environment. If the task-provided chain-of-trust-additional-data.json file also contained a top level object property environment containing further properties, they would be omitted from the resulting environment property in the published Chain of Trust certificate.

▶ [patch] #7014 Generic Worker now adds environment.imageHash (always), and environment.imageArtifactHash (when present) to public/chain-of-trust.json

... (truncated)

Commits

• a8f7e64 v82.0.0
• bbdb469 Worker manager launch configurations (#7266)
• 2ce1c82 Merge pull request #7536 from taskcluster/matt-boris/modernizeGo
• 20402d7 add OnExitStatus test validations for nil pointer dereference regression purp...
• ae11a8f chore: modernize go code
• 6c85de6 Merge pull request #7538 from taskcluster/HGI-to-GHI
• 6381baf Merge pull request #7537 from taskcluster/fix-changelog
• 96ffb40 Fix changelog PR link 5727 -> 7527
• 170392d no-op test envvar rename HGI -> GHI
• da740f7 v81.0.3
• 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 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 #652.