Repository navigation
ci: fix permissions in the release.yml - #249
Merged
Merged
Conversation
xyuria-zededa
approved these changes
Oct 23, 2026
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.
Fix release workflow 403 when publishing artifacts
The v2.9.0-rc release run failed at goreleaser's publish step:
The job's GITHUB_TOKEN had only
Contents: read.release.ymldoesn't declarepermissions, so it inherits the repo/org default, which is now read-only.Creating or updating a release and uploading assets needs
contents: write.This grants
contents: writeto the release workflow only.Follow-up: re-running the existing v2.9.0-rc run uses the workflow at the tagged
commit, so after merge either re-tag the RC on the new commit or cut v2.9.0-rc2.