Repository navigation
ci(release): grant contents:write to the release job - #72
Merged
Merged
Conversation
The job relied on the default GITHUB_TOKEN permission, which is now read-only: creating the v5.0.3-crc64 draft release failed with 403. Declare the permission explicitly, as the engine release workflow does. 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.
Why
Pushing
v5.0.3-crc64rantagged-release(run 40695807634): build, tar, deb and rpm passed, but Create Draft Release failed with403on every retry, so no draft release was created.The job declares no
permissions, so it depends on the defaultGITHUB_TOKENpermission of the repo/org. That default worked forv5.0.2-crc64andv4.1.12on 2026-09-30 and is now read-only. The engine release workflow declarescontents: writeexplicitly and kept working (v6.0.1-crc64on 2026-10-13).Change
Add
permissions: contents: writeto thetagged-releasejob, the minimum scopesoftprops/action-gh-releaseneeds to create the release and upload assets.After merge
Move the
v5.0.3-crc64tag to the merge commit (only this CI file differs from the current tag commit;LDB_VERSIONis unchanged) so the workflow creates the draft.master(4.x line) has the same workflow and will need the same change.🤖 Generated with Claude Code