Skip to content

Grant contents: write so the release workflow can push tags#418

Merged
twschiller merged 1 commit into
mainfrom
contents-write-release
Jul 10, 2026
Merged

Grant contents: write so the release workflow can push tags#418
twschiller merged 1 commit into
mainfrom
contents-write-release

Conversation

@grahamlangford

Copy link
Copy Markdown
Collaborator

Problem

After #417 fixed npm trusted publishing, the Publish workflow got further but failed at git push --follow-tags:

remote: Permission to pixiebrix/webext-messenger.git denied to github-actions[bot].
fatal: ... The requested URL returned error: 403

The workflow's GITHUB_TOKEN only had contents: read, but pushing the version tag and running gh release create both require contents: write. (failed run)

Fix

Change the workflow permission from contents: read to contents: write. id-token: write is retained for OIDC.

🤖 Generated with Claude Code

git push --follow-tags and gh release create both need write access to
contents; the workflow only had contents: read, so github-actions[bot]
got a 403 after a successful npm publish.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@twschiller
twschiller merged commit 72f8b39 into main Jul 10, 2026
5 checks passed
@twschiller
twschiller deleted the contents-write-release branch July 10, 2026 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants