Tighten up Go version specification about setup-go

[ncw]

I've just been bitten by this too. Working out that the go release tagged 'go1.15beta1' needs go-version: 'v1.15.0-beta1' is non trivial!

[mvdan]

Note that v3.0.0 has now dropped the stable input, so betas and RCs work by default. They have also switched to a slightly more consistent form of semver for the version strings. See #191.

I still think it would be good to support Go versions as named by upstream, but at least now the behavior is more consistent.

[myitcv]

One further observation, Go modules refer to versions as follows: v1.14.0-beta1. Note the v prefix. Updated the semver-like section of my previous comment to use the v prefix instead of go.

In a similar vein I just made this suggestion: golang/go#32450 (comment)

[Sergey-Murtazin]

Hi @myitcv ! Sorry for the late response!
Could you please clarify if the issue is still actual for you?
Thanks!

[myitcv]

@Sergey-Murtazin

Could you please clarify if the issue is still actual for you?

Yes, it remains an issue just as described in the original description.

[dsame]

Hello @myitcv , maybe it is better to use go prefix as an indicator of go versioning instead of adding special prefix to indicate semver versioning? This way we can keep backward compatibility.