Skip to content

Upgrade Go to 1.26 to fix govulncheck - #24

Merged
TheoBen880 merged 1 commit into
mainfrom
ci/go-1.26
Oct 21, 2026
Merged

TheoBen880 merged 1 commit into
mainfrom
ci/go-1.26

Conversation

@TheoBen880

Copy link
Copy Markdown
Contributor

This PR makes the Security workflow pass again. The govulncheck job fails on main because Go 1.25 has known vulnerabilities in the standard library, and the fixes are only in Go 1.26.9 and later.

Before and after

Before: CI uses Go 1.25 (go1.25.14). govulncheck finds 9 standard library vulnerabilities and the job fails with exit code 3.

After: CI, the Security workflow, and the Docker image use Go 1.26 (go1.26.10 today). govulncheck exits with code 0.

Risk

CI and the Docker image now build with Go 1.26. The minimum Go version in go.mod does not change. Reverting this PR fully undoes it.

Evidence

govulncheck@v1.7.0 ./... on go1.26.10, the same command that CI runs:

No vulnerabilities found.
exit: 0

I did not run the test suite locally. The CI checks on this PR will show it.

What changed

Bug fixes:

  • CI, the Security workflow, and the Docker image use Go 1.26 instead of Go 1.25.

Checklist

  • Change all Go 1.25 pins to 1.26
  • Run govulncheck on go1.26.10
  • CI checks pass on this PR

@TheoBen880
TheoBen880 merged commit a91d0b6 into main Oct 21, 2026
4 checks passed
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