Pin GitHub Actions to full-length commit SHAs

[Dan Fiedler (danfiedler-msft)]

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

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[David Levy (dlevy-msft-sql)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[Copilot]

Pull request overview

This PR hardens the repository’s CI/CD supply chain by pinning GitHub Actions references to full-length commit SHAs (improving reproducibility and reducing tag-retargeting risk) and by enabling Dependabot updates for GitHub Actions with a 7-day cooldown.

Changes:

• Pinned third-party GitHub Actions in existing workflows to full-length commit SHAs with version annotations.
• Pinned the third-party action used by the local composite action .github/actions/post-coverage-comment.
• Added .github/dependabot.yml to manage GitHub Actions updates with a weekly schedule and a 7-day cooldown.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
.github/workflows/pr-code-coverage.yml	Pins actions/checkout and actions/upload-artifact to full SHAs for safer PR coverage workflow execution.
.github/workflows/forked-pr-coverage.yml	Pins actions/checkout to a full SHA for forked PR coverage workflow safety.
.github/workflows/devskim.yml	Pins actions/checkout, microsoft/DevSkim-Action, and github/codeql-action/upload-sarif to full SHAs for deterministic security scanning.
.github/workflows/codeql-analysis.yml	Pins CodeQL workflow actions (checkout, init, autobuild, analyze) to full SHAs for reproducible scanning.
.github/dependabot.yml	Adds Dependabot configuration to update GitHub Actions on a weekly cadence with a 7-day cooldown.
.github/actions/post-coverage-comment/action.yml	Pins marocchino/sticky-pull-request-comment to a full SHA for safer composite action execution.

---

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