chore(deps): update dependency taskcluster-client to v66 #190
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:
65.0.1
->66.0.0
Release Notes
taskcluster/taskcluster (taskcluster-client)
v66.0.0
Compare Source
USERS
▶ [MAJOR] #7082
This change comprises three elements:
docker
rather thanpodman
if the DockerWorker task has the
privileged
capability enabled. This should result infewer tasks failing due to differences in default behaviour between docker
and podman privileged containers.
based on the declared capabilities of the Docker Worker task it was
converting, rather than deriving the target Generic Worker scopes solely
from the original Docker Worker task scopes. This allowed a task with
insufficient scopes under Docker Worker to gain elevated privileges under
Generic Worker.
v65.4.0
Compare Source
USERS
▶ [patch] #7083
Fixes query validation in pagination queries that were throwing
500 InternalServerError
instead of400 InputError
DEVELOPERS
▶ [minor] #7089
Fixes an issue when cancelling a task didn't remove it from the pending queue.
This made worker-manager think there are more pending tasks than there actually were, and create more workers.
v65.3.0
Compare Source
GENERAL
▶ [patch]
Upgrades to node v20.14.0 and go1.22.4 (SECURITY release).
DEPLOYERS
▶ [minor] #7035
Helm chart allows conditional deployment of several resource types:
This might be useful in the deployments that use custom Ingress or manage secrets and configs externally.
Example usage:
helm template --values .. --set "skipResourceTypes[0]"=ingress --set "skipResourceTypes[0]"=secert .
WORKER-DEPLOYERS
▶ [minor] #7076
Worker Runner now uses IMDSv2 instead of IMDSv1 in EC2. IMDSv1 is being phased out by Amazon.
DEVELOPERS
▶ [patch] #7080
Fixes github service issue during cancellation of the previous runs that were not created.
Response code was not checked properly which resulted in sending same error for each new build.
▶ [patch] #6668
Fixes an issue to support yarn run for dev:start and dev:stop scripts
v65.2.0
Compare Source
USERS
▶ [minor] #7070
Generic Worker now sets the environment variable TASKCLUSTER_INSTANCE_TYPE in task commands to the instance type of the worker, if configured. This matches the (undocumented) behaviour of Docker Worker. D2G also passes this environment variable through to podman, to emulate Docker Worker's behaviour.
▶ [patch]
Fixes UI issue in worker view where error was shown despite worker being found.
▶ [patch] #7059
D2G now includes
libvirt
OS group in generated Generic Worker task payloads that use Docker Worker KVM device.▶ [patch] #6954
Fixes an issue with github badges that timed out on non-existing branches.
▶ [patch]
Tasks using
notify.pulse.<topic>.on-<event>
routes now send out messagesusing the specified topic. This means it's now possible to subscribe to
specific topics.
DEVELOPERS
▶ [minor] #5073
Github service supports
issue_comment
events to trigger jobs through/tasckluster param
comments in open Pull Requests..taskcluster.yml
in default branch should allow this withpolicy.allowComments: collaborators
value.Tasks would be rendered with
tasks_for = "github-issue-comment"
andevent.taskcluster_comment = param
This is an implementation of RFC 168
▶ [patch] #6567
yarn generate
commands will attempt to runpg_dump
inside the docker container if local binary is missing or its version is different from the server version.Automated Package Updates
2 Dependabot updates
8daf19d
)60ca422
)v65.1.0
Compare Source
USERS
▶ [minor] #5967
Allows Docker Worker payloads to be used on the
insecure
Generic Worker engine, translated byd2g
.v65.0.2
Compare Source
USERS
▶ [patch] #7025
Fixes JavaScript error in "Create Worker Pool" page that was introduced in the last release.
Adds link to "Errors" in workers navigation bar.
Automated Package Updates
2 Dependabot updates
42569cc
)2bccd8b
)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.