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

Bump taskcluster from 44.23.4 to 49.2.0 #359

Merged
merged 1 commit into from
May 5, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 5, 2023

Bumps taskcluster from 44.23.4 to 49.2.0.

Release notes

Sourced from taskcluster's releases.

v49.2.0

GENERAL

▶ [patch] Upgrade Node.js version to 18.16.0 and go version to 1.19.9.

USERS

▶ [minor] #6169 Adds interactive shell support to generic-worker.

The worker configuration variable enableInteractive needs to be set to true to allow the interactive shell feature to be enabled. enableInteractive is disabled by default.

Once the worker configuration variable is set, the interactive feature can be enabled on a per-task basis.

To enable, set task.payload.features.interactive to true. And toggle on Interactive in the Create Task view of the UI.

v49.1.3

WORKER-DEPLOYERS

▶ [patch] #6186 Worker-manager refreshes worker from database before calling removeWorker on terminateAfter time exceeded to prevent from stopping workers that were already registered and running since worker scanner has started.

v49.1.2

USERS

▶ [patch] #6185 Fixed quarantine worker 'reason' field schema to be optional.

▶ [patch] #6058 Generic Worker no longer modifies the Access Control Lists of the Interactive Desktop and the associated Windows Station unless additional OS groups have been specified in the task payload osGroups property. Previously Generic Worker would modify the ACLs of these objects even if the access token it was using for launching task command processes already had suitable permissions. This patch is a workaround for a more general issue, which is that the ACL modifications seem not to be appropriate in all cases when a new access token is needed. See https://bugzilla.mozilla.org/show_bug.cgi?id=1815711.

There is a likely to be a follow up fix for the ACL modifications that occur when a new access token is required, once it is understood why the current modifications are not always sufficient.

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

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v49.2.0

GENERAL

▶ [patch] Upgrade Node.js version to 18.16.0 and go version to 1.19.9.

USERS

▶ [minor] #6169 Adds interactive shell support to generic-worker.

The worker configuration variable enableInteractive needs to be set to true to allow the interactive shell feature to be enabled. enableInteractive is disabled by default.

Once the worker configuration variable is set, the interactive feature can be enabled on a per-task basis.

To enable, set task.payload.features.interactive to true. And toggle on Interactive in the Create Task view of the UI.

v49.1.3

WORKER-DEPLOYERS

▶ [patch] #6186 Worker-manager refreshes worker from database before calling removeWorker on terminateAfter time exceeded to prevent from stopping workers that were already registered and running since worker scanner has started.

v49.1.2

USERS

▶ [patch] #6185 Fixed quarantine worker 'reason' field schema to be optional.

▶ [patch] #6058 Generic Worker no longer modifies the Access Control Lists of the Interactive Desktop and the associated Windows Station unless additional OS groups have been specified in the task payload osGroups property. Previously Generic Worker would modify the ACLs of these objects even if the access token it was using for launching task command processes already had suitable permissions. This patch is a workaround for a more general issue, which is that the ACL modifications seem not to be appropriate in all cases when a new access token is needed. See https://bugzilla.mozilla.org/show_bug.cgi?id=1815711.

There is a likely to be a follow up fix for the ACL modifications that occur when a new access token is required, once it is understood why the current modifications are not always sufficient.

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

... (truncated)

Commits
  • dfebc54 v49.2.0
  • 9735d36 Merge pull request #6170 from taskcluster/matt-boris/gwInteractive
  • 2de2eb9 Test interactive shell session with wrong secret
  • e3f5e0b Update changelog to include info on new worker config variable
  • 4aa7379 Fix websocktunnel usage string
  • dda83ab Put interactive support behind a config toggle, reduce some duplicate code
  • ad2c6d5 Use slugid secret in URL
  • b85d2e4 Listen on /shell, drop wss for now, correctly use exposer path by appending t...
  • afc3b5c Remove support from windows and docker engine, use process.Command to spawn b...
  • 377cc81 Log to task log and handle cmd.Wait error properly
  • 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)

Bumps [taskcluster](https://github.com/taskcluster/taskcluster) from 44.23.4 to 49.2.0.
- [Release notes](https://github.com/taskcluster/taskcluster/releases)
- [Changelog](https://github.com/taskcluster/taskcluster/blob/main/CHANGELOG.md)
- [Commits](taskcluster/taskcluster@v44.23.4...v49.2.0)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 5, 2023
@marco-c marco-c merged commit 5b1977e into master May 5, 2023
@marco-c marco-c deleted the dependabot/pip/taskcluster-49.2.0 branch May 5, 2023 13:13
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