ci: pin free-disk-space to a full commit SHA - #848
Open
kobihikri wants to merge 1 commit into
Open
Conversation
build-push-docker.yaml runs jlumbroso/free-disk-space via the mutable @main branch as the first step of the build job, which holds packages:write + id-token:write and logs into ghcr.io with GITHUB_TOKEN before pushing images. Pin to v1.3.1's commit so the code that runs in that credentialed job is fixed. Behaviour unchanged.
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-spaceinbuild-push-docker.yamlfrom@mainto the v1.3.1 release commit.Why
It's the first step of the
buildjob, which holdspackages: write+id-token: write, logs into ghcr.io withGITHUB_TOKEN, and pushes the published container images.@mainis a moving branch, so the exact third-party code running alongside those credentials can change without any change here. Pinning to a full SHA closes that; behaviour unchanged.I used AI assistance to identify this and draft the change; I verified it against the live workflows myself.