Bump taskcluster from 65.1.0 to 65.2.0 in /taskcluster

[dependabot]

Bumps taskcluster from 65.1.0 to 65.2.0.

Release notes

Sourced from taskcluster's releases.

v65.2.0

USERS

▶ [minor] #7070 Generic Worker now sets the environment variable TASKCLUSTER_INSTANCE_TYPE in task commands to the instance type of the worker, if configured. This matches the (undocumented) behaviour of Docker Worker. D2G also passes this environment variable through to podman, to emulate Docker Worker's behaviour.

▶ [patch] Fixes UI issue in worker view where error was shown despite worker being found.

▶ [patch] #7059 D2G now includes libvirt OS group in generated Generic Worker task payloads that use Docker Worker KVM device.

▶ [patch] #6954 Fixes an issue with github badges that timed out on non-existing branches.

▶ [patch] Tasks using notify.pulse.<topic>.on-<event> routes now send out messages using the specified topic. This means it's now possible to subscribe to specific topics.

DEVELOPERS

▶ [minor] #5073 Github service supports issue_comment events to trigger jobs through /tasckluster param comments in open Pull Requests. .taskcluster.yml in default branch should allow this with policy.allowComments: collaborators value. Tasks would be rendered with tasks_for = "github-issue-comment" and event.taskcluster_comment = param This is an implementation of RFC 168

▶ [patch] #6567 yarn generate commands will attempt to run pg_dump inside the docker container if local binary is missing or its version is different from the server version.

Automated Package Updates

• build(deps): bump taskcluster-taskgraph (8daf19d4c)
• build(deps): bump the go-deps group with 4 updates (60ca4228f)

Changelog

Sourced from taskcluster's changelog.

v65.2.0

USERS

▶ [minor] #7070 Generic Worker now sets the environment variable TASKCLUSTER_INSTANCE_TYPE in task commands to the instance type of the worker, if configured. This matches the (undocumented) behaviour of Docker Worker. D2G also passes this environment variable through to podman, to emulate Docker Worker's behaviour.

▶ [patch] Fixes UI issue in worker view where error was shown despite worker being found.

▶ [patch] #7059 D2G now includes libvirt OS group in generated Generic Worker task payloads that use Docker Worker KVM device.

▶ [patch] #6954 Fixes an issue with github badges that timed out on non-existing branches.

▶ [patch] Tasks using notify.pulse.<topic>.on-<event> routes now send out messages using the specified topic. This means it's now possible to subscribe to specific topics.

DEVELOPERS

▶ [minor] #5073 Github service supports issue_comment events to trigger jobs through /tasckluster param comments in open Pull Requests. .taskcluster.yml in default branch should allow this with policy.allowComments: collaborators value. Tasks would be rendered with tasks_for = "github-issue-comment" and event.taskcluster_comment = param This is an implementation of RFC 168

▶ [patch] #6567 yarn generate commands will attempt to run pg_dump inside the docker container if local binary is missing or its version is different from the server version.

Automated Package Updates

• build(deps): bump taskcluster-taskgraph (8daf19d4c)
• build(deps): bump the go-deps group with 4 updates (60ca4228f)

Commits

• f1da8f2 v65.2.0
• 78980ae Using issue_comment even to trigger builds (#7050)
• 9099033 Merge pull request #7071 from taskcluster/issue7070
• eb91bf3 Merge branch 'main' into issue7070
• ce6f6ab Docs: add TASKCLUSTER_INSTANCE_TYPE to env vars docs
• dfdec07 Merge pull request #7072 from taskcluster/feat/db-schema-dump
• ce43804 Generic Worker: add test for TASKCLUSTER_INSTANCE_TYPE
• affb2f4 Issue 7070: Set TASKCLUSTER_INSTANCE_TYPE env var in Generic Worker tasks
• 3552bb5 yarn generate uses any postgres container to run pg_dump
• 35b4e2d Merge pull request #7069 from ahal/notify
• 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)