tree f9c0f8a847e7951a37f379674cfbee6f76fc3d69
parent fa508ab9e94205f71790c8c0f7af65c1e677e480
author Dmitri Shuralyov <dmitshur@golang.org> 1729788583 -0400
committer Gopher Robot <gobot@golang.org> 1729808951 +0000

internal/task: read nested module's own go.mod files

As of the last change, it becomes easy to read the nested module's own
go.mod file and determine whether it had a toolchain directive. Before,
it was reusing the top-level go.mod file's decision for nested modules.

I didn't realize earlier there is a way to use the lower-level 'go mod
edit' command to drop a toolchain directive, but it turns out there is.
Switch to it now - it's equivalent but fits slightly better in context.

Fixes golang/go#68873.

Change-Id: I1ea4bfd9e5deb4e72843887d7f8d68a4b2a67f3e
Reviewed-on: https://go-review.googlesource.com/c/build/+/622396
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>