commit | dc121ce20ffab6bb810a0f231cfa9c24d3e51b29 | [log] [tgz] |
---|---|---|
author | Gopher Robot <gobot@golang.org> | Fri Feb 14 21:11:45 2025 +0000 |
committer | Gopher Robot <gobot@golang.org> | Fri Feb 14 13:54:42 2025 -0800 |
tree | 39cb2441e2ac8409243927d3b040fb97d0611a98 | |
parent | 52289f1fa75a8da0eb82d369cf5fda65fd6147b9 [diff] |
all: upgrade go directive to at least 1.23.0 [generated] By now Go 1.24.0 has been released, and Go 1.22 is no longer supported per the Go Release Policy (https://go.dev/doc/devel/release#policy). For golang/go#69095. [git-generate] (cd . && go get go@1.23.0 && go mod tidy && go fix ./... && go mod edit -toolchain=none) Change-Id: Id57a8feb7635d63f320ed0076af5c29a580ce6eb Reviewed-on: https://go-review.googlesource.com/c/mod/+/649717 Auto-Submit: Gopher Robot <gobot@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Cherry Mui <cherryyz@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.