Repository navigation
release: tag through the API, not git push - #277
Merged
Merged
Conversation
v20261119.01 built, signed and attested, and its tag push was refused: GitHub will not let GITHUB_TOKEN push a ref whose commits change .github/workflows/ without a workflows permission that token cannot hold. It is the first release with a workflow change since the one before it. The API creates the ref under contents: write. Co-Authored-By: Claude Opus 5.5 <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
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.
Release run 44544741603 built, signed and attested v20261119.01. Then its tag push was refused:
GitHub will not let
GITHUB_TOKENpush a ref whose commits change.github/workflows/without aworkflowspermission, and that token cannot hold one. This is the first release with a workflow change since the one before it: lab.yml, image.yml and refresh.yml all changed after v20261114.02.release:tagnow creates the ref withgh api …/git/refs, under thecontents: writethe release already has. A version that is already tagged is still refused: creating a ref that exists fails with 422.Nothing was published and no tag exists, so once this is on main a new dispatch takes v20261119.01 again.
🤖 Generated with Claude Code