chore: pin third-party GitHub Actions to commit SHAs#18
Merged
kinyoklion merged 3 commits intomainfrom Mar 30, 2026
Merged
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.
Co-Authored-By: rlamb@launchdarkly.com <4955475+kinyoklion@users.noreply.github.com>
Contributor
Version verification for pinned SHAs
|
Member
|
Devin, go ahead and update ruby/setup-ruby to 1.299.0, update the SHA and the comment. |
Co-Authored-By: rlamb@launchdarkly.com <4955475+kinyoklion@users.noreply.github.com>
kinyoklion
approved these changes
Mar 30, 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
2 participants
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.Updates since initial revision
# v4.4.0instead of# v4)ruby/setup-rubybumped from v1.295.0 (319994f...) to v1.299.0 (3ff19f5e2baf30647122352b96108b1fbe250c64), the latest v1 releasegoogleapis/release-please-actionconfirmed at v4.4.0 (16a9c90856f42705d54a6fda1823352bdc62cf38), already the latest v4 releaseRelease links for verification:
Review & Testing Checklist for Human
ruby/setup-rubyv1.299.0 (bumped from v1.295.0)Notes
slsa-framework/slsa-github-generatorreference on line 61 ofrelease-please.ymlremains at@v2.0.0(floating tag) — this action cannot be pinned to a commit SHA.Note
Low Risk
Low risk: changes only pin GitHub Action references to specific commits, with no functional logic changes beyond potential action version drift if the pinned SHAs differ from the floating tags.
Overview
Pins third-party GitHub Actions to immutable commit SHAs to harden CI/release workflows against supply-chain tampering.
Updates
ruby/setup-ruby@v1usages (composite CI action, Windows CI job, and docs publish workflow) to a specific commit SHA, and similarly pinsgoogleapis/release-please-action@v4in the release workflow to a specificv4.4.0commit.Written by Cursor Bugbot for commit 12e5cd3. This will update automatically on new commits. Configure here.
Link to Devin session: https://app.devin.ai/sessions/56bd3c6eff084ef4802aaa48b08ebab6
Requested by: @kinyoklion