chore(deps): update dependency taskcluster-client to v85 #220
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:
83.5.2
->85.0.1
Release Notes
taskcluster/taskcluster (taskcluster-client)
v85.0.1
Compare Source
WORKER-DEPLOYERS
▶ [patch] #7789
Generic Worker: Artifact uploads properly fail on 4xx status codes. Issue first noticed in v84.1.1
USERS
▶ [patch] #7786
Github service comments back when taskcluster command in issue comment didn't produce any tasks
▶ [patch] bug 1559766
d2g adds
localhost.localdomain
to /etc/hostsv85.0.0
Compare Source
WORKER-DEPLOYERS
▶ [MAJOR]
Generic Worker: renamed the following worker configuration options to avoid confusion:
absoluteHighMemoryThreshold
-->minAvailableMemoryBytes
relativeHighMemoryThreshold
-->maxMemoryUsagePercent
v84.2.1
Compare Source
USERS
▶ [patch] #7498
Further UI memory optimizations for the TaskGroup page to avoid using too much memory during intensive updates.
v84.2.0
Compare Source
WORKER-DEPLOYERS
▶ [minor] #7770
Generic Worker: adds additional resource monitoring auto-abortion configuration to better fine-tune how your worker aborts running task processes.
absoluteHighMemoryThreshold
: The minimum amount of available memory (in bytes) required before considering task abortion. If available memory drops below this value, it may trigger an abort. Default:524288000
(500MiB).relativeHighMemoryThreshold
: The percentage of total system memory usage that, if exceeded, contributes to the decision to abort the task. Default:90
.allowedHighMemoryDurationSecs
: The maximum duration (in seconds) that high memory usage conditions can persist before the task is aborted. Default:5
.Generic Worker will auto-abort a task if the total system memory used percentage is greater than
relativeHighMemoryThreshold
AND the available memory is less thanabsoluteHighMemoryThreshold
for longer thanallowedHighMemoryDurationSecs
, unlessdisableOOMProtection
is enabled.USERS
▶ [patch] #7769
Generic Worker: resource monitor will print out its usage summary after aborting the task.
Automated Package Updates
5 Dependabot updates
9730050
)6298cb2
)f3154fd
)e1544fb
)c8320ed
)v84.1.2
Compare Source
DEPLOYERS
▶ [patch] #7763
Helm chart forces metrics-only deployments to have
replicas: 0
ifprometheus.enabled
isfalse
USERS
▶ [patch] #7771
Fixes UI error on TaskGroup page
v84.1.1
Compare Source
GENERAL
▶ [patch]
Upgrades to Node.js v22.16.0 and go1.24.4 [SECURITY].
USERS
▶ [patch] #7498
Optimizes UI memory usage for some pages that were caching table data
OTHER
▶ Additional change not described here: bug 1971309.
Automated Package Updates
1 Dependabot updates
8c55b37
)v84.1.0
Compare Source
GENERAL
▶ [patch] #7712
Upgrades to go1.24.3 [SECURITY].
More details here.
DEPLOYERS
▶ [minor] #7707
Adds Prometheus metrics support to the monitor via a new plugin. Metrics can now be registered using
MonitorManager.registerMetric()
, similar to log types. When enabled, each configured service and background job starts a separate server on port9100
to expose metrics for Prometheus scraping.Example minimal Kubernetes
values.yml
configuration:If your cluster does not support the
monitoring.googleapis.com/v1/PodMonitoring
resource, add"podmonitoring"
to.skipResourceTypes[]
to prevent deployment failures.ADMINS
▶ [minor] #7646
The github service will now respect github rate limits instead of hammering against it as fast as it can
USERS
▶ [patch] #7757
Fixed input validation for some queue service endpoints to return a 400 error instead of a 500 error when validation fails.
DEVELOPERS
▶ [patch] #7612
Exposes worker-manager provision loop metrics to prometheus.
▶ [patch]
Modernized logger interface by replacing deprecated
logger.warn
withlogger.warning
to avoid DeprecationWarning in Python environments.Automated Package Updates
10 Dependabot updates
77d81f2
)562d292
)d146d04
)8bca2bb
)b88065d
)9b41394
)d6b8b95
)16c9599
)303865a
)4e1a719
)v84.0.2
Compare Source
USERS
▶ [patch] #4943
Fixes UI error "buildSignedUrl missing required credentials" shown directly after login due to missing credentials.
v84.0.1
Compare Source
GENERAL
▶ [patch]
Upgrades to Node.js v22.15.1 (SECURITY).
More info here.
WORKER-DEPLOYERS
▶ [patch] bug 1967254
Generic Worker (d2g): uses info log level when uploading error artifacts if the artifact was marked optional. Previously, the log would contain
[taskcluster:error]
which Treeherder would identify as a failure, even if the task is successful.▶ [patch] #7630
Generic Worker: improves artifact upload process by parallelizing the scanning of the system for file/directory artifacts from the payload.
v84.0.0
Compare Source
DEPLOYERS
▶ [MAJOR] #7287
Helm chart includes HorizontalPodAutoscaler for all web services which is not enabled by default.
Can be enabled per-service, and when enabled, deployment's "replicas" field will be ignored.
USERS
▶ [minor]
Pass /dev/nvidia* devices to
docker run
whenallowGPUs
is true. This works around the issue described in https://github.com/NVIDIA/nvidia-container-toolkit/issues/48, where GPUs disappear if a systemd daemon reload happens.v83.10.1
Compare Source
USERS
▶ [patch] #7686
Fixed task retrigger for tasks with underscored priority values (like
very_low
).▶ [patch] #7575
Taskcluster Yaml debugger properly simulates issue comment events, previously it was failing.
▶ [patch] #7474
UI: fixes hamburger menu closing too quickly
▶ [patch]
Generic Worker (D2G): no longer logs translated payload and our recommendation to migrate all tasks to Generic Worker payload format. Worker config
d2gConfig.logTranslation
is now unused and will be removed in a future release.▶ [patch] #7716
Generic Worker code internal refactoring: moved task startup/teardown steps into task features. No change to behaviour other than slight changes to both worker logs and task logs.
v83.10.0
Compare Source
WORKER-DEPLOYERS
▶ [minor] #7628
Generic Worker: adds a
Metadata
feature (controlled with worker configenableMetadata
[default:true
], not controllable in the task payload) that writes out a filegeneric-worker-metadata.json
(in the current working directory of the generic worker process) containing information about the last task run.Currently, the file will look something like this:
Additional data may be added to this file in future releases.
v83.9.1
Compare Source
v83.8.0
Compare Source
WORKER-DEPLOYERS
▶ [minor] #7678
D2G: pre and post-task-processing (image pulling/loading/saving, copying artifacts out of container, creating chain of trust additional data file, removing container/volumes, handling max runtime) now happens within the D2G Task Feature in Generic Worker, as opposed to within the resulting translated task payload. This slims the translated task payload to only the
docker run ...
command.▶ [patch] #7685
Fixes node-forge issue with certificates being removed during chain verification process,
which allowed Azure
registerWorker()
calls fail after some time.This happened when multiple certs had same subject hash but different issuers.
▶ [patch] #5786
Properly reap proxy processes when stopping the taskcluster proxy feature
Automated Package Updates
6 Dependabot updates
501c8ad
)fe67ad2
)1008f65
)76b7158
)c927822
)0f33f56
)v83.7.0
Compare Source
GENERAL
▶ [patch]
Upgrades to Node.js v22.15.0 and yarn v4.9.1
WORKER-DEPLOYERS
▶ [minor] #7670
Removed ECC Azure certificate and include extra information in errors.
v83.6.0
Compare Source
DEPLOYERS
▶ [minor] #3924
Removed bundled root CAs that exist in node already.
WORKER-DEPLOYERS
▶ [minor] #7670
Azure provider includes up-to-date intermediate certificates to speed up worker registration process,
expired certificates has been removed.
USERS
▶ [minor]
Add support for windows interactive tasks
v83.5.8
Compare Source
WORKER-DEPLOYERS
▶ [patch] #7671
D2G: removes unneeded
kvm
andlibvirt
OS groups for generic worker task user if KVM device is requested.USERS
▶ [patch] #7664
Fix an issue where taskcluster would try to report checks to github that exceeded the max allowed length if the log contained long lines in its tail
v83.5.7
Compare Source
GENERAL
▶ [patch]
Upgrades to go1.24.2.
DEVELOPERS
▶ [patch] #7099
Updated azure test certificates.
v83.5.6
Compare Source
WORKER-DEPLOYERS
▶ [patch] #7368
Generic Worker: increase performance of artifact uploads by removing a redundant file copy operation.
USERS
▶ [patch]
UI: don't show
Requested
filter option onQueue Workers
view, link toW-M Workers
filtered view when clicking onRequested Capacity
orStopping Capacity
buttons, don't redirect to Worker Manager Worker Pools page after saving Worker Pool config changes.v83.5.5
Compare Source
WORKER-DEPLOYERS
▶ [patch] #7652
Generic Worker: remove temp file created while adding additional data to chain of trust file.
USERS
▶ [patch]
Fixes duplicate taskcluster windows after external signin.
v83.5.4
Compare Source
GENERAL
▶ [patch]
Refactor web-server middleware
DEVELOPERS
▶ [patch]
UI: Improves login window after redirect
v83.5.3
Compare Source
GENERAL
▶ [patch]
Fix 3rd party login header issue
WORKER-DEPLOYERS
▶ [patch] #7650
Generic Worker (windows): fixes cache mount issue where generic worker fails to reset permissions on the cache directory. First noticed in v81.0.3.
Configuration
📅 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.