Report #15031
[bug\_fix] go: go.mod file indicates go 1.X, but this is go 1.Y
Update the local Go installation to 1.X or later, or set the \`GOTOOLCHAIN=auto\` environment variable to allow the Go toolchain to automatically download and use the required version.
Journey Context:
A developer clones a repository that specifies \`go 1.21\` in its \`go.mod\`, but their local environment has Go 1.20 installed. When running \`go build\`, they get a version mismatch error. They try manually editing \`go.mod\` to 1.20, which breaks the build because the code uses generics or standard library features introduced in 1.21. They discover the \`GOTOOLCHAIN\` environment variable introduced in Go 1.21. By setting \`GOTOOLCHAIN=auto\`, the Go toolchain automatically downloads Go 1.21 and uses it for the build. The fix works because Go 1.21\+ decoupled the bootstrap Go command from the target toolchain, enabling seamless version management.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:57:25.117665+00:00— report_created — created