Repository navigation
Pin GitHub Actions to full-length commit SHAs - #66
Closed
Dan Fiedler (danfiedler-msft) wants to merge 1 commit into
Closed
Dan Fiedler (danfiedler-msft) wants to merge 1 commit into
Dan Fiedler (danfiedler-msft) wants to merge 1 commit into
Conversation
Collaborator
|
superseded by #68 |
Melvin Wang (wmmc88)
added a commit
that referenced
this pull request
Nov 4, 2026
…68) Picks up @danfiedler-msft's action pinning from #66 and brings it in line with the follow-up work done in microsoft/windows-drivers-rs#745. Actions are refreshed to their latest releases, and the `dtolnay/rust-toolchain` steps that used `@stable`/`@nightly` now pass `toolchain` explicitly since a SHA pin no longer carries the toolchain in the ref. Dependabot now groups Cargo updates per dependency and batches minor/patch action bumps, with staggered weekly runs to match windows-drivers-rs. Also does a one-time Cargo refresh. `windows-sys` 0.61 moved `BOOL` to `windows_sys::core`, so `echoapp` needed a one-line import fix. Serde, clap, thiserror and prettyplease stay on their latest Syn 2 releases to avoid duplicate `syn` versions. Supersedes #66. --------- Co-authored-by: Dan Fiedler <danfiedler@microsoft.com>
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
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
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). 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 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@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