Skip to content

[Backport release-1.2] [Backport release-1.3] fix(ci): pass app token to Publish draft release step - #2575

Closed
github-actions[bot] wants to merge 1 commit into
release-1.2from
backport-2572-to-release-1.2
Closed

github-actions[bot] wants to merge 1 commit into
release-1.2from
backport-2572-to-release-1.2

Conversation

@github-actions

@github-actions github-actions Bot commented May 6, 2026

Copy link
Copy Markdown

Description

Backport of #2572 to release-1.2.

The Publish draft release step used the workflow's default GITHUB_TOKEN,
which does not return draft releases from listReleases — so the script
failed with "Draft release for vX.Y.Z not found" and every release tag
had to be undrafted manually.

This same bug was fixed once before in 4db55ac ([ci] Add Github
token to fetch draft releases) by adding github-token: GH_PAT to the
listing step. It was lost during the refactor in 66a756b that combined
the separate listing/flags/publish steps into a single Publish step,
and not restored when f96b2da migrated remaining github-token usages
from GH_PAT to the cozystack-ci App token.

Add github-token: app-token.outputs.token to the merged step so it
shares the same auth as the rest of the workflow.

Assisted-By: Claude <[email protected]>
Signed-off-by: Myasnikov Daniil <[email protected]>
(cherry picked from commit 7d2fe2f)
(cherry picked from commit 70e8f84)
@dosubot dosubot Bot added area/ci Issues or PRs related to CI workflows, GitHub Actions, automation area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/backport-previous Categorizes issue or PR as requiring a backport to the previous release line labels May 6, 2026
@myasnikovdaniil

Copy link
Copy Markdown
Contributor

Duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ci Issues or PRs related to CI workflows, GitHub Actions, automation area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/backport-previous Categorizes issue or PR as requiring a backport to the previous release line

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant