You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updated my go.mod go line to go1.22 and ran go test.
What did you see happen?
go: downloading go1.22 (darwin/arm64)
go: download go1.22 for darwin/arm64: toolchain not available
What did you expect to see?
Go 1.22.0 being downloaded.
I know go1.22 is not a toolchain now that we renamed that to go1.22.0, but when I set the go line I am not thinking primarily of toolchain versions, but of the Go 1.22 semantics, and I am happy for the latest version of Go 1.22 to be downloaded.
Looks like there's been a lot of confusion around this in the past dependabot/dependabot-core#7895 and some projects disabled auto toolchains to support go.mod files with "short" go versions.
If the behavior shouldn't be changed, at least the error can be more useful, suggesting changing the go line to include a patch version.
The text was updated successfully, but these errors were encountered:
FiloSottile
changed the title
import/path: issue title
cmd/go: go1.22 toolchain not available
Feb 9, 2024
Go version
go version go1.21.5 darwin/arm64
Output of
go env
in your module/workspace:What did you do?
Updated my go.mod
go
line togo1.22
and rango test
.What did you see happen?
What did you expect to see?
Go 1.22.0 being downloaded.
I know go1.22 is not a toolchain now that we renamed that to go1.22.0, but when I set the
go
line I am not thinking primarily of toolchain versions, but of the Go 1.22 semantics, and I am happy for the latest version of Go 1.22 to be downloaded.Looks like there's been a lot of confusion around this in the past dependabot/dependabot-core#7895 and some projects disabled auto toolchains to support go.mod files with "short"
go
versions.If the behavior shouldn't be changed, at least the error can be more useful, suggesting changing the
go
line to include a patch version.The text was updated successfully, but these errors were encountered: