Skip to content

release: tag through the API, not git push - #277

Merged
aledbf merged 1 commit into
mainfrom
release-tag-api
Nov 19, 2026
Merged

aledbf merged 1 commit into
mainfrom
release-tag-api

Conversation

@aledbf

@aledbf aledbf commented Nov 19, 2026

Copy link
Copy Markdown
Member

Release run 44544741603 built, signed and attested v20261119.01. Then its tag push was refused:

! [remote rejected] v20261119.01 -> v20261119.01 (refusing to allow a GitHub App to create or update workflow `.github/workflows/lab.yml` without `workflows` permission)

GitHub will not let GITHUB_TOKEN push a ref whose commits change .github/workflows/ without a workflows permission, 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:tag now creates the ref with gh api …/git/refs, under the contents: write the 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

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>
@aledbf
aledbf merged commit 8f5e288 into main Nov 19, 2026
1 check passed
@aledbf
aledbf deleted the release-tag-api branch November 19, 2026 14:54
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.

1 participant