chore: pin third-party GitHub Actions to commit SHAs#411
Open
chore: pin third-party GitHub Actions to commit SHAs#411
Conversation
Pin all third-party GitHub Actions to full-length commit SHAs to prevent supply chain attacks. Addresses findings from the third-party-action-not-pinned-to-commit-sha Semgrep rule.
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
1 participant
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
Pin all third-party GitHub Actions to full-length commit SHAs to prevent supply chain attacks.
Addresses findings from the
third-party-action-not-pinned-to-commit-shaSemgrep rule.Test plan
Note
Low Risk
Low risk: workflow-only changes that pin existing third-party actions to specific SHAs, with no functional logic changes beyond how actions are referenced.
Overview
Pins several third-party GitHub Actions in
manual-publish.ymlandrelease-please.ymlfrom floating tags (e.g.release/v1,v2.0.0,v4) to specific commit SHAs.This affects release automation steps for
release-please, PyPI publishing, and SLSA provenance generation, improving supply-chain security by making builds reproducible and resistant to upstream tag changes.Written by Cursor Bugbot for commit 5dfd1e6. This will update automatically on new commits. Configure here.