Taskcluster

Latest version: v65.1.0

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

Scan your dependencies

Page 42 of 52

28.2.3

USERS

▶ [patch] [2615](https://github.com/taskcluster/taskcluster/issues/2615)
Fix error showing when creating new client/role in the UI.

▶ [patch] [bug 1525419](http://bugzil.la/1525419)
Generic worker tasks on Windows can now define environment variables that contain special characters `()%!^"<>&|`. Previously they were not escaped.

DEVELOPERS

▶ [patch]
Development environments now default to a lower per-pod CPU request, which should help reduce the compute cost of idle development environments. Run `yarn dev:init` to update these defaults for your dev environment.

28.2.2

WORKER-DEPLOYERS

▶ [patch] [bug 1624602](http://bugzil.la/1624602)
Worker-runner is now more careful to read all output from the worker when the worker exits.

USERS

▶ [patch] [bug 1552323](http://bugzil.la/1552323)
Fixes the bug: https://sentry.prod.mozaws.net/operations/taskcluster-community/issues/7766271

28.2.1

DEPLOYERS

▶ [patch]
Fix error in notify service (monitor is required)

28.2.0

GENERAL

▶ [patch] [bug 1618333](http://bugzil.la/1618333)
Changelog entries now are categorized by the audience that they are useful for

WORKER-DEPLOYERS

▶ [patch]
Now, if the worker process running in aws/gcp exits, it will be requested to worker-manager to terminate the instance.

ADMINS

▶ [patch] [bug 1622943](http://bugzil.la/1622943)
The maximum value for a worker's `lifecycle.reregistrationTimeout` is now 30 days. Values greater than this cannot be represented in the worker's temporary credentials anyway.

USERS

▶ [minor] [bug 1552323](http://bugzil.la/1552323)
Adds ability to customize checks output in taskcluster-github Checks feature.
Apart from the bug mentioned, fixes the issue https://github.com/mozilla-mobile/fenix/issues/6760

▶ [patch] [1389](https://github.com/taskcluster/taskcluster/issues/1389)
Taskcluster UI nows offers a breadcrumbs view to easily jump back and forth when
viewing indexes (/tasks/index/)

DEVELOPERS

▶ [minor] [bug 1616998](http://bugzil.la/1616998)
taskcluster-worker-runner has been renamed to worker-runner and its docs have been added to the reference section of the docs portal.

▶ [patch] [2522](https://github.com/taskcluster/taskcluster/issues/2522)
Services that use a database now log information about that database, including connection pool counts and stored-function invocations.

▶ [patch] [2555](https://github.com/taskcluster/taskcluster/issues/2555)
The azure-queue emulation library now omits expired messages from its counts. The visible effect is that pending counts for queues no longer include tasks past their deadline.

▶ [patch] [2553](https://github.com/taskcluster/taskcluster/issues/2553)
The taskcluster-lib-azqueue library now returns "batches" of messages in the order they were inserted.

OTHER

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

28.1.0

▶ [minor] [bug 1436478](http://bugzil.la/1436478)
Add a new library taskcluster-lib-entities that exposes the same API as azure-entities but uses postgres rather than azure for its database. Note that all of the services are still using azure-entities. Services will eventually switch to using this new library. Date to be decided.

▶ [minor] [bug 1306494](http://bugzil.la/1306494)
Taskcluster UI now allow users to view the diff for scope changes (similar to the github write/preview functionality).

▶ [patch] [2292](https://github.com/taskcluster/taskcluster/issues/2292)
Add a new library taskcluster-lib-azqueue that exposes the same API as the Azure Queue service but uses Postgres rather than Azure. Note that all of the services are still using Azure. Services will eventually switch to using this new library. Date to be decided.

▶ [patch] [bug 1616931](http://bugzil.la/1616931)
Generic-worker now transmits its logs via taskcluster-worker-runner, in preparation for supporting arbitrary log destinations.

▶ [patch] [bug 1621420](http://bugzil.la/1621420)
Prepare to update octokit dependency

▶ [patch] [2503](https://github.com/taskcluster/taskcluster/issues/2503)
Some schemas in the Taskcluster documentation were not displayed with a "Cannot find .." error. This has been fixed.

▶ [patch] [2486](https://github.com/taskcluster/taskcluster/issues/2486)
Taskcluster UI now allows users to add matrix rooms to the denylist addresses.

▶ [patch]
Taskcluster deployments now support sending results to New Relic (optionally). See the deployment documentation for details.

▶ [patch] [bug 1618991](http://bugzil.la/1618991)
The Go client now correctly returns an error when 500 responses are retried to exhaustion.

▶ [patch] [2498](https://github.com/taskcluster/taskcluster/issues/2498)
The database upgrade command now checks roles and permissions attributes for database users.

▶ [patch]
The linux-arm builds of generic-worker are now considered [Tier-2](https://docs.taskcluster.net/docs/reference/workers/generic-worker/support-tiers), meaning that they are not tested in CI (but are still built). Testing is also disabled on Windows 10 / amd64 due to lack of capacity, but continues for Windows 2012 / amd64 so Windows / amd64 remains a tier-1 platform.

▶ [patch] [2536](https://github.com/taskcluster/taskcluster/issues/2536)
The node-postgres library is now configured to correctly handle timezones. As no data was stored with timestamps until now, this is not a breaking change.

▶ [patch] [bug 1622052](http://bugzil.la/1622052)
The protocol between workers and worker manager now correctly negotiates capabilities.

▶ Additional changes not described here: [bug 1623183](http://bugzil.la/1623183), [#2527](https://github.com/taskcluster/taskcluster/issues/2527), [#2539](https://github.com/taskcluster/taskcluster/issues/2539).

28.0.0

▶ [MAJOR] [2328](https://github.com/taskcluster/taskcluster/issues/2328)
This version adds a temporary "widgets" API method to the notify service. This is intended to allow testing of the deployment process for Taskcluster services' backend database, and not for tracking of actual widgets.

This new API requires that Helm properties `notify.read_db_url` and `notify.write_db_url` be set correctly as documented in the [deployment documentation](https://docs.taskcluster.net/docs/manual/deploying/database).

▶ [minor]
Add worker-runner binaries to the list of release artifacts

▶ [minor] [bug 1621630](http://bugzil.la/1621630)
Support for short-circuiting of boolean logic in JSON-e templates such as `.taskcluster.yml` is restored.

▶ [patch]
AWS, GCP and Azure providers support the "shutdown" message, which requests
the worker-manager to terminate the instance

▶ [patch] [bug 1621167](http://bugzil.la/1621167)
The Taskcluster-GitHub service now uses structured logging to describe its handling of events from GitHub. See [its logging documentation](https://docs.taskcluster.net/docs/reference/integrations/github/logs) for details.

▶ Additional change not described here: [bug 1621270](http://bugzil.la/1621270).

Page 42 of 52

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.