fix(CI-CD): use Trigganator app token for tag pushes - #62
Merged
Conversation
✅ PR Validation Passed
📋 Pipeline Status
🤖 Generated by @helpers4 CI • 2026-08-10 |
…OKEN GITHUB_TOKEN can never push a tag whose ref history touches .github/workflows/*.yml — GitHub blocks it outright, and there's no permissions: key that fixes this for the default token (confirmed against GitHub's own schema; adding one just makes the file invalid, already hit that once). The actual fix needs a token with the app-level 'workflows' permission. Trigganator is already installed for this repo and used two jobs down (trigger-website) — mint a second, narrower token from the same app (contents + workflows only, scoped to this repo) instead of provisioning a whole separate credential. Whether this actually works depends on Trigganator's installation having been granted the Workflows permission — that's only visible in GitHub's own UI, not something checkable from here. If it wasn't granted, create-github-app-token fails with a clear permission error and this needs a real PAT instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Trigganator's installation doesn't have the Workflows app permission granted (checked: Actions + Code only). Pushinator now does (added: actions, administration, code, issues, pull requests, workflows) — same minting logic, just the other app's credentials. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
baxyz
force-pushed
the
release-tag-push-app-token
branch
from
August 10, 2026 22:56
e3b3371 to
9a1ad01
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GITHUB_TOKENwith a Trigganator-minted token (scoped:contents: write+workflows: write, this repo only) for the one step that actually needs it — pushing tags whose ref history touches.github/workflows/*.yml.trigger-websitejob (vars.TRIGGANATOR_ID/secrets.TRIGGANATOR_KEY) instead of provisioning a new credential.permissions:block to just what GITHUB_TOKEN still needs for the other steps (GHCR publish, devcontainers/action's generate-docs commit).Open question
This only works if Trigganator's installation has actually been granted the "Workflows: Read and write" app permission — not something checkable from the API access this session has.
actions/create-github-app-tokenwill fail with a clear, specific error at mint time if it wasn't granted, so worst case this is a clean, informative failure, not a silent one.Test plan
release.yml only triggers on push to
mainmatchingsrc/*/devcontainer-feature.json— a PR can't exercise this path. Real signal only comes after merge, on the next push that bumps a feature version and creates a tag whose history touches a workflow file (which is basically every push right now, since this PR itself touches one).🤖 Generated with Claude Code