ci: push release bump+tag with GITHUB_TOKEN instead of a missing GitHub App#7
Merged
Merged
Conversation
The release job failed at "Mint release app token" because RELEASE_APP_ID / RELEASE_APP_PRIVATE_KEY are not set on this repo. The App existed only to bypass main's branch protection when pushing the version bump + tag -- but main has no branch protection, so the App is unnecessary. Push directly with the built-in GITHUB_TOKEN (contents: write). This unblocks the release, which then publishes to public PyPI (the existing pending publisher: workflow release.yml, environment pypi) and the Azure feed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Claude finished @uipreliga's task in 1m 35s —— View job PR Review: Fix Release Workflow GitHub Token Issue
|
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.
Problem
The first real Release run (dispatch on
main) failed immediately at "Mint release app token":RELEASE_APP_ID/RELEASE_APP_PRIVATE_KEYare not configured on this repo, so the App token can't be minted — andpublish-pypi(needs: release) was skipped. Nothing was published (safe failure).Why the App isn't needed
The App token existed only to bypass branch protection when pushing the version-bump commit + tag. But
mainhas no branch protection (Branch not protected), so a plainGITHUB_TOKENwithcontents: writecan push directly.Change (1 file)
Mint release app tokenstep.GITHUB_TOKEN(persisted for the push).permissions: contents: write(wasread) to allow the bump/tag push.GH_TOKEN→secrets.GITHUB_TOKEN.No other behavior changes — the run still bumps the version, publishes to the Azure feed and public PyPI (existing pending publisher: workflow
release.yml, envpypi), and pushes the GHCR image.🤖 Generated with Claude Code