Taskcluster

GENERAL

▶ [patch]
Upgrade Node.js version to 18.16.0 and go version to 1.19.9.

USERS

▶ [minor] [6169](https://github.com/taskcluster/taskcluster/issues/6169)
Adds interactive shell support to generic-worker.

The worker configuration variable `enableInteractive` needs to be set to `true` to allow the interactive shell feature to be enabled. `enableInteractive` is disabled by default.

Once the worker configuration variable is set, the `interactive` feature can be enabled on a per-task basis.

To enable, set `task.payload.features.interactive` to `true`. And toggle on `Interactive` in the Create Task view of the UI.

WORKER-DEPLOYERS

▶ [patch] [6186](https://github.com/taskcluster/taskcluster/issues/6186)
Worker-manager refreshes worker from database before calling removeWorker on terminateAfter time exceeded to prevent from stopping workers that were already registered and running since worker scanner has started.

USERS

▶ [patch] [6185](https://github.com/taskcluster/taskcluster/issues/6185)
Fixed quarantine worker 'reason' field schema to be optional.

▶ [patch] [6058](https://github.com/taskcluster/taskcluster/issues/6058)
Generic Worker no longer modifies the Access Control Lists of the Interactive Desktop and the associated Windows Station unless additional OS groups have been specified in the task payload `osGroups` property. Previously Generic Worker would modify the ACLs of these objects even if the access token it was using for launching task command processes already had suitable permissions. This patch is a workaround for a more general issue, which is that the ACL modifications seem not to be appropriate in all cases when a new access token is needed. See https://bugzilla.mozilla.org/show_bug.cgi?id=1815711.

There is a likely to be a follow up fix for the ACL modifications that occur when a new access token is required, once it is understood why the current modifications are not always sufficient.

GENERAL

▶ [patch]
Generic worker feature `task.Payload.OnExitStatus.PurgeCaches` now only purges caches related to the task, instead of all caches on the worker.

USERS

▶ [patch] [5773](https://github.com/taskcluster/taskcluster/issues/5773)
Fix UI bug when user profile was missing and causing whole page to crash.

▶ [patch] [bug 1590886](http://bugzil.la/1590886)
Github status handler listens to both `taskPending` and `taskRunning` events.

ADMINS

▶ [minor] [bug 1826417](http://bugzil.la/1826417)
Changes the way `expire-artifacts` works. It uses a separate function to fetch all expired artifacts and then uses bulk delete to remove them from S3 and the database.

GENERAL

▶ [patch]
Builds and tests generic worker (multiuser) on macOS Ventura 13 on new, arm64 machines.

USERS

▶ [MAJOR]
Remove python 3.6 support as it's past its end-of-life date.

Add python 3.10 and python 3.11 support.

▶ [minor] [6147](https://github.com/taskcluster/taskcluster/issues/6147)
Adds `task.payload.onExitStatus.purgeCaches` feature to generic worker to bring to parity with an existing docker worker feature.

`purgeCaches` is an array of exit status code integers that the user wants all caches associated with the task to be purged.