build(deps): bump taskcluster from 40.0.3 to 41.0.0 in /tools

[dependabot]

Bumps taskcluster from 40.0.3 to 41.0.0.

Release notes

Sourced from taskcluster's releases.

v41.0.0

GENERAL

▶ [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.

DEPLOYERS

▶ [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.

WORKER-DEPLOYERS

▶ [patch] #4336 Worker-Runner now correctly includes the workerGroup and workerId properties in error reports.

ADMINS

▶ [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.

USERS

▶ [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.

NOTE: client compatibility is only guaranteed in a forward direction -- an older client can talk to a newer service, and that remains the case with this release. However, this change will cause issues if a newer (41.x or higher) client is used to make any of the above API calls to an older (40.x or lower) service,

▶ [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

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v41.0.0

GENERAL

▶ [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.

DEPLOYERS

▶ [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.

WORKER-DEPLOYERS

▶ [patch] #4336 Worker-Runner now correctly includes the workerGroup and workerId properties in error reports.

ADMINS

▶ [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.

USERS

▶ [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.

... (truncated)

Commits

• 881d1e4 v41.0.0
• 487313b Merge pull request #4381 from djmitche/purge-cache-ui
• ac2d1bf Merge pull request #4385 from taskcluster/renovate/query-string-6.x-lockfile
• d70ebc5 Update dependency query-string to v6.14.0
• de16caf Merge pull request #4384 from taskcluster/renovate/spf13-cobra-1.x
• 7c1a3ba Update module spf13/cobra to v1.1.2
• fa538f3 Update dependency apollo-server-express to v2.20.0
• a3e5951 Update dependency @azure/ms-rest-js to v2.2.2
• ec17de5 Fix call to purgeCache.purgeCache in web-server to use workerPoolId
• 6c00130 Update dependency aws-sdk to v2.840.0 (#4379)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

Superseded by #792.