build(deps): Bump taskcluster from 26.0.1 to 28.0.0 in /tools

[dependabot-preview]

Bumps taskcluster from 26.0.1 to 28.0.0.

Release notes

Sourced from taskcluster's releases.

v28.0.0

▶ [MAJOR] #2328 This version adds a temporary "widgets" API method to the notify service. This is intended to allow testing of the deployment process for Taskcluster services' backend database, and not for tracking of actual widgets.

This new API requires that Helm properties notify.read_db_url and notify.write_db_url be set correctly as documented in the deployment documentation.

▶ [minor] Add worker-runner binaries to the list of release artifacts

▶ [minor] bug 1621630 Support for short-circuiting of boolean logic in JSON-e templates such as .taskcluster.yml is restored.

▶ [patch] AWS, GCP and Azure providers support the "shutdown" message, which requests the worker-manager to terminate the instance

▶ [patch] bug 1621167 The Taskcluster-GitHub service now uses structured logging to describe its handling of events from GitHub. See its logging documentation for details.

▶ Additional change not described here: bug 1621270.

v27.2.0

▶ [minor] bug 1621630 JSON-e has been reverted to v3.0.1, meaning that short-circuit evaluation of boolean operators is again unsupported. This support will return soon.

v27.1.0

▶ [minor] bug 1621630 JSON-e has been reverted to v3.0.2, meaning that short-circuit evaluation of boolean operators is again unsupported. This support will return soon.

v27.0.0

▶ [MAJOR] bug 1620109 The long-deprecated queue.defineTask API method has been removed.

▶ [minor] bug 1573192 A task's metadata.owner is no longer required to have the form of an email address, as discussed in RFC#153.

▶ [patch] Fixed worker-manager's azure-provider to properly report worker pool errors when provisioning workers fails.

▶ [patch] bug 1547731 The web-server service now includes structured logging for web-server requests.

Changelog

Sourced from taskcluster's changelog.

v28.0.0

▶ [MAJOR] #2328 This version adds a temporary "widgets" API method to the notify service. This is intended to allow testing of the deployment process for Taskcluster services' backend database, and not for tracking of actual widgets.

This new API requires that Helm properties notify.read_db_url and notify.write_db_url be set correctly as documented in the deployment documentation.

▶ [minor] Add worker-runner binaries to the list of release artifacts

▶ [minor] bug 1621630 Support for short-circuiting of boolean logic in JSON-e templates such as .taskcluster.yml is restored.

▶ [patch] AWS, GCP and Azure providers support the "shutdown" message, which requests the worker-manager to terminate the instance

▶ [patch] bug 1621167 The Taskcluster-GitHub service now uses structured logging to describe its handling of events from GitHub. See its logging documentation for details.

▶ Additional change not described here: bug 1621270.

v27.2.0

▶ [minor] bug 1621630 JSON-e has been reverted to v3.0.1, meaning that short-circuit evaluation of boolean operators is again unsupported. This support will return soon.

v27.1.0

▶ [minor] bug 1621630 JSON-e has been reverted to v3.0.2, meaning that short-circuit evaluation of boolean operators is again unsupported. This support will return soon.

v27.0.0

▶ [MAJOR] bug 1620109 The long-deprecated queue.defineTask API method has been removed.

▶ [minor] bug 1573192 A task's metadata.owner is no longer required to have the form of an email address, as discussed in RFC#153.

▶ [patch] Fixed worker-manager's azure-provider to properly report worker pool errors when provisioning workers fails.

▶ [patch] bug 1547731 The web-server service now includes structured logging for web-server requests.

Commits

• 4181d04 v28.0.0
• ce1dbd2 Merge pull request #2499 from djmitche/gw-protocol-fix
• 57204cb Include the graceful-termination capability in w-r protocol
• cd98ec0 fix changelog spelling
• 4f95dce yarn generate
• 279cd51 Document security invariants
• a004b15 Fix dev:db:upgrade and add dev:db:downgrade
• 70590be Support initializing configuration for a postgres DB
• 62369f1 Add support for DB downgrades
• 31005a6 Merge pull request #2330 from djmitche/issue2328
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)