Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump taskcluster from 59.2.0 to 60.0.0 #1583

Merged
merged 1 commit into from
Jan 9, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 9, 2024

Bumps taskcluster from 59.2.0 to 60.0.0.

Release notes

Sourced from taskcluster's releases.

v60.0.0

GENERAL

▶ [patch] Generic Worker: No longer logs out the redirect URL for the interactive shell feature since they are signed.

DEPLOYERS

▶ [MAJOR] #6759 Kubernetes pods use liveness probe instead of unconditionally killing containers daily.

▶ [patch] #6641 Worker-manager no longer counts "stopping" instances as part of the existing capacity when estimating the number of workers to start (although they are still counted towards maxCapacity).

Automated Package Updates

  • build(deps-dev): bump markdown-table from 2.0.0 to 3.0.3 (979bdebbe)
  • build(deps): bump the deps group in /ui with 5 updates (d1b5aedaf)
  • build(deps): bump taskcluster from 58.0.2 to 59.2.0 in /taskcluster (dcb3409ae)
  • build(deps): bump the deps group with 7 updates (3381ad533)
  • build(deps): bump the deps group with 1 update (497c11ff6)
  • build(deps): bump the deps group in /taskcluster with 1 update (156da5e47)
  • build(deps): bump github/codeql-action from 2 to 3 (1d9788a67)
Changelog

Sourced from taskcluster's changelog.

v60.0.0

GENERAL

▶ [patch] Generic Worker: No longer logs out the redirect URL for the interactive shell feature since they are signed.

DEPLOYERS

▶ [MAJOR] #6759 Kubernetes pods use liveness probe instead of unconditionally killing containers daily.

▶ [patch] #6641 Worker-manager no longer counts "stopping" instances as part of the existing capacity when estimating the number of workers to start (although they are still counted towards maxCapacity).

Automated Package Updates

  • build(deps-dev): bump markdown-table from 2.0.0 to 3.0.3 (979bdebbe)
  • build(deps): bump the deps group in /ui with 5 updates (d1b5aedaf)
  • build(deps): bump taskcluster from 58.0.2 to 59.2.0 in /taskcluster (dcb3409ae)
  • build(deps): bump the deps group with 7 updates (3381ad533)
  • build(deps): bump the deps group with 1 update (497c11ff6)
  • build(deps): bump the deps group in /taskcluster with 1 update (156da5e47)
  • build(deps): bump github/codeql-action from 2 to 3 (1d9788a67)
Commits
  • 3cd5b8d v60.0.0
  • b825219 Merge pull request #6760 from taskcluster/feat/6759-liveness-probe
  • abb5866 Merge pull request #6758 from taskcluster/dependabot/npm_and_yarn/markdown-ta...
  • 14e789d feat(k8s): use liveness probe instead of killing container
  • f1b0ff8 Fix markdownTable import, there's no default export
  • 979bdeb build(deps-dev): bump markdown-table from 2.0.0 to 3.0.3
  • b3f2dfc Merge pull request #6744 from jcristau/wm-estimator-stopping
  • 149ce10 Merge pull request #6750 from taskcluster/dependabot/npm_and_yarn/ui/deps-6d0...
  • 9c2fb44 Merge pull request #6754 from taskcluster/dependabot/pip/taskcluster/taskclus...
  • d1b5aed build(deps): bump the deps group in /ui with 5 updates
  • 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 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 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 59.2.0 to 60.0.0.
- [Release notes](https://github.com/taskcluster/taskcluster/releases)
- [Changelog](https://github.com/taskcluster/taskcluster/blob/main/CHANGELOG.md)
- [Commits](taskcluster/taskcluster@v59.2.0...v60.0.0)

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

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 9, 2024
@zzzeid zzzeid merged commit 286d423 into main Jan 9, 2024
15 checks passed
@zzzeid zzzeid deleted the dependabot/pip/taskcluster-60.0.0 branch January 9, 2024 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant