Repository navigation
ci: pin GitHub Actions to commit SHAs - #7
Merged
Merged
Conversation
Each action is pinned to the commit its current tag points to, with the version kept as a comment, so the same code runs. Covers the workflows that ran in the last 30 days and the reusable workflows and composite actions they call. Our own iblai/* actions keep their tags. 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.
Pins every action in this repo's active workflows to a full commit SHA, with the version kept as a comment:
A tag like
v4can be moved to different code at any time, including by someone who takes over the action's repo. A commit SHA can't be moved.No change in behaviour. Each SHA is the commit its existing tag points to today, so the same code runs and no version changes. Old versions stay as they are; upgrading them is a separate change.
git ls-remoteand the GitHub API) and both agreed.uses:lines changed, and every changed file parses to the same YAML as before apart from the refs.Scope: the workflows that ran in the last 30 days, plus the reusable workflows and composite actions they call: 2 references in 2 files. Our own
iblai/*actions and reusable workflows keep their tags and branches.Keeping the pins current: this repo has no Dependabot config, so the pins stay where they are until someone updates them.
Merging: os, lms and web-frontend use this action at
@v1, so the pins reach them only after a release (v1.6.1) movesv1. Nothing changes for callers until then.🤖 Generated with Claude Code