From: Ian Lance Taylor <iant@golang.org>
Date: Wed, 27 Feb 2019 22:13:55 +0000 (-0800)
Subject: [release-branch.go1.12] doc/go1.12: new go line in go.mod can break builds with Go... 
X-Git-Tag: go1.12.1~12
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=7e880151b1763ebe608d7c2cadf36b71f184332a;p=gostls13.git

[release-branch.go1.12] doc/go1.12: new go line in go.mod can break builds with Go 1.11 - 1.11.3

Updates #30446

Change-Id: If069f72fa9735f839df92f3ede3bf7b6d7a695a5
Reviewed-on: https://go-review.googlesource.com/c/164317
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Reviewed-by: Bryan C. Mills <bcmills@google.com>
(cherry picked from commit e32203f647370897c6a28018c16cfd9584849569)
Reviewed-on: https://go-review.googlesource.com/c/go/+/164318
---

diff --git a/doc/go1.12.html b/doc/go1.12.html
index fbd59e3df2..2945eb1c43 100644
--- a/doc/go1.12.html
+++ b/doc/go1.12.html
@@ -185,6 +185,17 @@ tour
   that build fails.
 </p>
 
+<p><!-- CL 147282, 147281 -->
+  This changed use of the <code>go</code> directive means that if you
+  use Go 1.12 to build a module, thus recording <code>go 1.12</code>
+  in the <code>go.mod</code> file, you will get an error when
+  attempting to build the same module with Go 1.11 through Go 1.11.3.
+  Go 1.11.4 or later will work fine, as will releases older than Go 1.11.
+  If you must use Go 1.11 through 1.11.3, you can avoid the problem by
+  setting the language version to 1.11, using the Go 1.12 go tool,
+  via <code>go mod edit -go=1.11</code>.
+</p>
+
 <p><!-- CL 152739 -->
   When an import cannot be resolved using the active modules,
   the <code>go</code> command will now try to use the modules mentioned in the