Skip to content

build(deps): bump taskcluster from 96.2.3 to 99.0.3 in /integration#3308

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/pip/integration/taskcluster-99.0.3
Open

build(deps): bump taskcluster from 96.2.3 to 99.0.3 in /integration#3308
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/pip/integration/taskcluster-99.0.3

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Apr 13, 2026

Bumps taskcluster from 96.2.3 to 99.0.3.

Release notes

Sourced from taskcluster's releases.

v99.0.3

WORKER-DEPLOYERS

▶ [patch] #8446 Worker Manager no longer removes Azure workers that are actively running tasks when an ARM deployment operation URL expires or the deployment shows a failed state. Previously, if Azure cleaned up a deployment record or the operation tracking URL expired before worker-manager marked provisioning as complete, the worker would be removed and any in-flight tasks resolved as exception/worker-shutdown, even though the worker was healthy.

DEVELOPERS

▶ [patch] Fixed scope resolver performance tests that were silently not running due to an async suite callback in mocha (which does not await suite callbacks). The tests using real-world role and client fixture data are now registered and executed correctly. Also removed a stale docker_posix.json entry from the unreferenced schemas list in lib-references.

Automated Package Updates

  • build(deps): bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4 (13d894b6aa)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 in /ui (57bbe0f3b1)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 in /ui/test/e2e (6a58323820)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 in /clients/client-web (c0454a4c74)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 in /clients/client (9f961dfb6b)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 (bd19c3bd6a)
  • build(deps): bump the client-python-deps group (86868da56a)
  • build(deps): bump the go-deps group with 5 updates (5ddd6ba940)
  • build(deps-dev): bump eslint (a523d2e67c)
  • build(deps): bump the client-rust-deps group (1f1353712c)
  • build(deps): bump dominikh/staticcheck-action (6540799a60)
  • build(deps): bump dependabot/fetch-metadata from 2.5.0 to 3.0.0 (dadd7754a3)

v99.0.2

Release v99.0.1 was sacrificed to the release Gods. Here were its changelogs:

v99.0.1

DEPLOYERS

▶ [patch] #6898 Azure workers that report a failed provisioning state (e.g., OSProvisioningClientError) but are actually running (PowerState/running) are no longer immediately terminated. Instead, they are allowed to attempt registration, with the existing terminateAfter timeout serving as a safety net for truly broken workers.

▶ [patch] Web Server: OAuth2 token scopes are now intersected with the registered client's allowed scopes in addition to the user's scopes, preventing a tampered consent form submission from requesting scopes beyond what the client was registered for. A warning is logged when a scope mismatch is detected.

WORKER-DEPLOYERS

▶ [patch] #8410

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v99.0.3

WORKER-DEPLOYERS

▶ [patch] #8446 Worker Manager no longer removes Azure workers that are actively running tasks when an ARM deployment operation URL expires or the deployment shows a failed state. Previously, if Azure cleaned up a deployment record or the operation tracking URL expired before worker-manager marked provisioning as complete, the worker would be removed and any in-flight tasks resolved as exception/worker-shutdown, even though the worker was healthy.

DEVELOPERS

▶ [patch] Fixed scope resolver performance tests that were silently not running due to an async suite callback in mocha (which does not await suite callbacks). The tests using real-world role and client fixture data are now registered and executed correctly. Also removed a stale docker_posix.json entry from the unreferenced schemas list in lib-references.

Automated Package Updates

  • build(deps): bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4 (13d894b6aa)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 in /ui (57bbe0f3b1)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 in /ui/test/e2e (6a58323820)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 in /clients/client-web (c0454a4c74)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 in /clients/client (9f961dfb6b)
  • build(deps): bump lodash from 4.17.23 to 4.18.1 (bd19c3bd6a)
  • build(deps): bump the client-python-deps group (86868da56a)
  • build(deps): bump the go-deps group with 5 updates (5ddd6ba940)
  • build(deps-dev): bump eslint (a523d2e67c)
  • build(deps): bump the client-rust-deps group (1f1353712c)
  • build(deps): bump dominikh/staticcheck-action (6540799a60)
  • build(deps): bump dependabot/fetch-metadata from 2.5.0 to 3.0.0 (dadd7754a3)

v99.0.2

OTHER

▶ Additional change not described here: #8013.

v99.0.1

DEPLOYERS

▶ [patch] #6898 Azure workers that report a failed provisioning state (e.g., OSProvisioningClientError) but are actually running (PowerState/running) are no longer immediately terminated. Instead, they are allowed to attempt registration, with the existing terminateAfter timeout serving as a safety net for truly broken workers.

... (truncated)

Commits
  • 5fe7c67 v99.0.3
  • add33c6 Merge pull request #8447 from taskcluster/matt-boris/wmLeaveRunningWorkersAlone
  • 856873e fix(worker-manager): don't remove RUNNING Azure workers on deployment expiry
  • e553637 Merge pull request #8445 from taskcluster/dependabot/go_modules/github.com/go...
  • 13d894b build(deps): bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4
  • 3b74e58 Merge pull request #8444 from taskcluster/dependabot/npm_and_yarn/ui/lodash-4...
  • b6f6175 Merge pull request #8443 from taskcluster/dependabot/npm_and_yarn/ui/test/e2e...
  • 57bbe0f build(deps): bump lodash from 4.17.23 to 4.18.1 in /ui
  • 6a58323 build(deps): bump lodash from 4.17.23 to 4.18.1 in /ui/test/e2e
  • 8277723 Merge pull request #8442 from taskcluster/dependabot/npm_and_yarn/clients/cli...
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [taskcluster](https://github.com/taskcluster/taskcluster) from 96.2.3 to 99.0.3.
- [Release notes](https://github.com/taskcluster/taskcluster/releases)
- [Changelog](https://github.com/taskcluster/taskcluster/blob/main/CHANGELOG.md)
- [Commits](taskcluster/taskcluster@v96.2.3...v99.0.3)

---
updated-dependencies:
- dependency-name: taskcluster
  dependency-version: 99.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integration Integration tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants