go.mod: ignore cyclic dependency for tagging

tools and mod have a cyclic dependency, which needs to be broken during
the upgrading/tagging process. This direction is due to the use of txtar
in the tests for the zip package, which is much less important than the
other direction.

For golang/go#48523.

Change-Id: Id5006280b0bc6b39f191b0281d542d251d80fff5
Reviewed-on: https://go-review.googlesource.com/c/mod/+/439335
Reviewed-by: Bryan Mills <bcmills@google.com>
Run-TryBot: Heschi Kreinick <heschi@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
1 file changed
tree: 0597ef29b70d44723e1fc50021771f5c002a64c7
  1. gosumcheck/
  2. internal/
  3. modfile/
  4. module/
  5. semver/
  6. sumdb/
  7. zip/
  8. codereview.cfg
  9. go.mod
  10. go.sum
  13. README.md



This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.

It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages.

The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.