fix(ci): use ADMIN_TOKEN for release automation#23
Merged
Conversation
GITHUB_TOKEN cannot push version-bump commits to branches with PR protection. Use org-level ADMIN_TOKEN instead, with skip-check to prevent infinite loops on release commits. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
ADMIN_TOKENinstead ofGITHUB_TOKENfor semantic-releaseRoot cause
The release workflow for PR #22 (submodule removal) just failed because
GITHUB_TOKENcan't push the version-bump commit to main (branch protection requires PRs). Same fix as applied to openadapt-evals and openadapt-capture.🤖 Generated with Claude Code