Skip to content

ci: make go-cve gate blocking (remove continue-on-error) - #84

Merged
gnanirahulnutakki merged 1 commit into
devfrom
chore/cve-gate-blocking
Jul 1, 2026
Merged

ci: make go-cve gate blocking (remove continue-on-error)#84
gnanirahulnutakki merged 1 commit into
devfrom
chore/cve-gate-blocking

Conversation

@gnanirahulnutakki

Copy link
Copy Markdown
Member

Summary

  • Remove continue-on-error: true from the go-cve job so govulncheck ./... is a hard gate on PRs to main/dev.

Why now

go/go.mod was already bumped to go 1.26.4 and golang.org/x/net v0.55.0 in 51133b4. Running govulncheck ./... under Go 1.26.4 (matching CI setup-go) reports 0 reachable vulnerabilities — the 19 stdlib CVEs previously found were all in go1.25.4 stdlib (fixed by ≤ go1.25.11, included in go1.26.4). The gate is now safe to harden.

Verification

govulncheck ./...  → No vulnerabilities found (0 reachable)
go test -count=1 ./...  → 13/13 packages ok
go vet ./...            → exit 0

All run under Go 1.26.4.

govulncheck ./... is clean under Go 1.26.4 (0 reachable vulnerabilities;
19 stdlib CVEs were in go1.25.4 stdlib, all fixed by ≥go1.25.11 and
included in go1.26.4 which is already pinned in go/go.mod since 51133b4).

Remove continue-on-error: true from go-cve so the scan is now a hard
gate on all PRs to main/dev. go test ./... and go vet ./... remain green
under Go 1.26.4.
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