ci: pin all GitHub Actions to full-length commit SHAs#362
Open
SvenPistre wants to merge 2 commits into
Open
Conversation
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.
PR content
This PR pins every third-party GitHub Action used across the workflows to a full-length commit SHA, with a trailing
# <version>comment for readability and Dependabot compatibility. No behavioural change — each SHA corresponds to the release already in use.It also updates
.github/dependabot.ymlso SHA-pinned actions stay current and adds a cooldown period of 7 days.Previously all patch-level updates for
github-actionswere ignored but with SHA pinning this is actually counterproductive.Security fixes will frequently ship as a patch release. To reduce update noise, one can group all GitHub Action updates together in one PR once a week.
This resolves #361 (the repo settings can only be edited by maintainers)
How the SHAs can be verified
Each pin maps a SHA to a published release tag. To verify, open the release link and confirm GitHub shows the same commit SHA the comment claims; the
# vX.Y.Zcomment must match the linked release.actions/checkout34e114876b0b11c390a56381ad16ebd13914f8d5actions/checkout9f698171ed81b15d1823a05fc7211befd50c8ae0actions/upload-artifactb7c566a772e6b6bfb58ed0dc250532a479d7789factions/download-artifact37930b1c2abaa49bbe596cd826c3c89aef350131docker/setup-buildx-action8d2750c68a42422c14e847fe6c8ac0403b4cbd6fdocker/login-actionc94ce9fb468520275223c153574b00df6fe4bcc9docker/setup-qemu-actionc7c53464625b32c7a7e944ae62b3e17d2b600130dtolnay/rust-toolchainstable)e97e2d8cc328f1b50210efc529dca0028893a2d9taiki-e/install-action0631aa6515c7d545823c67cfae7ef4fc7f490154rustsec/audit-check69366f33c96575abad1ee0dba8212993eecbe998release-plz/action4a08fbe6cb1bb0e4d066058e6efcf50f352db236