-
Notifications
You must be signed in to change notification settings - Fork 526
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
Using go-version: 1.20
breaks the build
#380
Comments
As this was reported before, I suggest editing the Go template of GH action and using quoted version there, so it does not make confusion again. Just closing the issue as "dupe" is not productive action |
Hello @metalim |
A workaround is to use the go-version-file option as 1.20 will work in that setup |
Fixed via #382 |
Hello everyone. I'm going to close the pull request because we added a note in scope of this pull request: #382 |
Description:
Using
go-version: 1.20
breaks the build, as it uses Go 1.2 instead of 1.20Action version:
v3 and v4
Platform:
Runner type:
Tools version:
1.20
Repro steps:
go.mod
in it, with proper module name (in my case:github.com/metalim/gotest
)go test ./...
passes locallygo-version
forsetup-go
from 1.19 to 1.20Expected behavior:
Should use Go 1.20 or 1.20.4
Actual behavior:
Uses Go 1.2
The text was updated successfully, but these errors were encountered: