Bump taskcluster from 68.0.0 to 68.0.4 in /taskcluster

[dependabot]

Bumps taskcluster from 68.0.0 to 68.0.4.

Release notes

Sourced from taskcluster's releases.

v68.0.4

USERS

▶ [patch] #7233 getArtifact now encodes artifact names to return valid URLs even when the name contains unsafe characters.

Automated Package Updates

• build(deps-dev): bump webpack in /ui in the ui-node-deps group (b70132394)
• build(deps): bump taskcluster from 67.0.1 to 68.0.3 in /taskcluster (9ad8b9965)
• build(deps): bump golang.org/x/sys in the go-deps group (2d8e970a0)

v68.0.3

WORKER-DEPLOYERS

▶ [patch] #7218 Generic Worker Multiuser engine on Linux, macOS and FreeBSD now waits for the required task user to be logged in to the console session, rather than waiting for any user to be logged in, and then checking whether it is the anticipated user. This subtle change in behaviour means that temporarily a different user may be (or appear to be) logged into the console session without causing Generic Worker to panic. It is hoped that this will reduce intermittent issues where a different user appears to be logged in (such as gdm user on Linux) since it is suspected that this might just be a fleeting login that passes due to some race condition in the start up of the Gnome Desktop.

If this doesn't resolve the issue, and under certain circumstances, the gdm user instead remains logged in, i.e. it is not a fleeting login, we may need to restore the previous behaviour, since otherwise when the issue does occur, it would take a full 5 minutes before timing out, adding to costs unnecessarily. However, we hope that that will not be the case.

v68.0.2

WORKER-DEPLOYERS

▶ [patch] #7012 Generic Worker retains the interactive username it determines inside WaitForLoginCompletion (by returning it) to avoid needing to re-determine it later. The intention is to reduce intermittent errors caused by the underlying method to determine the interactive username itself intermittently failing. So long as the interactive username can be determined just once during the specidied timeout period, the value can be retained and used when required.

v68.0.1

GENERAL

▶ [patch] #7172 Fixes UI js error on dashboard on some deployments

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v68.0.4

USERS

▶ [patch] #7233 getArtifact now encodes artifact names to return valid URLs even when the name contains unsafe characters.

Automated Package Updates

• build(deps-dev): bump webpack in /ui in the ui-node-deps group (b70132394)
• build(deps): bump taskcluster from 67.0.1 to 68.0.3 in /taskcluster (9ad8b9965)
• build(deps): bump golang.org/x/sys in the go-deps group (2d8e970a0)

v68.0.3

WORKER-DEPLOYERS

▶ [patch] #7218 Generic Worker Multiuser engine on Linux, macOS and FreeBSD now waits for the required task user to be logged in to the console session, rather than waiting for any user to be logged in, and then checking whether it is the anticipated user. This subtle change in behaviour means that temporarily a different user may be (or appear to be) logged into the console session without causing Generic Worker to panic. It is hoped that this will reduce intermittent issues where a different user appears to be logged in (such as gdm user on Linux) since it is suspected that this might just be a fleeting login that passes due to some race condition in the start up of the Gnome Desktop.

If this doesn't resolve the issue, and under certain circumstances, the gdm user instead remains logged in, i.e. it is not a fleeting login, we may need to restore the previous behaviour, since otherwise when the issue does occur, it would take a full 5 minutes before timing out, adding to costs unnecessarily. However, we hope that that will not be the case.

v68.0.2

WORKER-DEPLOYERS

▶ [patch] #7012 Generic Worker retains the interactive username it determines inside WaitForLoginCompletion (by returning it) to avoid needing to re-determine it later. The intention is to reduce intermittent errors caused by the underlying method to determine the interactive username itself intermittently failing. So long as the interactive username can be determined just once during the specidied timeout period, the value can be retained and used when required.

v68.0.1

GENERAL

... (truncated)

Commits

• 10009ea v68.0.4
• 69129d9 Merge pull request #7234 from jcristau/artifact-s3-encode
• 4b7e1f7 queue: uri-encode artifact names in CDN urls
• 7e8feb7 Merge pull request #7232 from taskcluster/matt-boris/ghaSecurityFix
• 731e415 fix(gha): secure gha workflows
• 0c4590d Merge pull request #7231 from taskcluster/restore-snd-aloop-tests
• 1aaf885 Generic Worker: restore snd-aloop CI tests
• 651508a Merge pull request #7225 from taskcluster/dependabot/npm_and_yarn/ui/ui-node-...
• b701323 build(deps-dev): bump webpack in /ui in the ui-node-deps group
• bdefff7 Merge pull request #7224 from taskcluster/dependabot/pip/taskcluster/taskclus...
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
taskcluster	[>= 57.1.a, < 57.2]

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)

[bhearsum]

Failure is a timeout that's completely unrelated to this. This upgrade should be safe to take.

[dependabot]

Superseded by #9896.