tree 312978fa63efe77545c2f8b95d87f6a0bc859fff
parent 863d85c99c4d3c3c1f6f47564d9472fd4c5b4782
author Dmitri Shuralyov <dmitshur@golang.org> 1749847118 -0400
committer Gopher Robot <gobot@golang.org> 1750801920 -0700

internal/task: extend best-effort updating to nested modules (part 2 of 2)

The previous CL made it so that both root and nested modules are treated
the same way when they're the targets being updated. That is, if some
module requires golang.org/x/exp and golang.org/x/exp/event, and we're
willing to do "go get golang.org/x/exp@upgrade", there's no good reason
not to also be willing to do "go get golang.org/x/exp/event@upgrade".

This CL makes it so that both root and nested modules are treated the
same way when they're the source modules being updated. That is, if
we're willing to cd into the root module and run go get + go mod tidy,
then we can be willing to cd into nested modules and do analogous work
there too.

There may be replace directives, so do it in two passes. In pass one,
do 'go get' in the root and nested modules. In pass two, after we're
done running 'go get', do 'go mod tidy' in the root and nested modules.

Tagging nested modules is entirely different and not in scope for now.

For golang/go#73264.

Change-Id: I302304ede17f4abe755f692784a00c981f327572
Reviewed-on: https://go-review.googlesource.com/c/build/+/681439
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>
Reviewed-by: Alan Donovan <adonovan@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>