Skip to content

ci(validate): pin govulncheck to an immutable commit - #449

Merged
joshua-temple merged 1 commit into
mainfrom
ci/pin-govulncheck-commit
Jul 5, 2026
Merged

joshua-temple merged 1 commit into
mainfrom
ci/pin-govulncheck-commit

Conversation

@joshua-temple

Copy link
Copy Markdown
Collaborator

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.0 comment 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.

Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
@joshua-temple
joshua-temple merged commit 0326150 into main Jul 5, 2026
15 checks passed
@joshua-temple
joshua-temple deleted the ci/pin-govulncheck-commit branch July 5, 2026 01:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant