Bump taskcluster from 60.1.3 to 65.0.1

[dependabot[bot]]

Bumps taskcluster from 60.1.3 to 65.0.1.

Release notes

Sourced from taskcluster's releases.

v65.0.1

GENERAL

▶ [patch] Upgrades to go1.22.3 (SECURITY release). Was supposed to be handled in PR #7006, but was accidentally left out.

v65.0.0

WORKER-DEPLOYERS

▶ [MAJOR] #7017 Generic Worker multiuser engine now places task directories under /home (Linux and FreeBSD) and /Users on macOS. Previously it was placing them under / by default on all three platforms, unless either HOME was set to a non-standard value in the process launching Generic Worker multiuser engine, or if tasksDir was explicitly set in Generic Worker config.

This is a bug fix, but due to being a significant change in behaviour, is being released as a major change to trigger a major version bump.

USERS

▶ [patch] #6117 Fixes Worker page when queue information was missing and error was displayed. If worker-manager data exists for this worker, it would be displayed instead.

▶ [patch] #6117 Workers in UI use consistent navigation element that allows to switch between worker pool definition, workers, pending and claimed tasks.

▶ [patch] #6117 Workers list page in UI shows "Worker Pool" link when it is available to improve navigation.

v64.3.0

GENERAL

▶ [patch] Upgrades to node v20.13.0 and go1.22.3 (SECURITY release).

WORKER-DEPLOYERS

▶ [minor] #6979 Generic Worker multiuser engine on Linux now sets environment variableXDG_RUNTIME_DIR to /run/user/<UID> in task command processes (unless Generic Worker config setting runTasksAsCurrentUser is set to true).

USERS

▶ [patch] bug 1768667 Adds Task Group link in UI for indexed tasks. Introduces new route to redirect to the Task Group view: /tasks/index/:namespace/:indexTask/task-group

Automated Package Updates

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v65.0.1

GENERAL

▶ [patch] Upgrades to go1.22.3 (SECURITY release). Was supposed to be handled in PR #7006, but was accidentally left out.

v65.0.0

WORKER-DEPLOYERS

▶ [MAJOR] #7017 Generic Worker multiuser engine now places task directories under /home (Linux and FreeBSD) and /Users on macOS. Previously it was placing them under / by default on all three platforms, unless either HOME was set to a non-standard value in the process launching Generic Worker multiuser engine, or if tasksDir was explicitly set in Generic Worker config.

This is a bug fix, but due to being a significant change in behaviour, is being released as a major change to trigger a major version bump.

USERS

▶ [patch] #6117 Fixes Worker page when queue information was missing and error was displayed. If worker-manager data exists for this worker, it would be displayed instead.

▶ [patch] #6117 Workers in UI use consistent navigation element that allows to switch between worker pool definition, workers, pending and claimed tasks.

▶ [patch] #6117 Workers list page in UI shows "Worker Pool" link when it is available to improve navigation.

v64.3.0

GENERAL

▶ [patch] Upgrades to node v20.13.0 and go1.22.3 (SECURITY release).

WORKER-DEPLOYERS

▶ [minor] #6979 Generic Worker multiuser engine on Linux now sets environment variableXDG_RUNTIME_DIR to /run/user/<UID> in task command processes (unless Generic Worker config setting runTasksAsCurrentUser is set to true).

USERS

▶ [patch] bug 1768667 Adds Task Group link in UI for indexed tasks.

... (truncated)

Commits

• c856774 v65.0.1
• fb3e304 Merge pull request #7021 from taskcluster/matt-boris/go1.22.3ForRealThisTime
• 7156528 build(deps): upgrade to go1.22.3
• c461353 v65.0.0
• 984ea83 Merge pull request #7019 from taskcluster/feat/w-m-ui
• 01d3559 feat(ui): Using consistent UI navigation across worker pages
• f44c5cf Merge pull request #7016 from taskcluster/feat/w-m-ui
• ceac13b Merge pull request #7018 from taskcluster/issue7017
• f7fe047 Issue 7017 - Generic Worker multiuser engine on macOS/Linux/FreeBSD: Fix loca...
• b5fae84 feat(ui): Display "worker pool" link button on the workers view
• 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 show 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)

[dependabot[bot]]

Superseded by #434.