-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
govulncheck-action: support go-version-file: 'go.mod' #61343
Comments
cc @golang/vulndb |
Given #57001, for Go versions 1.21 and above |
This change allows support for go-version-file in this action so that consumers can reference a `go.mod` or `go.work` file rather than keeping their action in sync with their go tooling. As actions/setup-go has go-version overwrite go-version-file, this will do the same. If both are provided, the go-version-input is used. Fixes golang/go#61343
Change https://go.dev/cl/511615 mentions this issue: |
Change https://go.dev/cl/521735 mentions this issue: |
Is it possible to get a new release of the govulncheck-action so that it is possible to use this? |
Yes, we should have one really soon. |
In regards to the new golang-govulncheck-action Github action recently released, would it be possible to add support for
go-version-file: 'go.mod'
like the existingactions/setup-go
action so that govulncheck will always use the version of go as described in thego.mod
file?The main benefit here would be that go versions specified in the GitHub action workflow would not need to be regularly updated to stay in sync with the projects
go.mod
file.The text was updated successfully, but these errors were encountered: