chore(deps): update dependency taskcluster-client to v61 #182
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
60.0.0->61.0.0Release Notes
taskcluster/taskcluster (taskcluster-client)
v61.0.0Compare Source
GENERAL
▶ [patch]
Generic Worker now utilizes
filepath.WalkDirinstead offilepath.Walk.filepath.WalkDirwas introduced in go1.16 and is more performant and efficient overfilepath.Walk.This may help with race conditions during artifact uploads, where a file was initially seen, but then became unavailable at upload time.
▶ [patch]
Upgrades to go1.22.1 which is a security release.
USERS
▶ [MAJOR] #6881
Google cloud workers spawned by Worker Manager now have
workerGroupset tothe Google Cloud Zone (e.g.
us-east1-d) rather than the Google CloudRegion (e.g.
us-east1). This makes it easier to issue api requests againstan instance, e.g.
gcloud compute instances delete <workerId> --zone=<workerGroup>.▶ [patch] #6890
D2G now always passes
--privilegedto the generatedpodman runcommand.Without this option, some tasks that ran successfully under Docker Worker,
including tasks without Docker Worker capabilities, would not run correctly
under Generic Worker. Please note, this only elevates the privileges inside the
podman container, which runs as the task user on the host. The privileges
inside the container are still limited to the host privileges of the task user.
▶ [patch]
Generic Worker now correctly reports the Worker Pool ID when an interactive task is attempted on a worker pool with the interactive feature disabled. Previously the task log would report the Worker Pool ID in the
exception/malformed-payloadtask run as<workerGroup>/<workerType>; now it correctly reports it as<provisionerId>/<workerType>. The Interactive feature is considered disabled when Generic Worker config settingenableInteractiveis either absent or explicitly set tofalsein the Generic Worker config.DEVELOPERS
▶ [patch]
Upgrades internal references library to use async fs operations to make upcoming node20 upgrade easier.
Automated Package Updates
7 Dependabot updates
f2bd071)ac2bb66)36fac2a)7b79a3e)ee709aa)c02ca54)0cd5033)v60.4.2Compare Source
USERS
▶ [patch]
Fixes graphql validation rules for hooks groups query.
▶ [patch] #6864
D2G now passes
--privilegedflag to the generatedpodman runcommand whenDocker Worker payload enables device capability
hostSharedMemory. Withoutthis option, the podman container could not successfully access the shared
memory, despite the inclusion of argument
--device=/dev/shm. With botharguments present (
--privilegedand--device=/dev/shm), shared memory nowappears to be available inside the podman container.
Automated Package Updates
3 Dependabot updates
280678f)be7836a)008b3fe)v60.4.1Compare Source
USERS
▶ [patch]
Fix docker worker interactive shell UI rows/cols settings.
▶ [patch] #6836
Upgrades graphql server and client libraries to graphql 16.8
▶ [patch] #6836
Upgrades graphql to 16.8.1 in ui
Automated Package Updates
1 Dependabot updates
485a491)v60.4.0Compare Source
USERS
▶ [minor] #6845
D2G now provides support for the (discontinued) disableSeccomp capability which was removed from Docker Worker, but was still used by the bugmon fuzzing project in the Community taskcluster environment. This was added to ease the migration path of this project from Docker Worker to Generic Worker.
▶ [patch] #6848
Fix an issue where an interactive session would close up when the shell would output invalid UTF-8.
▶ [patch] #6850
Add a proper TERM environment variable to interative sessions. This helps with some ncurses apps and tmux for example.
OTHER
▶ Additional change not described here: #6852.
Automated Package Updates
4 Dependabot updates
34cb19d)98d1c2c)360fdb2)19094b0)v60.3.5Compare Source
GENERAL
▶ [patch]
Switched to use
math/rand/v2(new in go1.22), removed deprecated call towindows.OpenCurrentProcessToken(), fixedstaticcheckerrors, and added astaticcheckGitHub actions workflow for our repo.▶ [patch]
Upgrades to node v18.19.1, which is a security release.
DEPLOYERS
▶ [patch]
Kubernetes lifecycle timeouts correctly set to avoid having 502s.
USERS
▶ [patch] #6795
Fixes "Raw Log" button in UI that can point to an expired artifact.
v60.3.4Compare Source
GENERAL
▶ [patch]
Upgrades to go1.22.0
USERS
▶ [patch] #6820
Fixes scope view in the UI. Search by scope shows roles and clients that use given scope.
Automated Package Updates
1 Dependabot updates
ecf9462)v60.3.3Compare Source
DEVELOPERS
▶ [patch]
Upgrades to yarn v4.1.0
Automated Package Updates
5 Dependabot updates
319f484)cde9bb3)35e1bf6)87b4265)8944d36)v60.3.2Compare Source
WORKER-DEPLOYERS
▶ [patch]
Worker Runner now checks for termination notice when starting the Google provider.
When Worker Runner runs, the instance may already be scheduled to be shutdown. So on Google provider startup, we now check for this case.
This functionality mimics what's already in place for AWS.
This change also decreases the time Worker Runner checks to see if the instance is scheduled to be shutdown from 30 seconds to 15 seconds on the Google and Azure providers, as they each have a 30 second notice before a hard-shutdown Google: https://cloud.google.com/compute/docs/instances/spot#preemption-process Azure: https://learn.microsoft.com/en-us/azure/virtual-machines/spot-vms.
USERS
▶ [patch] #6801
Fixes a bug in notify service where multiple messages to the same channel were not sent.
Adds
204status code to the email, matrix, pulse, slack endoints when message was detected to be duplicate and was not sent.▶ [patch] #6793
D2G will now ensure that tasks whose max run time is exceeded still have the chance to publish artifacts.
This means that Docker Worker tasks definitions that are run under Generic Worker and are aborted due to
hitting the max run time should still publish the artifacts from the aborted docker container they ran in.
▶ [patch] #6798
Generic Worker now includes the original Docker Worker task definition in the chain of trust certificate, if the task payload is a Docker Worker task payload. Previously, it was including the internal Generic Worker representation of the task definition.
▶ [patch]
The Task Creator now defaults to a task that only takes 1 minute to run instead of 10 mins, to redue resource consumption. Tutorials updated to reflect change.
Automated Package Updates
1 Dependabot updates
c7f9d92)v60.3.1Compare Source
USERS
▶ [patch] #6789
Generic Worker no longer modifies task scopes passed to Taskcluster Proxy.
Previously there was a bug where Taskcluster Proxy would be passed the
d2g-modified scopes by Generic Worker rather than the original task scopes from
the task definition of the
queue.claimWorkresponse body. If the task was notalso explicitly assigned the required generic-worker scopes, this would result
in HTTP 401 errors from Taskcluster Proxy calls.
This has now been fixed, so that it is sufficient for tasks with a Docker
Worker payload to contain only Docker Worker scopes, not have the associated
generic-worker scopes, yet still work under Generic Worker and use the
Taskcluster Proxy feature without causing HTTP 401 errors.
v60.3.0Compare Source
GENERAL
▶ [patch]
Generic Worker now copies archives to the task user's directory before unarchiving.
WORKER-DEPLOYERS
▶ [minor] #6785
Generic Worker now exits with exit code 82 if the chain of trust key is missing.
v60.2.0Compare Source
GENERAL
▶ [patch]
Go upgrade to 1.21.6.
WORKER-DEPLOYERS
▶ [minor]
Generic Worker: adds
unarchivesubcommand to thegeneric-workerbinary.USERS
▶ [minor] #6720
The taskcluster UI now shows errors when an action's input does not match the
action.schemav60.1.3Compare Source
GENERAL
▶ [patch] #6235
Migrates to aws sdk v3.
v60.1.2Compare Source
USERS
▶ [patch] #6563
Ensure livelog and interactive tasks tunnels work after a websocktunnel restart.
v60.1.0Compare Source
WORKER-DEPLOYERS
▶ [patch] #6779
Interactive feature data race fixed, whereby an error could cause a concurrent read and write of process state in different go routines.
USERS
▶ [minor] bug 1874568
Fixes token expiry issue for Auth0 login strategy that was not refetched.
▶ [patch] #6495
Improve changelog rendering in UI
DEVELOPERS
▶ [patch]
Added helper script to make it easier to run websocktunnel locally.
Automated Package Updates
1 Dependabot updates
c97cf83)v60.0.1Compare Source
GENERAL
▶ [patch] #6762
Generic Worker: Tasks internally translated by D2G will add exit code 128 to the retry exit status array for retrying on an intermittent docker image pull issue.
Automated Package Updates
5 Dependabot updates
d0f8546)fdf2641)77c73c5)1465e06)924ecbb)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.