Pin GitHub Actions to full-length commit SHAs

[jawelton74]

Preview this branch

NOTE This PR cherry-picks the changes from this PR as a branch from this repo so that the checks can access secrets. Below is the description from that PR:

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@ # 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

[github-actions]

Playwright tests ❌ failed

Passed	Failed	Flaky	Duration
675	2	10	898s

📁 Report: 33417107697-1/report.zip
Open container (Azure sign-in required) → click into 33417107697-1 folder → click report.zip → Download → unzip → open index.html · Workflow run

⚠️ 2 shard(s) failed before tests ran (infra/auth issue). Stats below reflect only shards that executed.

[github-actions]

Playwright tests ✅ passed

Passed	Failed	Flaky	Duration
64	0	2	489s

📁 Report: 33417107697-2/report.zip
Open container (Azure sign-in required) → click into 33417107697-2 folder → click report.zip → Download → unzip → open index.html · Workflow run

[Mike Krüger (mkrueger)]

CosmosDB Shell has a similiar PR. And for security reasons it's important to pin these actions.