go run not adhering to toolchain of go.mod when specifying package version

[wiegell]

Go version

1.22.4

Output of go env in your module/workspace:

GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/root/.cache/go-build'
GOENV='/root/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.2.linux-arm64'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local+auto'
GOTOOLDIR='/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.2.linux-arm64/pkg/tool/linux_arm64'
GOVCS=''
GOVERSION='go1.23.2'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/root/.config/go/telemetry'
GCCGO='gccgo'
GOARM64='v8.0'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/goproject/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3051749255=/tmp/go-build -gno-record-gcc-switches'

What did you do?

minimal repro repo (run execute_run_commands.sh):
https://github.com/wiegell/go-toolchain-repro

The local go version is 1.22.4, but github.com/99designs/gqlgen@v0.17.55 requires minimum 1.22.5. The local module is expecting 1.23.2 (in the local go.mod).
I am then using go run with a specific version of the package to run, like this: go run github.com/99designs/gqlgen@v0.17.55 generate.

What did you see happen?

When you do the above, you see the toolchain switch to go1.22.8.

What did you expect to see?

I would expect the version specific run command to adhere to the toolchain of the current module, like it does if i do the run command without a specific version: go run github.com/99designs/gqlgen generate (like this the toolchain will be go1.23.2)
Even though it's the same version of gqlgen being run, the toolchain differs.
You can see the difference by running the script in the repro repo.

Might be related to #69051

[gabyhelp]

Related Issues and Documentation

• cmd/go: GOTOOLCHAIN=version+auto doesn't use the named version in go install package@version #69051
• cmd/go: toolchain selection interacts unexpectedly with non-standard toolchains #63357 (closed)
• cmd/go: go toolchain version switch doesn't work when only language version is set in go.mod #65580 (closed)
• cmd/go: toolchain directive in go.mod being updated unnecessarily #65847
• cmd/go: go1.22 toolchain not available #65631 (closed)
• cmd/go: go get -u && go mod tidy behaves differently starting with Go 1.21.0, leading to unknown directive toolchain errors #62409 (closed)
• cmd/go: adjust `PATH` when `go run`/`go generate` runs the built binary #68005
• cmd/go: automatic toolchain upgrades make the combination of `go version` and `go install <package>@<version>` confusing #66518
• Go Toolchains > Go toolchain switches
• go mod edit: changing go versions in modules to invalid versions updates go.mod and causes weird problems #66491 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[seankhliao]

The @version syntax explicitly runs as outside the scope of the current module, so this is just #69051