ci: pin GitHub Actions to full commit SHAs to prevent supply-chain attacks#464
Open
XananasX7 wants to merge 1 commit into
Open
ci: pin GitHub Actions to full commit SHAs to prevent supply-chain attacks#464XananasX7 wants to merge 1 commit into
XananasX7 wants to merge 1 commit into
Conversation
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.
Summary
Pins all GitHub Actions in
ci.yamlandrelease.yamlto full immutable commit SHAs instead of mutable version tags.Vulnerability
Using mutable tags (
@v3,@v4,@v5) means the action code can change at any time — a compromised action repository could silently deliver malicious code in CI. Therelease.yamlworkflow is especially sensitive as it publishes to PyPI usingsecrets.PYPI_API_TOKEN.Changes
ci.yamlactions/checkout@v4@34e1148ci.yamlastral-sh/setup-uv@v5@d4b2f3brelease.yamlactions/checkout@v3@f43a0e5release.yamlactions/setup-python@v3@3542bcaAll pins point to the exact same version as the current tags — no behaviour change.
References