Taskcluster

Latest version: v65.1.0

Safety actively analyzes 638388 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 23 of 52

44.17.0

GENERAL

▶ [minor] [5456](https://github.com/taskcluster/taskcluster/issues/5456)
This change adds more DB functions to allow for filtering in the DB based on worker state and quarantined status for the workers page. Previously, filtering would only happen on the initial page loaded from the DB if results were paginated. This should also speed up the workers page rendering when a filter is applied.

▶ [patch] [5529](https://github.com/taskcluster/taskcluster/issues/5529)
This patch makes it so that the `docker-compose.yml` file is updated with the new taskcluster docker image version on a `yarn release`. Previously, the version wasn't updated, so the `meta-generate` task would fail on releases. This issue first appeared in v44.16.4.

▶ [patch] [5319](https://github.com/taskcluster/taskcluster/issues/5319)
This patch migrates the legacy, `process.hrtime([time])` to the new, `process.hrtime.bigint()`.
See [Node Docs](https://nodejs.org/docs/latest-v16.x/api/process.html#processhrtimetime) for more information.

▶ [patch]
This patch upgrades dependencies to their latest minor/patch versions. Doing so fixes a handful of vulns found within Snyk and docker scans.

DEVELOPERS

▶ [patch]
Added a `cloudbuild.yaml` file for the Google Cloud Build trigger on the `main` branch.

44.16.4

USERS

▶ [patch] [5517](https://github.com/taskcluster/taskcluster/issues/5517)
This patch fixes the quarantined value on the workers table to be `n/a` if the quarantined value is in the past. This issue was first noticed in v44.16.3.

DEVELOPERS

▶ [patch]
Added docker-compose.yml for local development.

OTHER

▶ Additional change not described here: [5503](https://github.com/taskcluster/taskcluster/issues/5503).

44.16.3

GENERAL

▶ [patch]
This patch returns up the `quarantineUntil` field in the `workerManager.getWorker` and `workerManager.listWorkers` methods. This issue was first noticed in v44.15.0.

44.16.2

GENERAL

▶ [patch]
This patch adds a new field to be logged out on a failed provision call. This field will be used to measure the provisioning failed count.

USERS

▶ [patch] [5503](https://github.com/taskcluster/taskcluster/issues/5503)
Add missing task-rerun scope to github handler.

▶ [patch] [5506](https://github.com/taskcluster/taskcluster/issues/5506)
Log debug information for incoming Github webhooks.

▶ [patch] [5501](https://github.com/taskcluster/taskcluster/issues/5501)
This patch makes it so a user cannot click the `Terminate Worker` button on a Static or Standalone worker. This patch also moves the `Terminate Worker` button on the view individual worker page to the speed dial menu alongside the `Quarantine` button. These issues were first brought up in v44.15.0.

Automated Package Updates

<details>
<summary>1 Renovate updates</summary>

* Update module golang.org/x/tools to v0.1.11 (147766abb)

</details>

44.16.1

GENERAL

▶ [patch]
This fixes the default worker state of a worker not known by worker manager to be `standalone` as opposed to `unmanaged` to be consistent with the rest of the project. This issue was first brought up in v44.16.0

USERS

▶ [patch]
Fix this error (`Function listWorkers takes options: continuationToken, limit, quarantined, workerState but was given isQuarantined`) while filtering workers based on quaratine status.

44.16.0

GENERAL

▶ [patch]
Don't allow additional properties in `worker-response.yml` schema. Updated descriptions in `worker-response.yml` and `list-workers-response.yml` schemas to explain some default values that may occur in the case where the queue knows about the worker, but worker manager does not. Also, updated the GraphQL queries to extract additional needed data.

▶ [patch]
Fix schema validation issues.

▶ [patch]
Upgrade node to the latest LTS release, v16.15.1. Also upgrade `golangci-lint` to 1.46.2.

▶ [patch]
Upgrade to `go1.18.3` from `go1.18.2`.

DEPLOYERS

▶ [patch] [5042](https://github.com/taskcluster/taskcluster/issues/5042)
Add a configuration option to disable CORS configuration for the queue's S3
client. This is a step forward for supporting minio as a S3 backend.

▶ [patch] [5043](https://github.com/taskcluster/taskcluster/issues/5043)
Add a configuration option to enable `s3ForcePathStyle` for the queue's S3 client

USERS

▶ [minor] [5085](https://github.com/taskcluster/taskcluster/issues/5085)
Allow Taskcluster to rerun single task from github interface.

▶ [patch]
Replace rust-crypto by hmac-sha256 in the rust client to help with dependency deduplication

▶ [patch]
Update a few rust dependencies in the client crate to help reducing duplicates

Page 23 of 52

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.