Using go-version: 1.20 breaks the build

[metalim]

Description:
Using go-version: 1.20 breaks the build, as it uses Go 1.2 instead of 1.20

Action version:
v3 and v4

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:
1.20

Repro steps:

• Create Go project with go.mod in it, with proper module name (in my case: github.com/metalim/gotest)
• Add test file that imports that module
• Confirm that go test ./... passes locally
• Setup GH action with Go template
• Change go-version for setup-go from 1.19 to 1.20
• Observe build failing. Example: https://github.com/metalim/gotest/actions

Expected behavior:
Should use Go 1.20 or 1.20.4

Actual behavior:
Uses Go 1.2

[metalim]

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

[marko-zivic-93]

Hello @metalim
Thank you for the heads up! We will investigate this issue and come back to you as soon as we have some results. 🙂

[nfuden]

A workaround is to use the go-version-file option as 1.20 will work in that setup

[gaby]

Fixed via #382

[dmitry-shibanov]

Hello everyone. I'm going to close the pull request because we added a note in scope of this pull request: #382

[metalim]

That might not help, and close was too early.
The cause of this issue originates from template provided by github, when you select template for Go Action:

README is not available at that point, but value already has incorrect format.
Requesting re-open