You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within go module directory I am trying to go get package using @tag specifier:
go get -v github.com/asaskevich/govalidator@v11
This repository has tag v11 but it does not have v11.X.Y tags which go requires to use as version since part after v isn't semver.
What did you expect to see?
go get: added github.com/asaskevich/govalidator v0.0.0-pseudo-tag-that-corresponds-to-v11-tag
Since v11 is a valid tag and not semver-compliant version, it is expected to behave in same way as any other tag that owner might want to use.
Or, if go treats v11 as valid version it should import package as github.com/asaskevich/govalidator/v11 despite v11 being invalid semver identifier.
What did you see instead?
go get github.com/asaskevich/govalidator@v11: no matching versions for query "v11"
The text was updated successfully, but these errors were encountered:
Note that branches and tags with names matched by other version queries cannot be selected this way. For example, the query v2 selects the latest version starting with v2, not the branch named v2.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Within go module directory I am trying to
go get
package using@tag
specifier:This repository has tag
v11
but it does not havev11.X.Y
tags which go requires to use as version since part afterv
isn't semver.What did you expect to see?
Since
v11
is a valid tag and not semver-compliant version, it is expected to behave in same way as any other tag that owner might want to use.Or, if go treats
v11
as valid version it should import package asgithub.com/asaskevich/govalidator/v11
despitev11
being invalid semver identifier.What did you see instead?
The text was updated successfully, but these errors were encountered: