You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently call analysis doesn't work for go projects with go version > 1.22.8, which is the go version of the latest osv-scanner-action image (v1.9.1).
When a new vulnerability is detected call analysis fails with:
Failed to run code analysis (govulncheck) on '/app/tools/src/buf/go.mod' because govulncheck: loading packages: err: exit status 1: stderr: go: go.mod requires go >= 1.23.3 (running go 1.22.8; GOTOOLCHAIN=local)
(the Go toolchain is required)
I suggest one of the following:
Release a new osv-scanner version and osv-scanner-action version when a new golang version is available. Currently there is an open PR with alpine based image update, which also updates go version to latest.
Add support in github action to install and run osv-scanner on machine instead of inside container, thus allowing the consumer to install go itself, similar to golangci-lint-action.
Can you please merge the PR for now and release a new version?
The text was updated successfully, but these errors were encountered:
Good idea to support using the host osv-scanner rather than fully relying on a containerised version. We'll release a new version of osv-scanner soon to fix the govulncheck issue as well.
Currently call analysis doesn't work for go projects with go version > 1.22.8, which is the go version of the latest
osv-scanner-action
image (v1.9.1).When a new vulnerability is detected call analysis fails with:
I suggest one of the following:
osv-scanner
on machine instead of inside container, thus allowing the consumer to install go itself, similar to golangci-lint-action.Can you please merge the PR for now and release a new version?
The text was updated successfully, but these errors were encountered: