$ go1.13beta1 get github.com/kubedb/apimachinery@v0.11.0
go: finding github.com/kubedb/apimachinery v0.11.0
go: finding github.com/kubedb/apimachinery v0.11.0
go: finding github.com v0.11.0
go: finding github.com/kubedb v0.11.0
go get github.com/kubedb/apimachinery@v0.11.0: unknown revision v0.11.0
$ go1.13beta1 get github.com/kubedb/apimachinery@0.11.0
go: finding github.com/kubedb/apimachinery 0.11.0
We use the git tag also as the Docker image tag. I like kubedb/operator:1.0.0 (without v) over kubedb/operator:v1.0.0. So, we went with that. Tools like glide, dep will automatically handle the presence or absence of v. But go mod does not do that.
What did you expect to see?
My question is can go mod automatically search for both of these prefixes?
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?
We use the git tag also as the Docker image tag. I like
kubedb/operator:1.0.0
(without v) overkubedb/operator:v1.0.0
. So, we went with that. Tools likeglide
,dep
will automatically handle the presence or absence ofv
. Butgo mod
does not do that.What did you expect to see?
My question is can
go mod
automatically search for both of these prefixes?What did you see instead?