Skip to content

ci: govulncheck scans with Go 1.27.3, the daemon release toolchain - #61

Merged
TeoSlayer merged 2 commits into
mainfrom
ci/go-1.27.3
Nov 9, 2026
Merged

TeoSlayer merged 2 commits into
mainfrom
ci/go-1.27.3

Conversation

@TeoSlayer

@TeoSlayer TeoSlayer commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

security.yml's govulncheck job scans with Go 1.27.3, the toolchain the daemon release builds with, using govulncheck v1.7.0 (the version pilotprotocol and updater pin; v1.1.4 cannot analyze Go 1.27's standard library). go.mod's go line stays at 1.25.13.

On Go 1.27.3 govulncheck reports no findings for this module (ten stdlib findings on 1.25.13).

common is a library with no release build of its own; it ships inside
the daemon, pilotctl and the registry. The registry is already built with
Go 1.27.3. The scan matches the daemon's release toolchain once the
daemon builds with 1.27.3 too (pilotprotocol release.yml, ci/go-1.27.3);
until that lands it is one step ahead of the shipped daemon.

On Go 1.25.13 govulncheck reports ten stdlib findings (GO-2026-6809 and
nine fixed in 1.26.9). On Go 1.27.3 it reports none, on main and on
fix/sign-network-role-ops (#60). go.mod's go line stays at 1.25.13.
@codecov

codecov Bot commented Nov 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

govulncheck v1.1.4 (golang.org/x/tools v0.29.0) panics on Go 1.27.3's
standard library on linux/amd64 ("unexpected expr: *ast.KeyValueExpr").
v1.7.0 is the version pilotprotocol and updater already pin; on Go 1.27.3
it reports no vulnerabilities for this module, on main and on
fix/sign-network-role-ops.
@TeoSlayer
TeoSlayer merged commit 23094fe into main Nov 9, 2026
11 checks passed
@TeoSlayer
TeoSlayer deleted the ci/go-1.27.3 branch November 9, 2026 00:56
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.

2 participants