Skip to content

build(deps): bump taskcluster from 84.0.2 to 86.0.2 in /report #2698

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 30, 2025

Bumps taskcluster from 84.0.2 to 86.0.2.

Release notes

Sourced from taskcluster's releases.

v86.0.2

WORKER-DEPLOYERS

▶ [patch] Generic Worker: prefer strconv.ParseUint() over strconv.Atoi() when resulting int is converted to an int type of smaller size to prevent unexpected values.

USERS

▶ [patch] #6951 Fixes UI issue with state when tasks change. Sometimes actions could be fired against wrong task group.

▶ [patch] Generic Worker multiuser on macOS now ensures finalisers are not called on launch agent pipes while they are still in use.

v86.0.1

WORKER-DEPLOYERS

▶ [patch] Generic Worker: Fix for intermittent "sendmsg: bad file descriptor" on macOS multiuser.

v86.0.0

USERS

▶ [MAJOR] #7356 Generic Worker multiuser engine on macOS now executes all task commands via a Launch Agent running in the context of the desktop session. This means that task commands now have full access to desktop session services, such as the clipboard.

Deployment Instructions - macOS

On macOS it is essential that after updating the generic-worker binary, before starting the worker up, that the file next-task-user.json is deleted. This file should only be deleted when upgrading the worker, not every time the worker runs. This will cause Generic Worker to create new task users, which is needed for the launch agent to work. Otherwise the new Generic Worker would try to use task users created by the old Generic Worker user, which would not work. Note, the full path to this file can be seen in the generic worker logs, if you are not sure where to find it on the file system.

Note, this only needs to be done once when installing the new version of Generic Worker. After that, Generic Worker will continue to mange this file itself as normal.

Automated Package Updates

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v86.0.2

WORKER-DEPLOYERS

▶ [patch] Generic Worker: prefer strconv.ParseUint() over strconv.Atoi() when resulting int is converted to an int type of smaller size to prevent unexpected values.

USERS

▶ [patch] #6951 Fixes UI issue with state when tasks change. Sometimes actions could be fired against wrong task group.

▶ [patch] Generic Worker multiuser on macOS now ensures finalisers are not called on launch agent pipes while they are still in use.

v86.0.1

WORKER-DEPLOYERS

▶ [patch] Generic Worker: Fix for intermittent "sendmsg: bad file descriptor" on macOS multiuser.

v86.0.0

USERS

▶ [MAJOR] #7356 Generic Worker multiuser engine on macOS now executes all task commands via a Launch Agent running in the context of the desktop session. This means that task commands now have full access to desktop session services, such as the clipboard.

Deployment Instructions - macOS

On macOS it is essential that after updating the generic-worker binary, before starting the worker up, that the file next-task-user.json is deleted. This file should only be deleted when upgrading the worker, not every time the worker runs. This will cause Generic Worker to create new task users, which is needed for the launch agent to work. Otherwise the new Generic Worker would try to use task users created by the old Generic Worker user, which would not work. Note, the full path to this file can be seen in the generic worker logs, if you are not sure where to find it on the file system.

Note, this only needs to be done once when installing the new version of Generic Worker. After that, Generic Worker will continue to mange this file itself as normal.

Automated Package Updates

... (truncated)

Commits
  • 9ce3264 v86.0.2
  • 727b898 Merge pull request #7808 from taskcluster/matt-boris/mountsLoggingCleanup
  • a406d11 Merge pull request #7807 from taskcluster/feat/task-page-react-state
  • a10653a chore(generic-worker): clean up mounts log when directory cannot be created
  • 521bc8d Merge pull request #7806 from taskcluster/gw-keepalive-agent-pipes-darwin-mul...
  • 772ee84 Merge pull request #7805 from taskcluster/matt-boris/codeqlFixes
  • 232f5bb feat(ui): Fix state for task view page
  • cdddb3d Generic Worker: keep both ends of Launch Agent pipes alive while in use
  • cfacee5 chore(generic-worker): prefer ParseUint over Atoi where possible
  • 330127c v86.0.1
  • 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 84.0.2 to 86.0.2.
- [Release notes](https://github.com/taskcluster/taskcluster/releases)
- [Changelog](https://github.com/taskcluster/taskcluster/blob/main/CHANGELOG.md)
- [Commits](taskcluster/taskcluster@v84.0.2...v86.0.2)

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

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the report Python tool to upload reports label Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
report Python tool to upload reports
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants