v16.6.1

Making release 16.6.1

v16.6.0

NOTE this version does not start up unless -worker-runner-protocol-pipe is supplied. This will be fixed in the next release

In v16.6.0 since v16.5.6

• Bug 1602512 - generic-worker: command abortion race condition
• Bug 1604201 - Support running generic-worker via worker-runner on windows

v16.5.6

In v16.5.6 since v16.5.5

• Bug 1595279 - No gecko-t-win64-aarch64-laptop workers are active and taking jobs, big backlog for Windows AArch laptops
• Bug 1596044 - generic-worker: secure files tasks-resolved-count.txt, file-caches.json, directory-caches.json

v16.5.5

In v16.5.5 since v16.5.4

• Bug 1594353 - generic-worker: "Not able to secure config file" on Windows

v16.5.4

In v16.5.4 since v16.5.3

This release is also unfortunately broken on Windows Server 2012 R2 (although runs on all other
supported platforms including Windows 7 and Windows 10). Fixed in 16.5.5.

• Bug 1593483 - generic-worker looks for deploymentId in the wrong place

v16.5.3

In v16.5.3 since v16.5.2

This release was intended to fix bug 1593483 but unfortunately did not. Bug 1593483 was later fixed in 16.5.4.

v16.5.2

In v16.5.2 since v16.5.1

This release fixes the bug that caused macOS multiuser generic-worker to be broken since v16.0.0.

• Bug 1592233 - calculate UID for new user under macOS multiuser

v16.5.1

In v16.5.1 since v16.5.0

• Bug 1591769 - generic-worker 16.5.0 does not start up

This multiuser macOS release is broken. If you require macOS multiuser, please use version 16.5.2 or higher.

v16.5.0

In v16.5.0 since v16.4.0

This release is buggy and does not start up. Please do not use this release!

• Bug 1590134 - Set TASKCLUSTER_WORKER_LOCATION environment variable in task command environments (RFC #0148)

v16.4.0

In v16.4.0 since v16.3.1

• Bug 1588834 - Add support for aws-provider to generic-worker.

This multiuser macOS release is broken. If you require macOS multiuser, please use version 16.5.2 or higher.