ci: pin jlumbroso/free-disk-space to a full commit SHA#1389
Open
kobihikri wants to merge 1 commit into
Open
Conversation
docker-publish.yml references this third-party action by the mutable @main tag, in a job that logs in to the container registry and pushes images. The workflow already SHA-pins docker/login-action, so this brings free-disk-space in line. Pin it to the current main commit SHA (tag kept in a trailing comment). Behaviour unchanged; per GitHub's guidance to pin actions to a full-length commit SHA. Signed-off-by: Kobi Hikri <kobi.hikri@gmail.com>
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
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
1 participant
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
jlumbroso/free-disk-space@main→54081f1…indocker-publish.yml(tag kept in a trailing comment).Why
@mainis a moving reference. This use is in the docker-publish job, which logs in to the containerregistry (
GITHUB_TOKEN) and pushes images. The workflow already SHA-pinsdocker/login-action, sothis just brings
free-disk-spacein line. If the action'smainwere moved (compromise or anaccidental change), the new code would run in the push job — the class of issue behind the 2025
tj-actions/changed-filesincident.Scope / safety
main. Signed-off.Per GitHub's guidance to pin actions to a full-length commit SHA.
AI-assisted; I verified the workflow and the pinned SHA myself.