Pin GitHub Actions to full-length commit SHAs - #1482
Pin GitHub Actions to full-length commit SHAs#1482Dan Fiedler (danfiedler-msft) wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Pull request overview
This PR hardens the repository’s dependency update and CI configuration by (1) ensuring GitHub Actions are referenced by immutable commit SHAs (with accurate version annotations) and (2) configuring Dependabot to manage GitHub Actions updates with a 7‑day cooldown to reduce exposure to newly published compromised releases.
Changes:
- Updated a workflow action reference comment to accurately reflect the pinned
actions/create-github-app-tokenversion. - Added a
github-actionsDependabot update entry, including grouping and a 7‑daycooldown.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/update-release-branch.yml | Keeps the action pinned by SHA and corrects the version comment for clarity/reproducibility. |
| .github/dependabot.yml | Adds Dependabot support for GitHub Actions updates with grouping and a 7‑day cooldown to improve supply-chain resilience. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
There was a problem hiding this comment.
Could you please also add the default cooldown for the other package-ecosystems as well?
There was a problem hiding this comment.
This only actually changes the version comment, not the pinned SHA. The PR description is misleading, as we were already pinning to full-length commit SHAs.
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.ymlhas been updated to ensure agithub-actionspackage-ecosystem section is present with acooldownconfiguration (default-days: 7). This groups Dependabot PRs for GitHub Actions and enforces a minimum 7-day cooldown between updates. If the file did not exist, it was created. If agithub-actionssection already existed, only thecooldownblock was added or itsdefault-daysvalue 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 are introduced. You can verify the pinned SHA value using the GitHub REST API (e.g., the commit hash for
actions/checkout@v7can be found in theshaproperty in the JSON response forGET https://api.github.com/repos/actions/checkout/commits/v7).Additional Information
For more information, please see https://aka.ms/action-pinning