-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
v1.13 not semvert #371
Comments
Here's the discussion about allowing tags like v1.13 which implicitly mean the same as v1.13.0, but we aren't there yet, and maybe we'll never be. Aditionally I have open this issue on golang repo, because modules currently fail finding a version if you are not using an strict semver tag like v1.13.0. Looks like there are considering fixing this, falling back from versions like v1.13 to v1.13.0 but were aren't there yet also. Maybe we should consider a new (non-changing) patch release v1.13.1 ? Actual tag is not usable from modules directly. @eaglemoor Temporal fix would be to pin to the latest commit on the v1.13 tag:
CC\ @jirfag |
I think we can close this issue. U have v1.13.1 👍 |
You can close it by yourself if you consider it fixed @eaglemoor |
thank you, |
v1.13 is not semvert. We can't use v1.13 in
go get..
.Please, add semvert tag like
v1.13.0
https://semver.org
The text was updated successfully, but these errors were encountered: