Taskcluster

Latest version: v65.1.0

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

Scan your dependencies

Page 34 of 52

39.2.0

WORKER-DEPLOYERS

▶ [patch]
This version fixes an error where a worker pool with an invalid providerId would cause all worker provisioning to cease.

USERS

▶ [minor] [3542](https://github.com/taskcluster/taskcluster/issues/3542)
Docker-worker no longer supports VNC access to interactive tasks. This support has been broken for ages and unused.

▶ [patch]
The `taskcluster-client-web` library client classes now have a `buildSignedUrlSync` method.

▶ [patch] [4056](https://github.com/taskcluster/taskcluster/issues/4056)
The taskcluster-proxy no longer follows redirects. In practice, this is only an issue when calling the artifact-related API methods that return a redirect to the artifact content. The proxy will now return the redirect response unchanged.

DEVELOPERS

▶ [minor] [3578](https://github.com/taskcluster/taskcluster/issues/3578)
The tasks table uses `task_queue_id` instead of separate `provisioner_id/worker_type` to identify task queues.
This change is applied through an online migration process.

OTHER

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

Automated Package Updates

<details>
<summary>5 Renovate updates</summary>

* Update Node.js to v14.15.2 (8689b010a)
* Update dependency hashids to v2.2.3 (7e4eec9db)
* Update dependency commander to v6.2.1 (beef8ecea)
* Update dependency newrelic to v7.0.2 (2068dbca1)
* Update dependency marked to v1.2.6 (7b44747e4)

</details>

39.1.2

USERS

▶ [patch]
The octokit throttling plugin has been removed in this release.
We did not appear to understand its assumptions. It will probably
come back later once we understand it better.

OTHER

▶ Additional changes not described here: [3892](https://github.com/taskcluster/taskcluster/issues/3892), [#4012](https://github.com/taskcluster/taskcluster/issues/4012).

Automated Package Updates

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

* Update dependency sinon to v9.2.2 (0dc9ff6f3)

</details>

39.1.1

DEPLOYERS

▶ [patch] [4034](https://github.com/taskcluster/taskcluster/issues/4034)
The queue's artifact expiration crontask now uses a much more efficient query and should be able to keep up with the load.

USERS

▶ [patch] [3797](https://github.com/taskcluster/taskcluster/issues/3797)
A race condition in github checks updates has been resolved

DEVELOPERS

▶ [patch] [4064](https://github.com/taskcluster/taskcluster/issues/4064)
Taskcluster services and docker-worker now use Node 14, the current LTS version.

OTHER

▶ Additional changes not described here: [2981](https://github.com/taskcluster/taskcluster/issues/2981), [#4100](https://github.com/taskcluster/taskcluster/issues/4100).

39.1.0

GENERAL

▶ [patch] [4059](https://github.com/taskcluster/taskcluster/issues/4059)
Fixed an issue fetching GitHub metadata when using a Taskcluster instance without the anonymous role.

This presented as unexpected 'Failed to get your artifact.' errors.

USERS

▶ [minor] [4006](https://github.com/taskcluster/taskcluster/issues/4006)
The `takscluster-client-web` library is no longer installable from a `<script>` tag.
Instead, it should be incorporated into the build process of the consuming application, like any other library.

▶ [patch]
Improved error messages related to fetching artifacts for GitHub checks.

▶ [patch] [4061](https://github.com/taskcluster/taskcluster/issues/4061)
This version fixes an issue with the "actions" button not appearing for task groups.

DEVELOPERS

▶ [patch] [3939](https://github.com/taskcluster/taskcluster/issues/3939)
The object service now supports `uploadId` in the upload process.

▶ [patch] [4074](https://github.com/taskcluster/taskcluster/issues/4074)
We now use github's library for generating app jwt tokens instead of making our own tokens

OTHER

▶ Additional changes not described here: [3951](https://github.com/taskcluster/taskcluster/issues/3951), [#3999](https://github.com/taskcluster/taskcluster/issues/3999), [#4036](https://github.com/taskcluster/taskcluster/issues/4036).

39.0.0

GENERAL

▶ [patch] [3901](https://github.com/taskcluster/taskcluster/issues/3901)
Fixed a bug where signing public S3 artifacts would result in Forbidden errors on the task and task group views.

▶ [patch] [3867](https://github.com/taskcluster/taskcluster/issues/3867)
Taskcluster-Github should now function correctly in a deployment with no scopes in the `anonymous` role.

If you have a locked-down deployment without allowing public artifacts fetching in your `anonymous` role, you must add
`queue:get-artifact:public/github/customCheckRunText.md` and `queue:get-artifact:public/github/customCheckRunAnnotations.json`
to the scopes of your task to avoid an error comment being added to your
commits. Note that this will change if you choose a custom artifact name (see custom artifact docs for more)

DEPLOYERS

▶ [MAJOR] [3713](https://github.com/taskcluster/taskcluster/issues/3713)
This version introduces a new, in-development object service. It is currently configured for a default replica count of 0, meaning that it will not run, and this is the recommended configuration. However, it will nonetheless require configuration of a new database user (`<prefix>_object`).

WORKER-DEPLOYERS

▶ [minor] [3669](https://github.com/taskcluster/taskcluster/issues/3669)
The Azure worker-manager takes additional steps to verify the identity proof
during worker registration. The identify proof is the output of the
[attested data API](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service#attested-data),
which includes details about the worker and is signed by the Azure platform.

Previously, the worker-manager checked that the message signer was issued by
one of four published intermediate certificates issued by a single root CA.
Azure is planning to expand to five more root CAs (see
[Azure TLS certificate changes](https://docs.microsoft.com/en-us/azure/security/fundamentals/tls-certificate-changes)
for details). The worker-manager now downloads an unknown intermediate
certificate, verifies that it was issued by a known root CAs, and adds it to
the list of trusted certificates. The 4 legacy intermediate certificates, still
in use in Azure as of November 2020, are pre-loaded as trusted certificates.

The worker manager now verifies that the message signer is for
`metadata.azure.com` or a subdomain. This is true for any workers in the
Azure public cloud, but not the sovereign clouds like azure.us.

One of the new root CAs uses Elliptic Curve Cryptography (ECC) instead of RSA.
The Azure worker-manager doesn't support this or other ECC certificates.
This is tracked in [issue 3923](https://github.com/taskcluster/taskcluster/issues/3923).

There is no performance change expected until Azure ships the TLS certificate
changes, planned by February 15, 2021. When new intermediate certificates are
used, there will be up to a 5 second delay on worker registration while the new
certificate is downloaded for the first time. A new manager log entry,
``registration-new-intermediate-certificate``, is emitted after a successful
download and verification, and includes the certificate details.

USERS

▶ [patch] [3899](https://github.com/taskcluster/taskcluster/issues/3899)
Docker-worker now decompresses downloaded images when they have a compressed content-encoding, as artifacts produced by docker-worker now have.

▶ [patch] [3637](https://github.com/taskcluster/taskcluster/issues/3637)
Taskcluster-Github should now avoid spamming an identical comment many times in certain situations.

▶ [patch] [3982](https://github.com/taskcluster/taskcluster/issues/3982)
The quickstart now correctly shows whether the GitHub integration is enabled for a repository.

▶ [patch] [3578](https://github.com/taskcluster/taskcluster/issues/3578)
There are two new API methods for the queue service: `listTaskQueues` and `getTaskQueue`

DEVELOPERS

▶ [minor] [3578](https://github.com/taskcluster/taskcluster/issues/3578)
The queue service now uses taskQueueId internally, instead of provisionerId/workerType, for worker info
purposes (provisioners, worker types and workers).
The `queue_provisioners` table is dropped and the `queue_worker_types` table is renamed to `task_queues`.

▶ [patch] [3832](https://github.com/taskcluster/taskcluster/issues/3832)
Octokit now uses github's own retry/rate-limit plugins instead of our own.

OTHER

▶ Additional changes not described here: [3712](https://github.com/taskcluster/taskcluster/issues/3712), [#3715](https://github.com/taskcluster/taskcluster/issues/3715), [#3717](https://github.com/taskcluster/taskcluster/issues/3717), [#3719](https://github.com/taskcluster/taskcluster/issues/3719), [#3808](https://github.com/taskcluster/taskcluster/issues/3808), [#3881](https://github.com/taskcluster/taskcluster/issues/3881), [#3898](https://github.com/taskcluster/taskcluster/issues/3898), [#3917](https://github.com/taskcluster/taskcluster/issues/3917), [#3935](https://github.com/taskcluster/taskcluster/issues/3935), [#3937](https://github.com/taskcluster/taskcluster/issues/3937), [#3954](https://github.com/taskcluster/taskcluster/issues/3954), [#3986](https://github.com/taskcluster/taskcluster/issues/3986), [#4009](https://github.com/taskcluster/taskcluster/issues/4009).

38.0.6

GENERAL

▶ [patch] [3906](https://github.com/taskcluster/taskcluster/issues/3906)
Creating comments on github is fixed in this release

▶ [patch] [3903](https://github.com/taskcluster/taskcluster/issues/3903)
Scopes are now expanded in between using a certificate's scopes and checking `authorizedScopes`
as well.

USERS

▶ [patch] [3908](https://github.com/taskcluster/taskcluster/issues/3908)
E-mail and Slack notifications should now correctly link to the group when the group ID does not match the task ID.

Page 34 of 52

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.