ci: pin third-party actions (github-push-action, free-disk-space) to full commit SHAs - #9575
Merged
Merged
Conversation
Pin the third-party actions referenced by mutable @master/@main tags to their current commit SHA (tag kept in a trailing comment): - ad-m/github-push-action (auto_lang, beta_release, release) — passed secrets.MY_TOKEN - jlumbroso/free-disk-space (release) release.yml hands github-push-action a write-scoped token, so a moved tag there would run unreviewed code with it. Behaviour unchanged; per GitHub's guidance to pin actions to a full-length commit SHA. Signed-off-by: Kobi Hikri <kobi.hikri@gmail.com>
skysliences
approved these changes
Aug 5, 2026
okatu-loli
approved these changes
Aug 5, 2026
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
3 participants
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.
What
Pin the third-party actions referenced by
@master/@mainto their current commit SHA (tag kept in a comment):ad-m/github-push-action@masterauto_lang.yml,beta_release.yml,release.ymljlumbroso/free-disk-space@mainrelease.ymlWhy
@master/@mainare moving refs. Inrelease.yml,github-push-actionis passedsecrets.MY_TOKEN(a write-scoped token). If that action'smasterwere moved (compromise or anaccidental change), the new code would run with the token — the class of issue behind the 2025
tj-actions/changed-filesincident. Pinning to a SHA removes that.Scope / safety
Behaviour unchanged — each SHA is the current tip of that action's default branch. Only third-party
actions touched. Signed-off. Per GitHub's pin-to-SHA guidance.
AI-assisted; I verified the workflows, the token exposure, and the pinned SHAs myself.