NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #4526 most downloaded on PyPI
Python client for Taskcluster
Latest stable
116.0.0
Last release 12 days ago
10 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
502 releases · first in 2014
Drag across the ruler to compare, or tap a release to open it.
The object service remains entirely experimental and further breaking changes will be made without major version bumps.
▶ [patch] #4272
The experimental object.uploadObject endpoint has been removed and replaced with object.createUpload. The object service remains entirely experimental and further breaking changes will be made without major version bumps.
▶ [patch] #4276 The worker-manager service will now start up even if one of its providers is down or misconfigured. Worker pools using that provider will not be provisioned, but other pools will continue to operate normally.
▶ [patch] #4336
Worker-Runner now correctly includes the workerGroup and workerId properties in error reports.
▶ [MAJOR] #4262
Tasks now have a projectId property that can be used to distinguish tasks for different purposes run in the same Taskcluster deployment. The queue.createTask method now requires scope queue:create-task:project:<projectId>, permitting administrative control over which clients can create tasks for which projects.
The default projectId is none. To avoid permissions errors on upgrade, we recommend that queue:create-task:project:none be added to the anonymous role before upgrading to this version. Once the upgrade is complete, callers may be modified to create tasks with non-default projectId and given appropriate scopes.
▶ [minor] #4270
Task manipulation (rerun, cancel, schedule) is now controlled by scopes related to the task's projectId, completing implementation of RFC#163. With this change, and with the inclusion of projectId in task definitions, administrators can control task manipulation by granting queue:<verb>-task-in-project:<projectId> scopes to the appropriate entities.
▶ [patch]
Upgrade to Sentry v6, but disable the new
session tracking feature
with autoSessionTracking: false, to avoid collecting more data than is
needed.
▶ [MAJOR] #3581
Client methods that took two separate provisionerId and taskQueueId parameters take now a
single parameter (workerPoolId or taskQueueId depending on the service involved).
Affected methods are queue.claimWork, queue.pendingTasks, purgeCache.purgeCache and purgeCache.purgeRequests.
The API maintains compatibility at the URL level.
▶ [MAJOR] #4058
The queue.getArtifact and queue.getLatestArtifact methods now also return a JSON body containing the URL from which the artifact can be downlodaed, in addition to the existing behavior, returning a 303 redirect.
This is a major change only because it changes the function signatures in the Go client.
▶ [minor] #3580 The queue service API responses will now include the taskQueueId, which will match provisionerId/workerType, which are also returned. Also, it is now possible to create tasks supplying a taskQueueId instead of the separate provisionerId and workerType identifiers.
▶ [minor] #4247
Updating an artifact from a reference type to link type now correctly updates the artifact type.
▶ [patch] #4248 Fixed an issue where listing tasks with link artifacts would cause errors.
▶ [patch] #4269
The task properties projectId and taskQueueId are now displayed in the Taskcluster UI, and referenced appropriately in the documentation.
▶ [patch] bug 1562993 generic-worker now only reports the first error it encounters when a task fails or hits an exception.
▶ [minor] #4058
Client libraries no longer treat redirects as errors. The methods that return redirects are those which involve fetching artifacts, and typically these have required generating signed URLs. With this change, these methods can be called directly and will return a JSON payload containing a url property from which the artifact can be downloaded. The fetch API does not support reading bodies from redirects, so this functionality is not available in taskcluster-client-web, which treats redirects as errors.
▶ [minor] #2393 On the page where all roles are listed, added Delete icon beside each role. This helps to delete role faster without going to the Role page.
▶ [minor] Taskcluster now sports a Rust client!
▶ [patch] #3789 Fixed an issue where when there's no more data, the continuationToken property was not being omitted, but being returned as just an empty string. Depending on implementation, that could cause a caller to loop endlessly calling the purge cache endpoint.
▶ Additional changes not described here: #3868, #4250, #4275, #4279, #4281, #4295, #4296, #4298, #4256.
<details> <summary>72 Renovate updates</summary>
</details>
Your coding agent can read these notes before it upgrades. Set up the MCP server →
No changes
No changes
▶ [minor] This version removes the unused deployment configuration variable queue.use_cloud_mirror and queue.public_artifact_ec2_proxies. Neither serv
▶ [minor]
This version removes the unused deployment configuration variable queue.use_cloud_mirror and queue.public_artifact_ec2_proxies. Neither served any useful purpose, and it is unlikely that either value appears in any deployment configuration.
▶ [patch] #4125
Workerpools now correctly understand the reregistrationTimeout option.
▶ [MAJOR] #3773
Support for superseding has been removed. See the linked issue for the detailed reasoning. While workers still allow supersederUrl in payloads, it has no effect. Older workers running with newer services that try to supersede tasks will encounter errors. No known instances of superseding exist.
▶ [MAJOR] #4123
The taskcluster-client-web library no longer implements OIDCCredentialAgent. This agent interfaced with a login.taskclutser.net service that no longer exists.
▶ [MAJOR] #3604 The notify service no longer supports irc notifications. IRC is declining in popularity and no known deployments of Taskcluster support this functionality, but it is nonetheless considered a breaking API change.
▶ [minor] #4050
The queue has a new artifact type, link, allowing links between artifacts on the same task.
▶ [patch] #4057 All clients (JS, Python, Go, Web, Shell) now fail when an API method results in a redirect, rather than following that redirect. The API methods that return redirects are those related to Taskcluster artifacts, and these methods must be accessed by building and fetching a signed URL.
▶ [patch] #2721
Taskcluster-proxy now correctly proxies "non-canonical" URLs, such as those containing // or urlencoded values.
▶ [patch] #3878 The Taskcluster UI now handles artifacts better, avoiding huge URLs that expire quickly.
▶ [patch] #3983 The UI will no longer fail when viewing a task with dependencies that have expired.
▶ [patch] #4199
The sift dependency has been updated again, to a version that does not cause #4061.
▶ [patch] #1064
The taskcluster command now parses errors from the API, and does not show the command usage when an error occurs.
▶ [patch] #3758
The taskcluster command will now display a warning after a short delay if it is expecting a request payload on stdin.
▶ [minor] #3578
The queue service now uses taskQueueId internally instead of the pair provisionerId/workerType for tasks.
▶ [patch] #3894 Postgres errors now include a Sentry fingerprint to help distinguish them in error reports.
▶ Additional changes not described here: #2398, #2875, #3466, #3665, #3739, #3751, #3888, #4072, #4125, #4209, #3718.
<details> <summary>57 Renovate updates</summary>
</details>
▶ [patch] This version fixes an error where a worker pool with an invalid providerId would cause all worker provisioning to cease.
▶ [patch] This version fixes an error where a worker pool with an invalid providerId would cause all worker provisioning to cease.
▶ [minor] #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 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.
▶ [minor] #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.
▶ Additional change not described here: #3940.
<details> <summary>5 Renovate updates</summary>
</details>
▶ [patch] The octokit throttling plugin has been removed in this release. We did not appear to understand its assumptions. It will probably come back
▶ [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.
▶ Additional changes not described here: #3892, #4012.
<details> <summary>1 Renovate updates</summary>
</details>
▶ [patch] #4034 The queue's artifact expiration crontask now uses a much more efficient query and should be able to keep up with the load.
▶ [patch] #4034 The queue's artifact expiration crontask now uses a much more efficient query and should be able to keep up with the load.
▶ [patch] #3797 A race condition in github checks updates has been resolved
▶ [patch] #4064 Taskcluster services and docker-worker now use Node 14, the current LTS version.
▶ [patch] #4059 Fixed an issue fetching GitHub metadata when using a Taskcluster instance without the anonymous role.
▶ [patch] #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.
▶ [minor] #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 This version fixes an issue with the "actions" button not appearing for task groups.
▶ [patch] #3939
The object service now supports uploadId in the upload process.
▶ [patch] #4074 We now use github's library for generating app jwt tokens instead of making our own tokens
▶ Additional changes not described here: #3951, #3999, #4036.
▶ [patch] #3901 Fixed a bug where signing public S3 artifacts would result in Forbidden errors on the task and task group views.
▶ [patch] #3901 Fixed a bug where signing public S3 artifacts would result in Forbidden errors on the task and task group views.
▶ [patch] #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)
▶ [MAJOR] #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).
▶ [minor] #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, 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 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.
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.
▶ [patch] #3899 Docker-worker now decompresses downloaded images when they have a compressed content-encoding, as artifacts produced by docker-worker now have.
▶ [patch] #3637 Taskcluster-Github should now avoid spamming an identical comment many times in certain situations.
▶ [patch] #3982 The quickstart now correctly shows whether the GitHub integration is enabled for a repository.
▶ [patch] #3578
There are two new API methods for the queue service: listTaskQueues and getTaskQueue
▶ [minor] #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 Octokit now uses github's own retry/rate-limit plugins instead of our own.
▶ Additional changes not described here: #3712, #3715, #3717, #3719, #3808, #3881, #3898, #3917, #3935, #3937, #3954, #3986, #4009.
▶ [patch] #3906 Creating comments on github is fixed in this release
▶ [patch] #3906 Creating comments on github is fixed in this release
▶ [patch] #3903
Scopes are now expanded in between using a certificate's scopes and checking authorizedScopes
as well.
▶ [patch] #3908 E-mail and Slack notifications should now correctly link to the group when the group ID does not match the task ID.
▶ [patch] #3874 The notify service now has enough scopes to handle notifications on Taskcluster instances without the anonymous role.
▶ [patch] #3874 The notify service now has enough scopes to handle notifications on Taskcluster instances without the anonymous role.
▶ [patch] #3884
Clients created with third-party sign-in (e.g., taskcluster signin) will no longer be disabled if they contain assume:anonymous or scopes in that role.
▶ [patch] #3899
Docker-worker now skips gzipping artifacts with an .lz4 extension, in addition to the existing list of extensions.
▶ [patch] #3873
The /provisioners/<worker-type> view now works correctly, fixing the error about reading property replace of null.
▶ Additional change not described here: #3837.
▶ [patch] Setting a node DEBUG env var via the debug field of service configs is supported again. If left unset it will default to ''. Example:
▶ [patch]
Setting a node DEBUG env var via the debug field of service configs is supported again.
If left unset it will default to ''. Example:
auth:
debug: '*'
▶ [patch] #3865 Livelog TLS support is now functional.
▶ [patch] #3851
The GitHub quickstart tool now generates correct .taskcluster.yml files, among other bugfixes.
▶ [patch] #3836 The web UI no longer fails with "ext.certificate.expiry < now".
▶ [patch] #3831 This version fixes an issue introduced in v38.0.0 which would cause the log viewer to display 401 errors.
▶ [patch]
Config types of env:list now generate the correct type in helm schemas.
▶ [patch] Fix one usage of Octokit in release machinery to fix releases
▶ [patch] Fix one usage of Octokit in release machinery to fix releases
▶ [patch] This version fixes an error in docker-worker's release script that caused the 38.0.0 release to fail.
▶ [patch] This version fixes an error in docker-worker's release script that caused the 38.0.0 release to fail.
▶ Additional change not described here: #3738.
Nothing published for this version
…its API is considered stable (in other words, breaking changes will result in a major version bump).
▶ [patch] #3659
Slack and Email notifications' Task Group URLs are now correct (containing /tasks).
▶ [patch] #3639
taskDefined messages will now always have an unscheduled status.
▶ [patch] #3631
Calling a JS Client constructor with no arguments works again -- assuming that any necessary configuration was passed to taskcluster.config(..).
▶ [minor] #3538
DB function get_workers is now deprecated.
▶ [patch] #3619
The tools/workerproto Go package is now available for external use, and its API is considered stable (in other words, breaking changes will result in a major version bump).
▶ Additional change not described here: #3591.
▶ [minor] A new queue deployment configuration variable sign_public_artifact_urls has been added which enables AWS URL signing for all S3 artifacts wh
▶ [minor]
A new queue deployment configuration variable sign_public_artifact_urls has been added which enables AWS URL signing for all S3 artifacts when true.
▶ [minor] #3606
Slack support has been added to the notifications service. You can now
send notifications to Slack channels by using a
notify.slack.C123456.on-any style route, or by using the new /slack
API endpoint.
▶ [patch] #3588
Database URLs can now be specified in the configuration with ssl=authorized, in which case Taskcluster will validate the Postgres server's SSL/TLS certificate against trusted root CAs. It is unusual for databases to be deployed with such certificates. See the documentation for details.
▶ [patch]
The tutorial in the documentation has been updated and modified to offer better guidance for different deployments of Taskcluster. The ui.site_specific configuration has a new, optional tutorial_worker_pool_id property (documented here) defining a worker pool for use by readers of the tutorial.
▶ [patch] #3561 Bug fix: calls to workermanager.updateWorker for the static provider have been fixed.
▶ [patch] #3358 The "badge" SVGs provided by the GitHub service now render correctly instead of as black shapes.
▶ [patch] #3495 The web-based schema viewer now shows descriptions of each field.
▶ [minor] #3579 The purge-cache, built-in, and worker-manager services now use taskQueueId internally, instead of provisionerId/workerType.
▶ [patch] #3473 Docker-worker has been ugpraded to use a newer version of dockerode, and no longer directly uses dockerode-promise.
▶ Additional changes not described here: bug 1668111, #3035, #3210, #3287, #3543, #3544, #3599, #3525.
▶ [patch] #3513 Node has been upgraded to 12.18.4 to address CVE-2020-8201.
▶ [patch] #3513 Node has been upgraded to 12.18.4 to address CVE-2020-8201.
▶ [patch] #3501
The worker-manager expire-errors job now correctly runs the error expiration process.
▶ [minor] #3347
The Azure provider now accepts an ignoreFailedProvisioningStates property in its launch configs which will cause it to ignore ProvisioningState/failed/<code> states on VMs. This is specifically useful for ignoring OSProvisioningTimedOut when the Azure VM agent is not running.
▶ [patch] #3346 The Azure provider now looks only for well-understood failure-related states in the Azure API to determine when a worker has failed. In cases where these measures miss an event, (re)registrationTimeouts will terminate the worker.
▶ [patch] #3058
The worker-manager's Azure provider now more accurately tracks the state of workers, and will not mark a worker RUNNING until it has called registerWorker.
▶ Additional changes not described here: #3036, #3502, #3503.
▶ [patch] #3175 Taskcluster's Github integration has been updated to the new standard for webhooks detailed in this post
▶ [patch] #3175 Taskcluster's Github integration has been updated to the new standard for webhooks detailed in this post
▶ [patch] The taskcluster-hooks-scheduler will no longer crash while trying to report errors firing hooks.
▶ [minor] #3189
The workerManager.removeWorker API method now works correctly for the static provisioner, and a new updateWorker API method supports modifying workers after they have been created.
▶ [patch] #3483
Faced with an error reclaiming a task, docker-worker will now correctly call reportException with reason internal-error.
▶ [patch] #3456
The workerManager.createWorker API method now correctly limits the workerGroup and workerId properties as described in the worker schema (38 characters, no dots).
▶ [minor] bug 1563191 generic-worker now logs the full task payload json schema if a task's payload fails json schema validation.
▶ [patch] #3355 The Taskcluster-GitHub service no longer throws errors on unknown pull-request actions in GitHub webhooks.
▶ [patch] #3464
Timestamps in the task status runs array are now formatted like all other timestamps in the Taskcluster API, without a trailing +00:00.
▶ [patch] #3354 This release handles error from malformed github check artifacts.
▶ [MAJOR] #3216 The auth, github, hooks, index, and notify services no longer take Helm config .azure_account_id, and auth no longer takes Helm config
▶ [MAJOR] #3216
The auth, github, hooks, index, and notify services no longer take Helm config <service>.azure_account_id, and auth no longer takes Helm config auth.azure_account_key, as these services no longer talk to Azure.
▶ [minor] #3216
The queue service no longer accepts the optional, and probably-unused, queue.azure_report_chance and queue.azure_report_threshold Helm configurations.
▶ [minor] #3168
The worker-manager now supports a scalingRatio that determines how much worker capacity to spawn per pending task.
The scalingRatio is a ratio of worker capacity to pending tasks - a ratio of 1.0 means that 1 capacity will be added for each pending task.
▶ [minor] #3033
The worker-manager updates the expires timestamp for AWS workers that are set to expire in less than a day.
Updating the expires timestamp is now handled in the worker-scanner scan() loop for all providers.
▶ [patch] bug 1637302 Docker-worker now allows configuring which artifacts it should compress on upload.
▶ [minor] bug 1623749 Docker-worker now allows features to be disabled in the worker config.
▶ [minor] bug 1623749 Docker-worker now allows scopes for devices and privileged containers to be per-pool, rather than global.
▶ [minor] #2973 Support docker images from tasks with only a docker v1.2 manifest.
▶ [minor] #1986
The maximum length of the hookGroupId and hookId identifiers is now 1000.
▶ [patch] #3366 A serious bug in dependency handling, introduced in v35.0.0, has been fixed. The issue occurred when a task on which more than 100 other tasks depend was resolved. In this case, some, but not all, of the dependent tasks would be marked pending.
▶ [patch] bug 1637302 Don't compress dmg files by default in docker worker.
▶ [patch] bug 1637302 Don't compress dmg or zst files by default in generic worker.
▶ [patch] #2992 Private artifacts are now accessable via the UI.
▶ [patch] #3398
This version upgrades JSON-e to 4.1.0, and in particular the $switch operator can now be used in hook task templates and in .taskcluster.yml files and everywhere else Taskcluster uses JSON-e.
▶ [patch] #3328
Database function compatbiility guarantees are now included in db/fns.md for reference by engineers writing database versions.
Takcluster-lib-entities has been removed from the codebase, as no entities-style tables remain.
▶ Additional changes not described here: #3178, #3334, #3337, #3342, #3344, #2910.
▶ [MAJOR] #2937 Github checks are now stored in a table called github_checks, and github integrations are now stored in a table called github_integrat
▶ [MAJOR] #2937
Github checks are now stored in a table called github_checks, and github integrations are now stored in a table called github_integrations. Both are accessed directly, rather than via taskcluster-lib-entities. This migration takes about 10 seconds for a million-row table.
▶ [MAJOR] #3216
The auth, github, hooks, index, and notify services no longer take Helm config <service>.azure_account_id, and auth no longer takes Helm config auth.azure_account_key, as these services no longer talk to Azure.
▶ [MAJOR] #3148 The tables in web-server are now all relational. The migration drops all data in these tables, which will have the effect of signing out all users and requiring them to sign in again. But it is a very quick upgrade.
Sign-ins will not work until the web-server service has been upgraded to this version (that is, sign-ins will not work during the time between the database upgrade and the services upgrade, nor if services are downgraded back to v35.0.0).
The web server service continues to honor web_server.azure_crypto_key, but now optionally takes an additional Helm variable web_server.db_crypto_keys as described in the deployment documentation
▶ [minor] #2933
The Queue service's workers, worker_types, and provisioners are now stored in a normal database table and access directly, rather than via taskcluster-lib-entities. If the queue_workers_entities table has many rows, this migration could take some time. Consider dropping all, or some, rows from the table before beginning the migration.
▶ [minor] #3083
The auth service's clients are now stored in the clients table and the service accesses that information directly, rather than via taskcluster-lib-entities. As the number of clients is small, this migration should be very fast.
▶ [minor] #2936 The hooks service now stores hooks and ancillary information about Pulse queues and hook history in normal database tables, without the use of taskcluster-lib-entities. This migration is quick.
The hooks service continues to honor hooks.azure_crypto_key, but now optionally takes an additional Helm variable hooks.db_crypto_keys as described in the deployment documentation
▶ [minor] #3216
The queue service no longer accepts the optional, and probably-unused, queue.azure_report_chance and queue.azure_report_threshold Helm configurations.
▶ [minor] #2931 The secrets service now stores its secrets in a normal table, without the use of taskcluster-lib-entities. The migration should be quick, as secrets are typically few in number (hundreds).
The secrets service continues to honor secrets.azure_crypto_key, but now optionally takes an additional Helm variable secrets.db_crypto_keys as described in the deployment documentation
▶ [patch] #3245
The taskcluster/websocktunnel and taskcluster/livelog docker images now include a leading v in their tags, e.g., taskcluster/websocktunnel:v36.0.0.
▶ [patch] A worker pool with no launch configs will no longer cause errors (although it will also not create any workers!)
▶ [patch] #3169
If workerTypeMetadata is given in a generic-worker worker pool definition, its contents will now be merged with the metadata from the provider and passed to generic-worker.
▶ [patch] bug 1654086 This version fixes a bug which would cause the hooks service to crash when sending error reports to denylisted addresses.
▶ [patch] bug 1645032 User IDs as received from Auth0 in the Mozilla-Auth0 login strategy are no longer suffixed with github usernames or firefox-accounts emails. In practice, such user IDs are unused.
▶ [patch] #3272
A mapping between DB and TC versions is now maintained automatically in db/versions/README.md.
▶ [patch] #3289
The DB schema is now documented in db/schema.md.
▶ [patch] #3276
The main branch of development on the Taskcluster repository is now named main.
▶ [patch] #2928 taskcluster-lib-postgres now allows calling stored functions with named arguments.
▶ Additional changes not described here: #3170, #3176, #3184, #3185, #3224, #3285, #3290, #3301.
▶ [patch] #2887 Generic-worker now supports reporting runtime errors to worker-manager via worker-runner.
▶ [patch] #2887 Generic-worker now supports reporting runtime errors to worker-manager via worker-runner.
▶ [MAJOR] #3148 The web-server service now stores Github access tokens in a dedicated table and accesses them directly, rather than via taskcluster-lib-entities. This upgrade drops existing tokens, meaning that users will need to sign in again after the upgrade is applied. This migration is very fast.
▶ [MAJOR] With this version, the auth, hooks, and secrets services no longer verify signatures on rows read from database tables. This is in preparation for a future version where these tables will no longer contain signatures.
▶ [minor] #2937
Github builds are now stored in a table called github_builds, and accessed directly rather than via taskcluster-lib-entities. This migration can process at least 40,000 rows in no more than a few seconds. For a table larger than that, deleting the table contents before running the migration is an option. This table backs the "status" and "badge" endpoints, so missing data is of minor consequence.
▶ [minor] #2938 The auth service's roles are now stored in a normal database table and accessed directly. This is a quick migration.
▶ [minor] #2935 The index service now uses its tables directly, rather than via taskcluster-lib-entities. This is step 2, a continuation of https://github.com/taskcluster/taskcluster/pull/3141. Step 2 involved creating new DB functions and refactoring the service itself to use the new functions. The db upgrade should be very fast.
▶ [minor] #3112 The queue service now uses its artifact-related database tables directly, rather than via taskcluster-lib-entities.
▶ [minor] #2932 The queue service now uses its task- and task-group-related database tables directly, rather than via taskcluster-lib-entities.
▶ [minor] #3030 The worker manager's worker pool errors are now stored in a normal database table. This should be a small migration.
▶ [minor] #3240 Worker pool errors are now properly listable by workerPoolId.
▶ [patch] #3222
The persistent errors about missing function digest(text, unknown) logged by the database are now fixed.
▶ [patch] #3191
The task.extra.github.customCheckRun.annotationsArtifactName property is now correctly consulted for the name of the annotations artifact, as documented.
▶ [patch] The taskcluster-lib-postgres library now allows any Postgres collation that sorts ASCII characters correctly.
Nothing published for this version
▶ [MAJOR] #2934 Migrates Postgres Phase I table notify.denylisted_notification_entities to Postgres Phase II table notify.denylisted_notifications.
▶ [MAJOR] #2934
Migrates Postgres Phase I table notify.denylisted_notification_entities to
Postgres Phase II table notify.denylisted_notifications.
▶ [patch] #3116
The db upgrade and downgrade scripts now verify that the default database collation is en_US.UTF8. No other collation is allowed.
Unfortunately, changing the default collation requires dumping and re-creating the database.
▶ Additional changes not described here: bug 1636193, #3093, #3147, bug 1635455.
▶ [patch] bug 1637302 Docker-worker now automatically gzips artifacts before uploading them. It sets content-encoding in the S3 headers so that most c
▶ [patch] bug 1637302 Docker-worker now automatically gzips artifacts before uploading them. It sets content-encoding in the S3 headers so that most consumers should be able to transparently handle decompression.
▶ [MAJOR] #3012
An encrypted column "secret" has been added to the workers table. The
worker-manager service now requires an additional environment variable DB_CRYPTO_KEYS
to be set which is a JSON array where each element is an object of the form.
{
"id": "a unique identifier",
"algo": "aes-256",
"key": "32 bytes of base64 string"
}
Note that for this upgrade it will only be an array of a single object.
▶ [patch] bug 1638921 Kubernetes cron tasks are now configured with concurrencyPolicy: Forbid, to prevent multiple pods of the same job from running concurrently.
▶ [patch] #3080
Docker-worker is now more careful to shut down only when it is idle and has not begun to claim a task, avoiding race conditions that could lead to claim-expired tasks.
▶ [patch] #3012 Worker runner can now re-register a worker with worker-manager, refreshing its credentials. This allows workers to run for an unlimited time, so long as they continue to check in with the worker manager periodically. Both docker-worker and generic-worker, as of this version, support this functionality. Older worker versions will simply terminate when their credentials expire.
▶ [patch] Docker-worker now includes an error message in the task log when uploading an artifact fails
▶ [patch] #2883
Endpoints that return worker pools now contain an existingCapacity field that contains the total
amount of capacity for the worker pool between all workers that are not stopped.
▶ [patch] #3004
Generic-worker now uses the task's credentials to fetch artifacts specified in the mounts property of the task's payload. This will allow use of private artifacts in mounts.
▶ [patch] #2882 Workerpools lists and views in the ui now show the amount of currently existing capacity is provided by the workers in the pool and the pending count of tasks.
▶ [minor] #3013
Github integration can now set annotations for check runs.
By default it will read public/github/customCheckRunAnnotations.json but it can be overridden by setting
task.extra.github.customCheckRun.annotationsArtifactName. The json will be passed along unmodified.
▶ Additional changes not described here: bug 1638921, #2887, #2890, #3021, #3067, #3079, #2962.
▶ [patch] Worker Manager now avoids scanning all the workers table in memory to avoid possible OOM issues.
▶ [patch] Worker Manager now avoids scanning all the workers table in memory to avoid possible OOM issues.
▶ [patch] bug 1607605 Generic-worker now supports shutting down gracefully when instructed to do so by worker-runner, such as when a cloud VM is being terminated.
▶ [patch] bug 1639713
Tasks using the hostSharedMemory device capability will now properly mount /dev/shm from the host into the container.
▶ [minor] #2877 The wmworkers_entities table has now been migrated to use a relational table. The new table is called workers. wmworkers_entities will
▶ [minor] #2877
The wmworkers_entities table has now been migrated to use a relational table.
The new table is called workers. wmworkers_entities will get deleted.
▶ [patch] Release tasks now have access to taskcluster-proxy
▶ [patch] Release tasks now have access to taskcluster-proxy
▶ [patch] An incorrect use of a relative path caused sign-ins to fail in v30.0.1. This has been fixed.
▶ [patch] An incorrect use of a relative path caused sign-ins to fail in v30.0.1. This has been fixed.
▶ [patch]
Fix docker worker not working in the latest release of Taskcluster. It was
previously throwing taskVolumeBindings is not iterable.
▶ [patch] #2876 The purge cache UI view now allows filtering a search result by cache name.
▶ Additional change not described here: #2845.
▶ [patch] A typo causing index service not to start up in 30.0.0 is now fixed.
▶ [patch] A typo causing index service not to start up in 30.0.0 is now fixed.
The hidden notify.updateWidgets API method, but this method was never meant to be used so this removal is not considered a breaking change.
▶ [patch] bug 1638047
This release fixes a bug where the web UI opens the log viewer for any text/plain artifacts, which breaks for private artifacts. The web UI will now only use the log viewer for text/plain *.log files.
▶ [patch] bug 1587145 taskcluster-client-web now only builds a single umd asset. This asset is compatible with both cjs and esm.
▶ [minor]
Database version 11 removes the widgets table that was used to test Postgres deployment. It contains no useful data.
The hidden notify.updateWidgets API method, but this method was never meant to be used so this removal is not considered a breaking change.
▶ [patch] bug 1639913 Worker-manager now logs when a worker is removed, and includes debug logging of provisioning and scanning.
▶ [MAJOR] bug 1636321
The generic-worker configuration parameters livelogKey, livelogCertificate, livelogGETPort, livelogPUTPort, and livelogSecret are no longer needed and are prohibited in the worker's configuration.
▶ [minor] #2861 The unused and unmaintained docker-worker features balrogVPNProxy, balrogStagingVPNProxy, and relengAPIProxy have been removed.
▶ [patch] bug 1638370
Azure provider no longer has a race condition between registerWorker and checkWorker.
▶ [patch] Docker-worker will now fail early with a useful error message if the loopback audio or video devices are not available, but are configured.
▶ [patch]
The docker-worker version is now logged in the serviceContext.version property of its structured logs.
▶ [patch] bug 1627769 Worker lifecycle defaults are now being properly applied.
▶ [patch] #1061 In client-shell added flag --verbose/-v for getting log to stderr for all the commands.
▶ [patch] The docker-worker payload format is now available in Taskcluster's online documentation.
▶ [patch] #2844 All services are now invoked from the root of the monorepo directory.
▶ Additional changes not described here: bug 1636164, bug 1636174, #2822, #2838, #2844.
▶ [minor] bug 1638002 The Azure, AWS, and Google worker provisioners now use an instance's region or location as workerGroup, instead of the worker po
▶ [minor] bug 1638002
The Azure, AWS, and Google worker provisioners now use an instance's region or location as workerGroup, instead of the worker pool's providerId.
▶ [minor] #2811 The Queue schema now allows for ssh:// source urls.
▶ [patch] An issue with building external urls with traceId'd clients has been fixed
▶ Additional change not described here: bug 1637982.
Nothing published for this version
▶ [patch] bug 1636292 The bug in 29.4.0 which caused DB migration to fail given large WorkerPool table rows has been fixed with a patch to DB version
▶ [patch] bug 1636292 The bug in 29.4.0 which caused DB migration to fail given large WorkerPool table rows has been fixed with a patch to DB version 10.
▶ [patch] bug 1635985 Docker Worker code now lives in this repository instead of taskcluster/docker-worker
▶ [patch] bug 1631829 Fixes an issue where azure-provider wasn't properly tagging resources.
▶ [patch] bug 1631829 Fixes an issue where azure-provider wasn't properly tagging resources.
▶ [minor] bug 1630023 The worker manager's worker pools are now stored in a normal database table. This table is small, and the DB migration should complete in seconds.
▶ [patch] Fix missing db TypeError in purge-cache.
▶ [patch] bug 1633897 Remove outdated check for taskcluster.net when sending cookies. This was used back when the UI was hosted in heroku.
▶ Additional change not described here: bug 1633882.
▶ [minor] bug 1630019 The purge_cache service now uses normalized db tables
▶ [minor] bug 1630019 The purge_cache service now uses normalized db tables
▶ [patch] bug 1633582 The worker-manager Google provider now labels worker disks with the same set of labels as VMs.
▶ [patch] #1536 taskcluster-client-web no longer shows the 'hawk is undefined' regression error.
▶ [patch] bug 1630023 DB version 8 introduces some utility functions that will be useful in migrating from (and downgrading to) tc-lib-entities-compatible tables.
▶ [patch] The morgan-debug logging for web services has been removed in favor of continued support of our api logging and iprepd logging in production
▶ Additional change not described here: bug 1633882.
▶ [patch] bug 1606006 Services that use ephemeral queues now use a different queue name on each connection. This avoids issues with RESOURCE-LOCKED fr
▶ [patch] bug 1606006 Services that use ephemeral queues now use a different queue name on each connection. This avoids issues with RESOURCE-LOCKED from RabbitMQ.
▶ [minor] bug 1629807 Taskcluster login now includes a state token in the url search query during the login transaction to conform with the recommendations in rfc-261.
▶ [patch] bug 1631099 Taskcluster-GitHub now retries on 401 "Bad Credentials" errors from GitHub, as suggested by GitHub developers.
▶ [patch] bug 1633622
The taskcluster-client-web package now contains the build directory as expected.
▶ [patch] A dependency that was mistakenly thought to be unused has been added back
▶ [patch] A dependency that was mistakenly thought to be unused has been added back
▶ [patch] bug 1627116 The worker manager AWS provider now tags EBS volumes created for EC2 instances with the same set of tags.
▶ [patch] bug 1631829 The worker-manager Azure provider now tags all worker related Azure resources with the set of standard tags.
▶ [patch] bug 1632325 release:publish tasks now save debug logs as artifacts
▶ [patch] bug 1632325 release:publish tasks now save debug logs as artifacts
▶ [patch] The db:upgrade and db:downgrade commands now correctly roll back on error.
▶ [patch]
The db:upgrade and db:downgrade commands now correctly roll back on error.
▶ [patch] #2634
taskcluster-lib-entities .modify no longer reaches out to the db when the data
is not modified.
▶ [MAJOR] bug 1436478 The Taskcluster services now use a Postgres backend, instead of Azure Cables and Azure Containers. All data in Azure must be mig
▶ [MAJOR] bug 1436478
The Taskcluster services now use a Postgres backend, instead of Azure Cables and Azure Containers. All data in Azure must be migrated to Postgres during a downtime using yarn importer:run, and this is planned for all known deployments. There should be no immediate user-visible impact from this change, aside from faster API responses, but it unlocks many planned improvements.
▶ [patch] #2615 Fix error showing when creating new client/role in the UI.
▶ [patch] #2615 Fix error showing when creating new client/role in the UI.
▶ [patch] bug 1525419
Generic worker tasks on Windows can now define environment variables that contain special characters ()%!^"<>&|. Previously they were not escaped.
▶ [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.
▶ [patch] bug 1624602 Worker-runner is now more careful to read all output from the worker when the worker exits.
▶ [patch] bug 1624602 Worker-runner is now more careful to read all output from the worker when the worker exits.
▶ [patch] bug 1552323 Fixes the bug: https://sentry.prod.mozaws.net/operations/taskcluster-community/issues/7766271
▶ [patch] Fix error in notify service (monitor is required)
▶ [patch] Fix error in notify service (monitor is required)
▶ [patch] bug 1618333 Changelog entries now are categorized by the audience that they are useful for
▶ [patch] bug 1618333 Changelog entries now are categorized by the audience that they are useful for
▶ [patch] Now, if the worker process running in aws/gcp exits, it will be requested to worker-manager to terminate the instance.
▶ [patch] bug 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.
▶ [minor] bug 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 Taskcluster UI nows offers a breadcrumbs view to easily jump back and forth when viewing indexes (/tasks/index/)
▶ [minor] bug 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 Services that use a database now log information about that database, including connection pool counts and stored-function invocations.
▶ [patch] #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 The taskcluster-lib-azqueue library now returns "batches" of messages in the order they were inserted.
As no data was stored with timestamps until now, this is not a breaking change.
▶ [minor] bug 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 Taskcluster UI now allow users to view the diff for scope changes (similar to the github write/preview functionality).
▶ [patch] #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 Generic-worker now transmits its logs via taskcluster-worker-runner, in preparation for supporting arbitrary log destinations.
▶ [patch] bug 1621420 Prepare to update octokit dependency
▶ [patch] #2503 Some schemas in the Taskcluster documentation were not displayed with a "Cannot find .." error. This has been fixed.
▶ [patch] #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 The Go client now correctly returns an error when 500 responses are retried to exhaustion.
▶ [patch] #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, 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 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 The protocol between workers and worker manager now correctly negotiates capabilities.
▶ Additional changes not described here: bug 1623183, #2527, #2539.
▶ [MAJOR] #2328 This version adds a temporary "widgets" API method to the notify service. This is intended to allow testing of the deployment process
▶ [MAJOR] #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.
▶ [minor] Add worker-runner binaries to the list of release artifacts
▶ [minor] bug 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 The Taskcluster-GitHub service now uses structured logging to describe its handling of events from GitHub. See its logging documentation for details.
▶ Additional change not described here: bug 1621270.
▶ [minor] bug 1621630 JSON-e has been reverted to v3.0.1, meaning that short-circuit evaluation of boolean operators is again unsupported. This suppor
▶ [minor] bug 1621630 JSON-e has been reverted to v3.0.1, meaning that short-circuit evaluation of boolean operators is again unsupported. This support will return soon.
▶ [minor] bug 1621630 JSON-e has been reverted to v3.0.2, meaning that short-circuit evaluation of boolean operators is again unsupported. This suppor
▶ [minor] bug 1621630 JSON-e has been reverted to v3.0.2, meaning that short-circuit evaluation of boolean operators is again unsupported. This support will return soon.
▶ [MAJOR] bug 1620109 The long-deprecated queue.defineTask API method has been removed.
▶ [MAJOR] bug 1620109
The long-deprecated queue.defineTask API method has been removed.
▶ [minor] bug 1573192
A task's metadata.owner is no longer required to have the form of an email address, as discussed in RFC#153.
▶ [patch] Fixed worker-manager's azure-provider to properly report worker pool errors when provisioning workers fails.
▶ [patch] bug 1547731 The web-server service now includes structured logging for web-server requests.
▶ [patch] Changes version imports for internal go libraries that weren't properly updated by the release script to v26.
▶ [patch] Changes version imports for internal go libraries that weren't properly updated by the release script to v26.
▶ [minor] bug 1608185 Taskcluster-worker-runner now passes --with-worker-runner to generic-worker when running it directly. When running generic-worke
▶ [minor] bug 1608185
Taskcluster-worker-runner now passes --with-worker-runner to generic-worker when running it directly. When running generic-worker as a Windows service, this argument should be included in the service definition.
Only generic-worker versions 25.0.0 and higher support this argument. In general, we recommend running matching versions of taskcluster-worker-runner and generic-worker.
▶ [minor] bug 1522154 Matrix notifications are now supported if a deployment is configured with credentials for a homeserver. The three fields needed are:
notify.matrix_base_url: foo # The homeserver where your client is registered
notify.matrix_user_id: bar # The user that will act on behalf of taskcluster
notify.matrix_access_token: baz # An access token for this user
If you are using riot, you can get the access token by following this guide.
▶ [patch] bug 1600071 Avoid overprovisioning for instances that take a long time to boot.
▶ [patch] #2404 Fix worker type page when the latest task has no runs. Previously, an error panel was being displayed with text "t.run is null".
▶ [patch] bug 1616922 Generic-Worker documentation is now included in the Taskcluster documentation site, and the generic-worker task payload has been slightly tightened.
task.payload.artifacts must contain unique itemstask.payload.onExitStatus.retry must contain unique items▶ [patch] bug 1558240
Generic-worker now outputs a newline before === Task Finished ===, to ensure that line is separated from other output in the logs.
▶ [patch] bug 1433854 Task directories from previous task runs on Windows are now more aggressively purged.
This should reduce the amount of time spent trying to delete task directories between task runs, and also the amount of logging, in addition to freeing up more disk space.
This issue always existed on the Windows version of generic-worker. A similar issue existed on macOS and Linux but was fixed in bug 1615312 which was initially tagged for release in v25.0.0, but first appeared in release 25.3.0 due to some problems with the release process.
▶ [patch] #2004 The Task Details panel in the Task view now wraps the payload text in order to be able to see the complete payload without scrolling.
▶ [patch] bug 1618066 fix bug where workerInfo could have NaN values
▶ [patch] bug 1616649 reimplements azure-provider's use of the azure SDK to avoid blocking operations that can hold up worker-manager iterations resource creation operations that were previously waiting for completion in the provisioner now are tracked and checked on as part of the worker-scanner iteration
▶ Additional change not described here: bug 1616900.
▶ [patch] This version removes the undocumented, deprecated WebListener class from taskcluster-client-web.
▶ [minor] bug 1616214 Source code repositories taskcluster-worker-runner and jsonschema2go have been migrated to the taskcluster monorepo. This is an internal change that should not impact the release. However, it is a reasonably significant change to the build/release process.
▶ [patch] #2377 Editing a task that contains ISO-8601 dates embedded in larger strings no longer fails with "Invalid Date".
▶ [patch] bug 1616022 Fixes the version number reported by generic-worker. This was first attempted (unsuccessfully) in release 25.2.0.
▶ [patch] bug 1606874 The Taskcluster-GitHub service now checks that the person who filed a pull request is a collaborator and the repo from which the changes are being pulled belongs to a collaborator or is the usptream repository.
▶ [patch] This version removes the undocumented, deprecated WebListener class from taskcluster-client-web.
▶ Additional changes not described here: bug 1437193, #2371, #2375.
▶ [minor] bug 1616022 Generic worker now correctly reports its version number. The version number was incorrectly reported in release 25.1.1.
▶ [minor] bug 1616022 Generic worker now correctly reports its version number. The version number was incorrectly reported in release 25.1.1.
▶ Additional changes not described here: bug 1615762, #2367.
No changes
No changes
▶ [patch] bug 1611266 azure-provider now ensures generated adminPasswords meet all passwords requirements
▶ [patch] bug 1611266 azure-provider now ensures generated adminPasswords meet all passwords requirements
▶ [minor] #2293 The Taskcluster Python client now has an helper function to easily upload artifacts.
▶ [minor] #2293 The Taskcluster Python client now has an helper function to easily upload artifacts.
▶ [minor] bug 1604175 The maximum "deadline" has been reverted to 5 days, after its change to 10 days in v24.1.3. Values over 7 days caused internal server errors anyway, because the Azure queue backend cannot handle delays greater than that value. Since this functionality never worked, the revert is considered minor.
▶ [patch] bug 1606874 Changes behavior of tc-github when checking the user permissions on PR: now tc-github always checks the permissions of the PR author (or the organization of the PR origin if the PR was made from a fork in an org)
▶ [patch] bug 1611266 Limit azure-provider name generation to alphanumeric to reduce invalid name errors (previously characters such as _ and - were included in some names and could be the ending character, resulting in errors)
▶ [patch] bug 1613150 Taskcluster services now run with Node version 12.15.0.
▶ [patch] bug 1584208 The client libraries' documentation has been throughly refactored and is now more helpful and contains better links to the documentation site.
▶ [patch] The deployment documentation now contains information on how Pulse users should be set up, as well as a complete schema for the Helm values file.
▶ [patch] bug 1604649 The queue now avoids calling GetEntity for a worker in claimWork when no work was claimed, providing a very minor reduction in Azure load.
▶ [patch] bug 1436478
This version includes the taskcluster-lib-postgres library, but does not use that library at runtime.
▶ Additional changes not described here: bug 1537922, bug 1588083, bug 1611694, bug 1611696, #1963, #2130.
▶ [minor] bug 1600966 Adds a provider for azure vm instances to worker-manager.
▶ [minor] bug 1600966 Adds a provider for azure vm instances to worker-manager.
▶ [patch]
The Python client now normalizes the root URL in optionsFromEnvironment().
▶ [patch] #2269 Links to specific log lines now autoscroll to correct location.
▶ [patch] #2031 Taskcluster UI revamped the date picker component to allow selecting the hour and the minute in addition to the date.
▶ [patch] #2031 Taskcluster UI revamped the date picker component to allow selecting the hour and the minute in addition to the date.
▶ [patch] bug 1608176
The go client's client.SignedURL(..) function can now accept and sign full URLs in its first argument. This allows signing arbitrary URLs, even if they are not on the same RootURL as the client.
▶ Additional changes not described here: bug 1606948, #2201.
▶ [patch] bug 1598649 Final bits of release debugging (sorry!)
▶ [patch] bug 1598649 Final bits of release debugging (sorry!)
▶ [patch] #2159 Taskcluster UI /auth/scopes view has been revamped to improve the experience and avoid confusions with the Clients and Roles views.
▶ [patch] #2159 Taskcluster UI /auth/scopes view has been revamped to improve the experience and avoid confusions with the Clients and Roles views.
▶ [patch] #2166 Taskcluster UI Worker view now gracefully allows a user to quarantine a worker when a recent task has expired.
▶ [patch] bug 1537922
The auth.createClient API method is now properly idempotent, allowing the same call multiple times in short succession.
▶ [patch] bug 1603197 The notify service's irc process now logs a bit more contextual information about what it is up to, and ignores some common replies from IRC servers instead of considering them "unhandled".
One column per quarter.