Repository navigation
ci: pin third-party actions to exact commit SHAs - #65
Open
justinbanon-agent wants to merge 1 commit into
Open
justinbanon-agent wants to merge 1 commit into
justinbanon-agent wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What this does
Pins 1 third-party action reference in 1 file to the exact commit its tag points to today, with the version in a comment. This is option 2 from bosonprotocol/core-components#1046.
@v4can be moved by its publisher; a commit SHA cannot. That is what happened withtj-actions/changed-filesin March 2025.Pinned
.github/workflows/lint-pr.yamlamannn/action-semantic-pull-request@v5.5.2amannn/action-semantic-pull-request@cfb6070Full SHAs are in the diff.
Left as they are
Nothing: every third-party reference in this repo is now pinned.
How to check
On this pull request, these workflows start (no "workflow file issue") and pass:
In each job's "Set up job" log, the "Download action repository" lines show the pinned SHAs.
Once this is green, the organisation's "any version" entries for these actions can be swapped for the exact SHAs, but only for an action that no other repo still uses by tag.
Rollback: revert this merge.
Prepared by Claude for Justin; Ludo reviews and merges. Refs bosonprotocol/core-components#1046.
🤖 Generated with Claude Code