chore: capture and use image digest in Dockerfile#139
Merged
Conversation
Member
|
great contribution, thank you |
joemiller
approved these changes
Jun 9, 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
2 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.
If you pin the GitHub Action workflow to a sha, for example, '57a6c787385af407a557374c794a09273aaebfd7', there is still an opportunity for a supplychain attack via the Dockerfile, as it is pinned to a mutable image tag rather than a digest.
With this update, the image digest is captured and reused in the Dockerfile rather than the image tag, thus ensuring that if you pin this workflow to a specific sha then the docker image can't change without updating the action.