Fix write permission for the existing minor release alias job - #60
Merged
Merged
Conversation
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 v0.5.1 npm publication and GitHub release succeeded, but the existing minor-alias job received a 403 because it inherited the workflow's contents: read permission. Grant contents: write only to that job, matching its existing purpose and the release job's scope.
The documented movable v0.5 alias has been refreshed to the validated v0.5.1 commit. Published patch tags, release notes, assets and packages remain unchanged. No new release is needed for this workflow-only correction.
Validation: actionlint and git diff --check pass. CLI/product code and distribution files are unchanged; the normal CI/security checks also run.