mozilla / task-boot

Taskcluster Boot utils
Mozilla Public License 2.0
5 stars 15 forks source link

Bump taskcluster from 44.23.4 to 49.1.1 #352

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps taskcluster from 44.23.4 to 49.1.1.

Release notes

Sourced from taskcluster's releases.

v49.1.1

GENERAL

▶ [patch] Generic worker feature task.Payload.OnExitStatus.PurgeCaches now only purges caches related to the task, instead of all caches on the worker.

USERS

▶ [patch] #5773 Fix UI bug when user profile was missing and causing whole page to crash.

▶ [patch] bug 1590886 Github status handler listens to both taskPending and taskRunning events.

v49.1.0

ADMINS

▶ [minor] bug 1826417 Changes the way expire-artifacts works. It uses a separate function to fetch all expired artifacts and then uses bulk delete to remove them from S3 and the database.

v49.0.0

GENERAL

▶ [patch] Builds and tests generic worker (multiuser) on macOS Ventura 13 on new, arm64 machines.

USERS

▶ [MAJOR] Remove python 3.6 support as it's past its end-of-life date.

Add python 3.10 and python 3.11 support.

▶ [minor] #6147 Adds task.payload.onExitStatus.purgeCaches feature to generic worker to bring to parity with an existing docker worker feature.

purgeCaches is an array of exit status code integers that the user wants all caches associated with the task to be purged.

v48.3.0

ADMINS

▶ [minor] #4343 Workers can be quarantined with an optional comment. queue.quarantineWorker accepts a quarantineInfo string. Quarantine details also include timestamp and clientId of the user who quarantined the worker. This information can be fetched with worker-manager.getWorker. quarantineDetails would be a list of all the quarantine requests made for the worker. UI shows this history and allows to specify a comment for quarantine request.

USERS

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v49.1.1

GENERAL

▶ [patch] Generic worker feature task.Payload.OnExitStatus.PurgeCaches now only purges caches related to the task, instead of all caches on the worker.

USERS

▶ [patch] #5773 Fix UI bug when user profile was missing and causing whole page to crash.

▶ [patch] bug 1590886 Github status handler listens to both taskPending and taskRunning events.

v49.1.0

ADMINS

▶ [minor] bug 1826417 Changes the way expire-artifacts works. It uses a separate function to fetch all expired artifacts and then uses bulk delete to remove them from S3 and the database.

v49.0.0

GENERAL

▶ [patch] Builds and tests generic worker (multiuser) on macOS Ventura 13 on new, arm64 machines.

USERS

▶ [MAJOR] Remove python 3.6 support as it's past its end-of-life date.

Add python 3.10 and python 3.11 support.

▶ [minor] #6147 Adds task.payload.onExitStatus.purgeCaches feature to generic worker to bring to parity with an existing docker worker feature.

purgeCaches is an array of exit status code integers that the user wants all caches associated with the task to be purged.

v48.3.0

ADMINS

▶ [minor] #4343 Workers can be quarantined with an optional comment. queue.quarantineWorker accepts a quarantineInfo string. Quarantine details also include timestamp and clientId of the user who quarantined the worker. This information can be fetched with worker-manager.getWorker. quarantineDetails would be a list of all the quarantine requests made for the worker.

... (truncated)

Commits
  • 23fb4d2 v49.1.1
  • 07500e1 Merge pull request #6182 from taskcluster/feat/github-statuses-pending
  • 20e0613 Merge pull request #6183 from taskcluster/matt-boris/fixPurgeCaches
  • 4ddd6ca Merge pull request #6181 from taskcluster/feat/5773-ui-user-profile-fix
  • daa6ea9 Address PR comments
  • 56395f6 fix(generic-worker): only purge task caches
  • 3b91ab4 Update changelog/issue-5773.md
  • 963fcf0 feat(github): Set status back to pending as soon as task restarts
  • 09bd294 feat(ui): Fix profile name handling in UI
  • 4537ead Merge pull request #6179 from taskcluster/matt-boris/retryDockerWorkerChunkTasks
  • 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 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[bot] commented 1 year ago

Superseded by #354.