Pin GitHub Actions to commit SHAs and add Dependabot - #214
Merged
Conversation
Version tags are mutable. The tj-actions/changed-files compromise repointed every tag at a commit that dumped runner secrets into build logs; only SHA-pinned consumers were unaffected. Three of the actions here are third-party (setup-uv, actions-setup-redis, setup-buildx-action). The Dependabot config is the half that makes SHA pinning sustainable: it rewrites the SHA and its version comment together, so the workflows track upstream instead of freezing. Grouped monthly to keep it to one pull request. Every pin resolves the tag already in use, so behavior is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Jul 28, 2026
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.
Version tags are mutable. The
tj-actions/changed-filescompromise in March 2025 repointed every version tag at a commit that dumped runner secrets into build logs, hitting roughly 23,000 repositories; tag pinning offered no protection and SHA pinning offered complete protection. Three of the actions used here are third-party —astral-sh/setup-uv,shogo82148/actions-setup-redis, anddocker/setup-buildx-action.The Dependabot config is the half that makes this sustainable, and it is not optional. Dependabot understands SHA-pinned actions and rewrites the SHA together with its trailing
# vNcomment, so pinned workflows keep tracking upstream. Without it, pinning silently freezes the workflows on whatever was current the day they were written — which is exactly what happened in ord-app and ord-infrastructure, both fully SHA-pinned with no update mechanism and both a major version behind onsetup-uv.Updates are grouped so this arrives as one pull request a month rather than one per action.
Every pin resolves the tag that was already in use, so nothing changes behavior. Resolved through the git refs API, dereferencing annotated tags to their commits. All pre-commit hooks pass.
Part of an org-wide sweep alongside ord-schema#910 and ord-data#264.
🤖 Generated with Claude Code
Greptile Summary
Pins every GitHub Actions dependency to an immutable commit SHA and adds monthly grouped Dependabot updates to keep those pins current.
Confidence Score: 5/5
The PR appears safe to merge with no actionable defects identified.
The workflow changes preserve the existing action versions and valid
usessyntax, while the new Dependabot configuration covers the pinned actions with a valid grouped monthly update schedule.Important Files Changed
Reviews (1): Last reviewed commit: "Pin GitHub Actions to commit SHAs and ad..." | Re-trigger Greptile