From 74d366f4844026494e777638caffaf94255166dc Mon Sep 17 00:00:00 2001 From: Jay Conrod Date: Mon, 27 Jan 2020 15:29:29 -0500 Subject: [PATCH] doc/go1.14: go command behavior with GO111MODULE=on outside modules Hopefully this won't affect many people, but it's a substantial change in behavior for a specific case, so it's probably worth mentioning. Updates #32027 Change-Id: I61cd50e93d0199e94b011cc90150e072b6bb10ca Reviewed-on: https://go-review.googlesource.com/c/go/+/216597 Run-TryBot: Jay Conrod Reviewed-by: Michael Matloob Reviewed-by: Bryan C. Mills TryBot-Result: Gobot Gobot --- doc/go1.14.html | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/doc/go1.14.html b/doc/go1.14.html index 245b068ce8..f5f0735741 100644 --- a/doc/go1.14.html +++ b/doc/go1.14.html @@ -217,6 +217,32 @@ TODO of GOINSECURE is a comma-separated list of glob patterns.

+

Commands outside modules

+ +

+ When module-aware mode is enabled explicitly (by setting + GO111MODULE=on), most module commands have more + limited functionality if no go.mod file is present. For + example, go build, + go run, and other build commands can only build + packages in the standard library and packages specified as .go + files on the command line. +

+ +

+ Previously, the go command would resolve each package path + to the latest version of a module but would not record the module path + or version. This resulted in slow, + non-reproducible builds. +

+ +

+ go get continues to work as before, as do + go mod download and + go list -m with explicit version + patterns. +

+

+incompatible versions

-- 2.52.0