design/draft-workspace.md: add idea for pushing buildlist down to workspace mods
Change-Id: I40eea072e34ad8ab91a1361e0208f6c09cc509ea
Reviewed-on: https://go-review.googlesource.com/c/proposal/+/310469
Trust: Michael Matloob <matloob@golang.org>
Run-TryBot: Michael Matloob <matloob@golang.org>
Reviewed-by: Michael Matloob <matloob@golang.org>
diff --git a/design/draft-workspace.md b/design/draft-workspace.md
index 43a1463..9505e99 100644
--- a/design/draft-workspace.md
+++ b/design/draft-workspace.md
@@ -605,3 +605,13 @@
depend on new versions of the dependency modules. A tool built in the future can
use the current workspace as well as the set of dependencies in the module graph
to automate this work.
+
+### Pushing down dependencies from the build list back to the workspace modules
+
+Even though it's out of scope to update the dependencies between workspace
+modules because that requires a release, it might be useful to make dependency
+versions consistent. One idea could be to push the module versions of dependency
+modules back into the go.mod files of the dependency modules. But this could
+lead to confusion because while the dependency versions will be consistent, the
+dependencies between the workspace modules will still need to be updated
+separately.
