| commit | 3afcd4e90a74c23515a9543f1e8fb68f05ecc8e0 | [log] [tgz] |
|---|---|---|
| author | Michael Matloob <matloob@golang.org> | Thu Aug 15 12:31:23 2024 -0400 |
| committer | Michael Matloob <matloob@golang.org> | Thu Aug 15 19:21:00 2024 +0000 |
| tree | a533a4e58ca29c75524fcb938c3c46a5a634ed8d | |
| parent | b1d336cfca975f8b4b9c88e782fbe1911b2494b0 [diff] |
go.mod: set go version to 1.22.0 The go verison was set to 1.22 but on Go versions 1.21.0 up to 1.21.10, the toolchain upgrade logic will try to download the release "1.22", which doesn't exist. Go 1.21.11+ incorporates CL 580217 (cherry-picked in CL 583797) and will download 1.22.0, so it should be fine, but set 1.22.0 to allow the upgrade for users with older local toolchains. Change-Id: I9aafaaa389ded3200b15fd3e7bb676610fa958d8 Reviewed-on: https://go-review.googlesource.com/c/mod/+/605935 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Commit-Queue: Michael Matloob <matloob@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
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.