Repository navigation
Conversation
Org will require full-length SHA pins for Actions. Pin every uses: ref to the SHA of its current tag; keep the tag as a comment.
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.
Org policy "require actions pinned to full-length commit SHA" is about to be turned on for NodeOps-app (post-incident hardening). Unpinned
uses:refs will fail once it is on.What: every third-party
uses:now points at the commit SHA its current tag resolves to. The original tag is kept as a trailing comment. No version changes.Merge this, then the org setting gets enabled.