build(deps): bump taskcluster from 42.1.1 to 43.0.0 in /tools

[dependabot]

Bumps taskcluster from 42.1.1 to 43.0.0.

Release notes

Sourced from taskcluster's releases.

v43.0.0

DEPLOYERS

▶ [patch] #4655 Since #4586 landed, the built-in-workers service has failed to resolve tasks due to using the wrong credentials. This issue has been fixed, and no released version of Taskcluster had this bug.

▶ [patch] #4561 The GitHub service now allows collaborators to test out a .taskcluster.yml in a PR, when there is no such file in the default branch initialized yet.

▶ [patch] #4556 The auth.azure_accounts Helm value is no longer required.

▶ [patch] #3981 The new queue.task_claim_timeout Helm configuration parameter controls the duration of the task claim that queue.claimWork returns. The default is 20 minutes, matching the previous hard-coded setting.

WORKER-DEPLOYERS

▶ [MAJOR] #3779 Generic-worker simple/docker engine now have a default tasks directory of tasks, relative to the working directory. This is a breaking change from previous behaviour.

▶ [patch] #4691 Added a generic-worker config parameter (livelogPortBase) to allow configuring which ports are used for live logging.

▶ [patch] #4715 The worker-manager service now deprovisions workers when removeWorker is called and when the workers terminate themselves. Previously it would wait forever for such workers to be deleted, without attempting that deletion.

USERS

▶ [MAJOR] #4586 The following queue API endpoints no longer support their legacy scopes. In most of these cases, the legacy scopes are shorter than the still-supported fully-qualified scopes.

• queue.claimTask no longer accepts queue:claim-task.
• queue.reclaimTask no longer accepts queue:reclaim-task.
• queue.reportCompleted and queue.reportException no longer accept queue:resolve-task.
• queue.createArtifact no longer accepts queue:create-artifact:<name>.

Investigations detailed in the linked issue suggest that none of these scopes are actively used.

▶ [minor] #4516 The index service has a new index.deleteTask method that can be used to delete indexed tasks.

▶ [minor] #4547 This version adds new queue methods artifact, latestArtifact, artifactInfo, and latestArtifactInfo, all of which provide more flexible access to information about artifacts.

▶ [patch] #4502 The GitHub service now correctly handles tasks that depend on other tasks not defined in .taskcluster.yml.

▶ [patch] #3794 The worker manager no longer considers quarantined users in its definition of existing capacity. If necessary, it will provision new workers for any pending tasks as if the quarantined worker did not exist.

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v43.0.0

DEPLOYERS

▶ [patch] #4655 Since #4586 landed, the built-in-workers service has failed to resolve tasks due to using the wrong credentials. This issue has been fixed, and no released version of Taskcluster had this bug.

▶ [patch] #4561 The GitHub service now allows collaborators to test out a .taskcluster.yml in a PR, when there is no such file in the default branch initialized yet.

▶ [patch] #4556 The auth.azure_accounts Helm value is no longer required.

▶ [patch] #3981 The new queue.task_claim_timeout Helm configuration parameter controls the duration of the task claim that queue.claimWork returns. The default is 20 minutes, matching the previous hard-coded setting.

WORKER-DEPLOYERS

▶ [MAJOR] #3779 Generic-worker simple/docker engine now have a default tasks directory of tasks, relative to the working directory. This is a breaking change from previous behaviour.

▶ [patch] #4691 Added a generic-worker config parameter (livelogPortBase) to allow configuring which ports are used for live logging.

▶ [patch] #4715 The worker-manager service now deprovisions workers when removeWorker is called and when the workers terminate themselves. Previously it would wait forever for such workers to be deleted, without attempting that deletion.

USERS

▶ [MAJOR] #4586 The following queue API endpoints no longer support their legacy scopes. In most of these cases, the legacy scopes are shorter than the still-supported fully-qualified scopes.

• queue.claimTask no longer accepts queue:claim-task.
• queue.reclaimTask no longer accepts queue:reclaim-task.
• queue.reportCompleted and queue.reportException no longer accept queue:resolve-task.
• queue.createArtifact no longer accepts queue:create-artifact:<name>.

Investigations detailed in the linked issue suggest that none of these scopes are actively used.

▶ [minor] #4516 The index service has a new index.deleteTask method that can be used to delete indexed tasks.

▶ [minor] #4547 This version adds new queue methods artifact, latestArtifact, artifactInfo, and latestArtifactInfo, all of which provide more flexible access to information about artifacts.

▶ [patch] #4502 The GitHub service now correctly handles tasks that depend on other tasks not defined in .taskcluster.yml.

▶ [patch] #3794 The worker manager no longer considers quarantined users in its definition of existing capacity. If necessary, it will provision new workers for any pending tasks as if the quarantined worker did not exist.

... (truncated)

Commits

• fb202d2 v43.0.0
• 127c788 Merge pull request #4731 from taskcluster/renovate/date-fns-2.x-lockfile
• 147161c Update dependency date-fns to v2.20.0
• 66b55c4 Update dependency aws-sdk to v2.882.0
• c3c436e Merge pull request #4728 from rbrishabh/fix/fix-ref-links
• e74b62f Merge pull request #4727 from taskcluster/renovate/c8-7.x-lockfile
• 5960acb Adds changelog
• 1291842 Adds changelog and fixes lint issues
• 0a41b2d location => location.pathname
• 1114447 Update dependency c8 to v7.7.1
• 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 #900.