chore(deps): update dependency taskcluster to v81 #283
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
>=44.0.0,<80.1->>=44.0.0,<81.1Release Notes
taskcluster/taskcluster (taskcluster)
v81.0.0Compare Source
GENERAL
▶ [patch]
Upgrades to go1.23.6 and golangci-lint 1.63.4
DEPLOYERS
▶ [minor] #7508
Removes Cloud Armor specific policy config from deployment templates as it was applied incorrectly.
WORKER-DEPLOYERS
▶ [MAJOR]
Generic Worker: feature
runTaskAsCurrentUser(note:TasknotTasks) has been added to replace the previous global task config settingrunTasksAsCurrentUser(which is no longer supported). Worker pools can elect to enable or disable the feature with boolean config settingenableRunTaskAsCurrentUser. Tasks with the feature enabled (task.payload.features.runTaskAsCurrentUser = true) require scopegeneric-worker:run-task-as-current-user:<provisionerID>/<workerType>.This change was introduced in order that access to this privileged feature are guarded not only by worker config settings, but also by task scopes, and furthermore the feature must be explicitly requested, in order that tasks do not unintentionally inherit the feature by virtue of overgenerous scopes or unintentionally running on a pool with the feature enabled.
▶ [patch] #7462
Generic Worker (D2G): prune docker images during garbage collection, if needed.
USERS
▶ [MAJOR]
The interactive feature will now drop users in the task container instead of the host
▶ [minor] #7506
Generic Worker Chain Of Trust feature now allows tasks to inject additional
data into
public/chain-of-trust.json. Tasks wishing to add additional fieldsshould write them as json to the file
chain-of-trust-additional-data.jsoninthe task directory. In this initial release, there are no provisions to
customise the name or path of the file. The file contents will be merged with
the default chain of trust certificate, with the default field values taking
precedence over any provided in
chain-of-trust-additional-data.json. If thefile is not created by the task, no merging will take place, and the feature
will operate as before.
▶ [minor]
Set TASK_WORKDIR environment variable for generic-worker tasks.
▶ [patch]
Fixed the
--completedflag fortaskcluster group listso it actually works instead of returning an empty list all the timeConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.