Skip to content

fix(ci): use GITHUB_TOKEN for release approval#151

Merged
fahimfaisaal merged 1 commit into
mainfrom
fix/release-approval-github-token
Jun 25, 2026
Merged

fix(ci): use GITHUB_TOKEN for release approval#151
fahimfaisaal merged 1 commit into
mainfrom
fix/release-approval-github-token

Conversation

@fahimfaisaal

Copy link
Copy Markdown
Member

Summary

Fixes release CI failing at manual-approval with:

403 Resource not accessible by personal access token

The approval step now uses GITHUB_TOKEN (workflow already grants issues: write). GORELEASER_TOKEN stays on the GoReleaser job only.

Also adds task release:remove to unwind a failed tag/release before retrying.

Usage

# After merging, re-tag for v0.13.0:
task release:remove -- v0.13.0   # optional — clean up failed attempt
task release -- v0.13.0          # push tag again once fix is on main

Test plan

  • Workflow YAML validates (approval uses secrets.GITHUB_TOKEN)
  • Merge to main, then re-push v0.13.0 or cut a new patch tag

manual-approval needs Issues write; GORELEASER_TOKEN is release-scoped and
returns 403 on issue creation. Add task release:remove to unwind failed tags.
@fahimfaisaal
fahimfaisaal merged commit d06f7db into main Jun 25, 2026
@fahimfaisaal
fahimfaisaal deleted the fix/release-approval-github-token branch June 25, 2026 08:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant