doc/next: document buildtag changes

Fixes #64127

Change-Id: I1562953caa3b1b2bc5dd3b7692671e0f3d5d2b9b
Reviewed-on: https://go-review.googlesource.com/c/go/+/632355
Commit-Queue: Tim King <taking@google.com>
Reviewed-by: Alan Donovan <adonovan@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>

diff --git a/doc/next/3-tools.md b/doc/next/3-tools.md
index 33a4e682dca849f50019003772acf3cdaefbb077..d319299c63de19c170f9c2b7a5406874b5c9acd6 100644 (file)
--- a/doc/next/3-tools.md
+++ b/doc/next/3-tools.md
@@ -49,6 +49,13 @@ with no other arguments. Such calls are nearly always a mistake
 as the value of `s` may contain the `%` symbol; use `fmt.Print` instead.
 See [#60529](/issue/60529).
 
+<!-- go.dev/issue/64127 -->
+The existing `buildtag` analyzer now reports a diagnostic when
+there is an invalid Go [major version build constraint](/pkg/cmd/go#hdr-Build_constraints)
+within a `//go:build` directive. For example, `//go:build go1.23.1` refers to
+a point release; use `//go:build go1.23` instead.
+See [#64127](/issue/64127).
+
 <!-- go.dev/issue/66387 -->
 The existing `copylock` analyzer now reports a diagnostic when a
 variable declared in a 3-clause "for" loop such as