Pin GitHub Actions to commit SHAs - #3
Merged
Merged
Conversation
A major tag like v5 can be moved to point at new code, and the release job runs with contents: write. A SHA cannot move. Each pin is the commit the major tag pointed at today, so behaviour does not change.
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
2 participants
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.
Both workflows used moving major tags, and the release job runs with
contents: write. A tag can be repointed at new code, a SHA cannot.Each pin is the commit the major tag pointed at today, so nothing changes in behaviour.
actions/checkoutandactions/setup-nodeboth have a newer major upstream. I left those bumps out so this PR stays a no-op.