Google Git
Sign in
go / mod / 273ef6c30f77718d9c04e38b791a0913f652b9c9
commit273ef6c30f77718d9c04e38b791a0913f652b9c9[log] [tgz]
authorDmitri Shuralyov <dmitshur@golang.org>Wed Sep 06 08:08:20 2023 -0400
committerGopher Robot <gobot@golang.org>Wed Sep 06 16:08:47 2023 +0000
treee8a7ddfe29170d9b1678a7fbcaf81253b5bd44b2
parentbaa5c2d058db25484c20d76985ba394e73176132 [diff]
go.mod: update to go 1.18 and x/tools v0.13.0

Done with:

go get go@1.18 golang.org/x/tools@upgrade
go mod tidy

Using go1.21.0.

Change-Id: I6376b8ea06832ecddb5989538af1b2b663f62cfd
Reviewed-on: https://go-review.googlesource.com/c/mod/+/525977
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Bryan Mills <bcmills@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
2 files changed
tree: e8a7ddfe29170d9b1678a7fbcaf81253b5bd44b2
  1. gosumcheck/
  2. internal/
  3. modfile/
  4. module/
  5. semver/
  6. sumdb/
  7. zip/
  8. codereview.cfg
  9. go.mod
  10. go.sum
  11. LICENSE
  12. PATENTS
  13. README.md
README.md

mod

PkgGoDev

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.