Taskcluster

▶ [minor] [bug 1621630](http://bugzil.la/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](http://bugzil.la/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](http://bugzil.la/1620109)
The long-deprecated `queue.defineTask` API method has been removed.

▶ [minor] [bug 1573192](http://bugzil.la/1573192)
A task's `metadata.owner` is no longer required to have the form of an email address, as discussed in [RFC153](https://github.com/taskcluster/taskcluster-rfcs/blob/master/rfcs/0153-remove-email-validation-for-metadata-owner.md).

▶ [patch]
Fixed worker-manager's azure-provider to properly report worker pool errors when provisioning workers fails.

▶ [patch] [bug 1547731](http://bugzil.la/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.

▶ [MAJOR] [bug 1596177](http://bugzil.la/1596177)
Legacy create-task scopes without a priority, of the form `queue:create-task:<provisionerId>/<workerType>`, are no longer supported.

▶ [minor]
Add support for a simple generic FreeBSD worker

▶ [minor] [bug 1473155](http://bugzil.la/1473155)
Schemas are now displayed in a two-column viewer to provide a more comprehensive understanding of the schema structures. The left panel shows the overall data structure while the right panel shows additional properties to keep in mind for certain data within the schemas. Users can also expand or shrink $ref schemas when needed.

▶ [minor] [bug 1618916](http://bugzil.la/1618916)
The Azure worker-manager provider now provides bootstrapping information to the worker in tags in addition to the `customData` instance metadata field, and worker-runner now expects to find data in tags. This avoids the use of the barely-functional customData. Reading this information from customData is now deprecated, but will continue to work at least until the next major Taskcluster release.

▶ [minor]
The json-e library now supports short-circuiting in boolean logic, and so does Taskcluster for taskcluster.ymls now!

▶ [patch] [bug 1619925](http://bugzil.la/1619925)
Bug fix: taskcluster-proxy credential updates from task reclaims no longer race with taskcluster proxy process termination. Previously if a task completed just as the task was being reclaimed, it was possible for generic-worker to terminate the taskcluster-proxy process while it was HTTP posting updated credentials to it, which caused generic-worker to crash.

▶ [patch] [bug 1559434](http://bugzil.la/1559434)
Pulse passwords are now correctly encoded and can contain `/` characters.

▶ [patch] [2386](https://github.com/taskcluster/taskcluster/issues/2386)
Taskcluster UI now no longer shows a cached view when a user deletes a role,
client or hook.

▶ [patch] [bug 1558240](http://bugzil.la/1558240)
The generic-worker logging change that appeared in v25.4.0 has been reverted.

▶ [patch] [bug 1617685](http://bugzil.la/1617685)
The queue service will now start up even if the AWS IP-to-region mapping file is not accessible. In this case, it will use a local, cached copy of this information.

▶ [patch] [bug 1618983](http://bugzil.la/1618983)
The worker-manager's `static` provider type now supports worker lifecycles, and in particular `reregistrationTimeout`.

▶ [patch]
Update `registerWorker` API to grant scopes for workers to terminate themselves

▶ [patch] [bug 1591476](http://bugzil.la/1591476)
worker-manager's `registerWorker()` now returns worker config, and worker-runner (for Azure and static providers, others coming soon) merges that configuration with other configuration sources. This allows worker pools to include configuration for static workers, and allows Azure workers to fetch their config without referencing the non-functional customData instance metadata.

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

▶ [minor] [bug 1608185](http://bugzil.la/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](http://bugzil.la/1522154)
[Matrix](https://matrix.org/) notifications are now supported if a deployment is configured
with credentials for a homeserver. The three fields needed are:

yaml
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](https://t2bot.io/docs/access_tokens/).

▶ [patch] [bug 1600071](http://bugzil.la/1600071)
Avoid overprovisioning for instances that take a long time to boot.

▶ [patch] [2404](https://github.com/taskcluster/taskcluster/issues/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](http://bugzil.la/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 items
* `task.payload.onExitStatus.retry` must contain unique items

▶ [patch] [bug 1558240](http://bugzil.la/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](http://bugzil.la/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](https://github.com/taskcluster/taskcluster/issues/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](http://bugzil.la/1618066)
fix bug where workerInfo could have NaN values

▶ [patch] [bug 1616649](http://bugzil.la/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](http://bugzil.la/1616900).