ci: pin workflow actions to commit SHAs (PROT-39)#3
Merged
Conversation
Pin actions/checkout (v4), actions/setup-dotnet (v5), and googleapis/release-please-action (v4) to immutable commit SHAs with version comments, closing the supply-chain risk of a moving tag being repointed on this public repo. Majors are unchanged; newer majors (checkout v6, release-please v5) are deferred as a separate evaluation. Refs: PROT-39 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ljones491
approved these changes
Jun 1, 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
Supply-chain hardening for the public repo: pin every action in
.github/workflows/release-please.ymlto a full commit SHA (with a version comment) instead of a moving tag. A tag like@v4can be repointed at any time; a SHA is immutable, so the workflow always runs the exact code we reviewed.Jira: PROT-39
Changes
googleapis/release-please-action@v4@5c625bf…# v4actions/checkout@v4@34e1148…# v4actions/setup-dotnet@v5@9a946fd…# v5Majors are intentionally unchanged. Newer majors exist (
actions/checkoutv6,release-please-actionv5); upgrading those is deferred to a separate, deliberate change so an untested major bump isn't bundled into a security pin.Why this is the right hardening here
The repo is public and the release-please workflow runs with
contents/issues/pull-requestswrite. Pinning to SHAs is the standard mitigation and pairs with thedefault_workflow_permissions: readbaseline already in place.Side effect (intended)
Merging this to
mainre-triggers therelease-pleaseworkflow. Now that "Allow GitHub Actions to create and approve pull requests" is enabled, that run should finally open the 0.1.0 Release PR that the previous run couldn't create.🤖 Generated with Claude Code