| commit | afe80cfef620e1ab15b5ad9f9152ff6f7f3611d5 | [log] [tgz] |
|---|---|---|
| author | Russ Cox <rsc@golang.org> | Wed Apr 18 00:59:56 2018 -0400 |
| committer | Russ Cox <rsc@golang.org> | Wed Apr 25 01:41:17 2018 +0000 |
| tree | e01003a433097f80fdb64dc8e7f681245309326d | |
| parent | 77e0cc2a6645a7ff4825940bae8d88d881a82839 [diff] |
cmd/go/internal/modfetch: avoid using non-canonical semver tags We insist that semver tags in repos be fully spelled out, as required by semver: v1.2.0, not v1.2. In other places, like go.mod, we do allow saying v1.2 as shorthand for v1.2.0. Don't confuse the issue by reporting a "v1.2" tag in the version list, since it's unaddressable. (If you type v1.2 vgo will look for v1.2.0.) Similarly, don't report tags that don't match the module path, and don't report tags that look like pseudo-versions. Additional fix for golang/go#23954, golang/go#24476. Change-Id: Iaac0fb36362b25e5faef5271c110d432ec04bc8b Reviewed-on: https://go-review.googlesource.com/107659 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
This repository holds a prototype of what the go command might look like with integrated support for package versioning.
See research.swtch.com/vgo for documents about the design.
Use go get -u golang.org/x/vgo.
You can also manually git clone the repository to $GOPATH/src/golang.org/x/vgo.
See CONTRIBUTING.md.
This is still a very early prototype. You are likely to run into bugs. Please file bugs in the main Go issue tracker, golang.org/issue, and put the prefix x/vgo: in the issue title.
Thank you.