Skip to content
This repository was archived by the owner on Oct 15, 2026. It is now read-only.

Pin GitHub Actions to full-length commit SHAs - #370

Merged
Brandon Myers (bmyerz0) merged 2 commits into
microsoft:mainfrom
danfiedler-msft:danfiedler/pin-actions
Oct 15, 2026
Merged

Brandon Myers (bmyerz0) merged 2 commits into
microsoft:mainfrom
danfiedler-msft:danfiedler/pin-actions

Conversation

@danfiedler-msft

Copy link
Copy Markdown
Contributor

Summary

This PR pins GitHub Actions to full-length commit SHAs for improved security and reproducibility and adds a 7 day cooldown to Dependabot configuration for GitHub Actions. This work is described in more detail at https://aka.ms/action-pinning.

Why?

Pinning actions to commit SHAs prevents supply-chain attacks where a tag could be moved to point to malicious code. This is a recommended security best practice per the GitHub Actions security hardening guide.

This change mitigates the risk of tag retargeting to malicious code as seen in incidents like the tj-actions/changed-files action compromise or codfish/semantic-release-action compromise and improves the integrity and reproducibility of the CI/CD pipeline.

What changed?

Action pinning: Third-party action references in .github/workflows/ that used mutable tag-based references (e.g., actions/checkout@v4) have been updated to full-length commit SHAs with a version comment (e.g., actions/checkout@<sha> # v4) using the pinact tool. References that were already pinned to a SHA, or that used immutable release tags, were left unchanged.

Dependabot configuration: .github/dependabot.yml has been updated to ensure a github-actions package-ecosystem section is present with a cooldown configuration (default-days: 7). If the file did not exist, it was created. If a github-actions section already existed, only the cooldown block was added or its default-days value was increased to 7 if it was lower. The 7-day cooldown provides a window for the community to detect and report compromised releases before they are automatically proposed as updates, reducing exposure to supply-chain attacks via newly published malicious versions.

Is this safe to merge?

Yes. The pinned SHAs correspond to the same commits that the existing tags pointed to. No behavioral changes in action execution are introduced. You can verify the pinned SHA value using the GitHub REST API (e.g., the commit hash for actions/checkout@v7 can be found in the sha property in the JSON response for GET https://api.github.com/repos/actions/checkout/commits/v7).

Additional Information

For more information, please see https://aka.ms/action-pinning

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The pins preserve the existing action versions, and no blocking issues were identified.

0 open findings

What changed in this PR

This PR hardens CI workflows by pinning GitHub Actions to full-length commit SHAs and configuring delayed dependency updates.

Changes:

  • Pin checkout and Python setup actions, retaining version comments.
  • Add grouped weekly Dependabot updates for GitHub Actions with a seven-day cooldown.
File Description
.github/​workflows/​test-plugin.yml Pin both checkout steps to a commit SHA.
.github/​workflows/​clang-format.yml Pin checkout and Python setup actions.
.github/​dependabot.yml Configure grouped weekly updates and a seven-day cooldown.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d2c264ba-031d-48b0-8cf9-1e9a54cc1fea
@bmyerz0
Brandon Myers (bmyerz0) enabled auto-merge (squash) October 15, 2026 18:43
@bmyerz0
Brandon Myers (bmyerz0) merged commit 11a803d into microsoft:main Oct 15, 2026
4 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants