[CHA-0] fix(ci): grant contents write to the release workflow - #264
Merged
Conversation
The release job creates the tag and the GitHub release, which needs contents: write. The workflow got contents: read in #261, so the 1.46.0 release failed with 403 after the package was already published.
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
1 participant
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.
The release job creates the tag and the GitHub release with
ncipollo/release-action, which needscontents: write. #261 set the workflow tocontents: read, so the first release after it, 1.46.0, failed withError 403: Resource not accessible by integration. The package reached Maven Central, only the tag and the release were missing.1.46.0 is now published by hand: https://github.com/GetStream/stream-chat-java/releases/tag/1.46.0
Verify: the next release run creates its tag and release without a 403.