Repository navigation
docs: pin the shared workflows to a commit SHA instead of @v1 - #2
Merged
Merged
Conversation
Callers reference a release by commit SHA with a version comment, so Dependabot can bump it and a tag can't change under them. The zizmor policy now requires a SHA for every uses:, our own workflows included.
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.
Callers now pin the shared workflows to the commit SHA of a release, with a
# vX.Y.Zcomment, instead of the moving@v1tag. A tag can be moved, a SHA can't, and Dependabot still bumps the SHA and comment on a new release. The go-sms-issuer canary also showed that CodeQL flags every@v1/@mainreference (actions/unpinned-tag), in every consuming repository.zizmor.ymlandtemplates/zizmor.yml: drop theref-pinexception forprivacybydesign/*; everyuses:needs a SHA.Part of YIV-401.