Open sbp-bvanb opened 1 month ago
Related Issues and Documentation
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
I am having same issue
reproduction:
I wanted to pass go-version-file
which is 1.23.2
in my go.mod project but the action assigned the go version as 1.23.3
Warning: Both go-version and go-version-file inputs are specified, only go-version will be used
govulncheck version
golang/govulncheck-action@v1.0.4
Does this issue reproduce at the latest version of golang.org/x/vuln?
Output of
go env
in your module/workspace:What did you do?
What did you see happen?
Warning: Both go-version and go-version-file inputs are specified, only go-version will be used
What did you expect to see?
No warning as
go-version-file: go.mod
has been defined. If this is the case, then the code should omit go-version and only use the version that is defined in the go.mod file. Now it is using another Golang version, while another version is defined in the go.mod file.