Bump taskcluster from 107.0.0 to 110.1.0

[dependabot]

Bumps taskcluster from 107.0.0 to 110.1.0.

Release notes

Sourced from taskcluster's releases.

v110.1.0

DEPLOYERS

▶ [minor] bug 1599247 The auth service's gcpCredentials endpoint now supports any number of GCP projects configured in gcp_credentials_allowed_projects, rather than being limited to a single project. Each configured project keeps its own credentials and allowedServiceAccounts allow-list, and requests are scoped to the project named in the request path.

WORKER-DEPLOYERS

▶ [patch] bug 2071937 Generic Worker on Windows no longer interpolates payload.osGroups into a PowerShell -Command string when adding or removing the task user from OS groups. Membership is updated with NetLocalGroupAddMembers / NetLocalGroupDelMembers, so group names cannot break out of a PowerShell single-quoted literal (including via Unicode quotation marks U+2018–U+201B).

▶ [patch] On Windows, the worker now replaces the whole security descriptor of the files it secures instead of just dropping ACL inheritance on it. The ownership is now also changed to BUILTIN\Administrators

USERS

▶ [minor] index.findTasksAtIndex no longer returns expired indices

▶ [patch] #9127 Dashboard shows pending and claimed task counts for task queues that worker-manager does not own (hardware workers, for example). These queues were previously missing from the dashboard's task totals entirely. Discovering them requires the queue:list-task-queues scope, plus queue:pending-count:<taskQueueId> and queue:claimed-count:<taskQueueId> for each queue.

▶ [patch] #9172 In the python client, importing taskcluster.helper before anything from taskcluster.aio no longer leaves taskcluster.aio without any of its clients

▶ [patch] Indexing a task no longer silently does nothing when an expired entry with a higher rank still exists at the same index path

▶ [patch] #9065 The worker pools list now shows a "Claimed Tasks" column alongside "Pending Tasks". The claimed counts already came back from the batched taskQueueCounts request the page makes, so this adds no extra API calls.

▶ [patch] #9065 UI: Dashboard and Worker Manager load pending/claimed counts in batched requests. Stopping capacity is no longer shown. Public deployments must grant both queue:pending-count:* and queue:claimed-count:* to the anonymous role for these counts to appear.

▶ [patch] UI: hardened task artifact log links with proper encoding.

▶ [patch] bug 2072160 Worker-manager improves error handling when duplicate static worker is created.

DEVELOPERS

▶ [patch] yarn db:new and yarn db:renumber don't require you to provide either ADMIN_DB_URL or USERNAME_PREFIX anymore

OTHER

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v110.1.0

DEPLOYERS

▶ [minor] bug 1599247 The auth service's gcpCredentials endpoint now supports any number of GCP projects configured in gcp_credentials_allowed_projects, rather than being limited to a single project. Each configured project keeps its own credentials and allowedServiceAccounts allow-list, and requests are scoped to the project named in the request path.

WORKER-DEPLOYERS

▶ [patch] bug 2071937 Generic Worker on Windows no longer interpolates payload.osGroups into a PowerShell -Command string when adding or removing the task user from OS groups. Membership is updated with NetLocalGroupAddMembers / NetLocalGroupDelMembers, so group names cannot break out of a PowerShell single-quoted literal (including via Unicode quotation marks U+2018–U+201B).

▶ [patch] On Windows, the worker now replaces the whole security descriptor of the files it secures instead of just dropping ACL inheritance on it. The ownership is now also changed to BUILTIN\Administrators

USERS

▶ [minor] index.findTasksAtIndex no longer returns expired indices

▶ [patch] #9127 Dashboard shows pending and claimed task counts for task queues that worker-manager does not own (hardware workers, for example). These queues were previously missing from the dashboard's task totals entirely. Discovering them requires the queue:list-task-queues scope, plus queue:pending-count:<taskQueueId> and queue:claimed-count:<taskQueueId> for each queue.

▶ [patch] #9172 In the python client, importing taskcluster.helper before anything from taskcluster.aio no longer leaves taskcluster.aio without any of its clients

▶ [patch] Indexing a task no longer silently does nothing when an expired entry with a higher rank still exists at the same index path

▶ [patch] #9065 The worker pools list now shows a "Claimed Tasks" column alongside "Pending Tasks". The claimed counts already came back from the batched taskQueueCounts request the page makes, so this adds no extra API calls.

▶ [patch] #9065 UI: Dashboard and Worker Manager load pending/claimed counts in batched requests. Stopping capacity is no longer shown. Public deployments must grant both queue:pending-count:* and queue:claimed-count:* to the anonymous role for these counts to appear.

▶ [patch] UI: hardened task artifact log links with proper encoding.

▶ [patch] bug 2072160 Worker-manager improves error handling when duplicate static worker is created.

DEVELOPERS

▶ [patch] yarn db:new and yarn db:renumber don't require you to provide either ADMIN_DB_URL or USERNAME_PREFIX anymore

OTHER

... (truncated)

Commits

• 8522ee4 v110.1.0
• 6941073 Merge pull request #9120 from addielaruee/fix/9119-github-app-link
• c65502c Merge pull request #9177 from Eijebong/in-circles
• 5501b20 Fix circular import breaking the aio python client
• fdef0d4 feat(ui): encode log artifact name in the URL (#8997)
• 0ec843b Merge pull request #9168 from Eijebong/fix-yarn-db-new
• 56b091e Merge pull request #9175 from Eijebong/fix-index-insert
• 21a3269 Indexing a task now ignores expired entries with a higher rank on insertion
• 0d2b01e Merge pull request #9174 from Eijebong/dont-return-expired-stuff
• f9b3874 feat(w-m): Fix unique violation detection in static worker create (#9171)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)