Skip to content

fix(ci): use PAT for auto-tag to trigger downstream release build#692

Merged
lefarcen merged 1 commit intomainfrom
fix/auto-tag-use-pat
Mar 30, 2026
Merged

fix(ci): use PAT for auto-tag to trigger downstream release build#692
lefarcen merged 1 commit intomainfrom
fix/auto-tag-use-pat

Conversation

@lefarcen
Copy link
Copy Markdown
Collaborator

What

Switch desktop-auto-tag.yml from GITHUB_TOKEN to RELEASE_PAT for checkout and tag push.

Why

Tags pushed by GITHUB_TOKEN don't trigger on: push: tags workflows β€” this is GitHub's anti-recursion safeguard. As a result, merging the Release PR auto-tagged correctly but the desktop-release.yml build never fired. Had to manually dispatch for v0.1.8.

How

  • Checkout uses token: ${{ secrets.RELEASE_PAT }} so git push authenticates with PAT
  • gh release create also uses RELEASE_PAT for consistency
  • Added comments explaining why PAT is needed

Setup required

Add repo secret RELEASE_PAT: a Personal Access Token with contents:write scope.

Checklist

  • No code changes, workflow-only
  • Tested: v0.1.8 auto-tag worked, but build didn't trigger (this fixes that)

Tags pushed by GITHUB_TOKEN don't trigger on.push.tags workflows
(GitHub anti-recursion safeguard). Switch to RELEASE_PAT so the
desktop-release.yml build fires automatically after auto-tagging.

Requires: repo secret RELEASE_PAT with contents:write scope.
@lefarcen lefarcen merged commit 6cd0975 into main Mar 30, 2026
7 checks passed
@mrcfps mrcfps deleted the fix/auto-tag-use-pat branch March 30, 2026 13:25
@lefarcen lefarcen mentioned this pull request Apr 1, 2026
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.

2 participants