Skip to content

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

Open
TeoSlayer wants to merge 1 commit into
mainfrom
ci/go-1.27.3
Open

TeoSlayer wants to merge 1 commit into
mainfrom
ci/go-1.27.3

Conversation

@TeoSlayer

Copy link
Copy Markdown
Contributor

security.yml's govulncheck job scans with Go 1.27.3, the toolchain pilotprotocol's release builds cmd/updater with. go.mod's go line stays at 1.25.13.

On Go 1.27.3 there are no stdlib findings. Five findings in golang.org/x/net v0.58.0 remain; their fix (v0.60.0) declares go 1.26.0, so the job stays red until the go line moves.

This module has no release build of its own: the shipped updater is
pilotprotocol's cmd/updater, which that repo's release.yml builds with
Go 1.27.3 from ci/go-1.27.3 on. Scan with the same toolchain so stdlib
findings match what ships. go.mod's go line stays at 1.25.13 so
pilotprotocol can keep requiring this module.

On Go 1.27.3 the scan reports no stdlib findings, but five in
golang.org/x/net v0.58.0 (fixed in v0.60.0, which declares go 1.26.0),
so the job stays red until the go line can move.
@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!

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