-
Notifications
You must be signed in to change notification settings - Fork 514
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
Document what happens when '.x' version is specified, such as '1.16.x' #115
Comments
if anyone knows what the difference is now, do tell! |
leaving out the patch version results in choosing the latest patch Ex. Setup go stable version spec 1.17
Found in cache @ C:\hostedtoolcache\windows\go\1.17.1\x64
Added go to the path
Successfully setup go version 1.17
go version go1.17.1 windows/amd64 |
Hi, @x448 ! The
|
Hi @Sergey-Murtazin, It's too easy for users to confuse 1.16 as "use default 1.16 installed" vs "download latest 1.16.x to replace default 1.16". Same confusion with 1.16.x. Adding a short example to docs would be a reasonable & easy solution. New users to GitHub won't be able to just try both 1.15 and 1.15.x to clear up the ambiguity because the default is Go 1.15.15 on ubuntu-latest and there' no newer 1.15.x available. And specifying 1.16 or 1.16.x both grab 1.16.10 even though 1.16.11 has been available for 4 days. Something like this clarification in the docs would be helpful to GitHub users:
|
Hi, @x448! Thanks for your proposal! |
Hello everyone. I'm going to close this issue because we add a note about SemVer in scope of this pull request. Besides, we're going to add check latest logic in scope of this pull request. |
Thanks for adding |
README.md should explain differences (if any) between specifying "1.16" vs "1.16.x".
Even if go-version documents this in the future, it would be user-friendly to document it (at least briefly) in setup-go.
The text was updated successfully, but these errors were encountered: