security: Pin GitHub Actions to specific git revisions #16
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.
Summary
This change improves our supply chain security by pinning all third-party GitHub Actions to specific git revisions using ratchet.
Why this matters
When GitHub Actions are referenced by mutable tags like
@v3or@main, the actual code being executed can change without notice. This creates security risks:What changed
@{sha}) instead of mutable tagsmdsolorganization are preserved as-is (marked with# ratchet:exclude)ratchet:{action}@{version}ratchet updateto get the latest SHA that matches your version constraintDependabot Integration
This change also configures Dependabot to automatically create pull requests when new versions of GitHub Actions become available:
dependabot.ymlordependabot.yamlfile already exists, it's updated to include GitHub ActionsTesting
This change does not modify the behavior of the workflows, only pins them to specific revisions. Workflows will continue to function as before, but with improved security and reproducibility.
References