ci(validate): pin govulncheck to an immutable commit - #449
Merged
Merged
Conversation
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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.
Problem
The vulnerability scan gate pins govulncheck by the v1.3.0 semver tag. This repo pins its GitHub Actions by immutable commit SHA so a supply chain input cannot change under a moved tag; the govulncheck pin should follow the same convention.
Fix
Pin both govulncheck invocations (root and e2e module) to the immutable commit that v1.3.0 points to, 0782b76014f15f24e22a438f30f308df42899ba1, keeping a
# v1.3.0comment for readability.Verification
The pinned commit resolves and runs locally (
go run golang.org/x/vuln/cmd/govulncheck@0782b76014f15f24e22a438f30f308df42899ba1 -version); actionlint clean on the changed workflow.