Repository navigation
Replies: 1 comment 1 reply
|
You're right: the warning's advice can't be followed when the #14308 makes mise read it the same way. An exact Until it's released, AI-assisted — Tool: Claude Code; model: anthropic/claude-opus-5-5; version: 2.1.295. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The deprecation warning says: "Add a toolchain goX.Y.Z line to go.mod, or set the version in .go-version or mise.toml. This will be removed in mise 2026.11.0."
But when the toolchain version equals the go directive (e.g. go 1.27.1 + toolchain go1.27.1), go mod tidy deletes the toolchain line (see golang/go#75331 open as a proposal
So following the warning's advice produces a go.mod that tidy rewrites, and go mod tidy CI checks fail. Repos that want the build version to be the exact patch release can't satisfy both.
Repro: set go 1.27.1 and toolchain go1.27.1, run go mod tidy, and the toolchain line is gone. mise then emits the deprecation warning again.
A workaround is using a later toolchain.
I previously had
but a library required 1.27.1, which bumped the minimum version, and then the toolchain matched.
Ideally, the upstream go#75331 gets resolved, but do you have any proposed workarounds, or is anything acceptable to use the go directive without a toolchain?
All reactions