Repository navigation
ci: pin the security scanners and build with Go 1.26.10 - #41
Merged
Merged
Conversation
gosec v2.30.0, released 2026-10-23, turned lattice-server's pull requests red with findings in code v2.29.0 passed. Scanners here now move only when they are bumped on purpose: gosec at v2.29.0 where it runs, and govulncheck at v1.9.0. The vulnerability database is still fetched fresh on every run.
govulncheck reports GO-2026-6809 on 1.26.9: crypto/x509 gained a denylist of compromised intermediate certificates that Verify now rejects, and the agent reaches Verify through its HTTPS downloads. 1.26.10 carries the fix. The release workflow moves with CI so the next agent release is built with it.
lr00rl
changed the title
This was referenced Oct 24, 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
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.
Pins gosec at v2.29.0 and govulncheck at v1.9.0 instead of @latest (gosec v2.30.0 broke lattice-server CI overnight). With the scanners pinned, govulncheck reports GO-2026-6809 (crypto/x509 distrusts compromised intermediate certificates), fixed in Go 1.26.10, so CI and the release workflow move to 1.26.10. The next agent release is built with it; nothing is released here.
Test plan: CI on this PR; sh scripts/check-release-workflow.sh.