Matthew Hughes 1d76b952eb Improve toolchain handling (#460) ... * Configure environment to avoid toolchain installs Force `go` to always use the local toolchain (i.e. the one the one that shipped with the go command being run) via setting the `GOTOOLCHAIN` environment variable to `local`[1]: > When GOTOOLCHAIN is set to local, the go command always runs the bundled Go toolchain. This is how things are setup in the official Docker images (e.g.[2], see also the discussion around that change[3]). The motivation behind this is to: * Reduce duplicate work: if the `toolchain` version in `go.mod` was greated than the `go` version, the version from the `go` directive would be installed, then Go would detect the `toolchain` version and additionally install that * Avoid Unexpected behaviour: if you specify this action runs with some Go version (e.g. `1.21.0`) but your go.mod contains a `toolchain` or `go` directive for a newer version (e.g. `1.22.0`) then, without any other configuration/environment setup, any go commands will be run using go `1.22.0` This will be a **breaking change** for some workflows. Given a `go.mod` like: module proj go 1.22.0 Then running any `go` command, e.g. `go mod tidy`, in an environment where only go versions before `1.22.0` were installed would previously trigger a toolchain download of Go `1.22.0` and that version being used to execute the command. With this change the above would error out with something like: > go: go.mod requires go >= 1.22.0 (running go 1.21.7; GOTOOLCHAIN=local) [1] https://go.dev/doc/toolchain#select [2] dae3405a32/Dockerfile-linux.template (L163) [3] https://github.com/docker-library/golang/issues/472 * Prefer installing version from `toolchain` directive Prefer this over the version from the `go` directive. Per the docs[1] > The toolchain line declares a suggested toolchain to use with the module or workspace It seems reasonable to use this, since running this action in a directory containing a `go.mod` (or `go.work`) suggests the user is wishing to work _with the module or workspace_. Link: https://go.dev/doc/toolchain#config [1] Issue: https://github.com/actions/setup-go/issues/457 * squash! Configure environment to avoid toolchain installs Only modify env if `GOTOOLCHAIN` is not set * squash! Prefer installing version from `toolchain` directive Avoid installing from `toolchain` if `GOTOOLCHAIN` is `local`, also better regex for matching toolchain directive		2025-08-28 22:21:56 -05:00
..
data	Fix versions check failure (#479)	2024-05-10 11:25:20 -05:00
cache-restore.test.ts	Add and configure ESLint and update configuration for Prettier (#341)	2023-03-08 10:45:16 +02:00
cache-utils.test.ts	Revise isGhes logic (#511)	2024-10-21 11:56:08 -05:00
setup-go.test.ts	Improve toolchain handling (#460)	2025-08-28 22:21:56 -05:00
utils.test.ts	Update self-hosted environment validation and bump undici version (#556)	2025-04-01 10:32:30 -05:00
verify-go.sh	Use GitHub releases to download Go versions. (#58)	2020-06-29 11:41:13 -04:00
windows-toolcache.test.ts	Fix Install on Windows is very slow (#393)	2023-08-03 14:33:56 +02:00