builder: suggest GOTOOLCHAIN and -go-compatibility when the host Go is too new - #5643
Open
0pcom wants to merge 1 commit into
Open
builder: suggest GOTOOLCHAIN and -go-compatibility when the host Go is too new#56430pcom wants to merge 1 commit into
0pcom wants to merge 1 commit into
Conversation
…s too new The window between a Go release and the TinyGo release that supports it is when most users hit the version gate, and the error gives no way forward. Both escape hatches already exist: GOTOOLCHAIN=go1.<max>.x makes the go command download and run a supported toolchain (TinyGo follows it transparently), and -go-compatibility=false skips the check. Mention them in the too-new case; the too-old case keeps the plain message.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The window between a Go release and the TinyGo release that supports it is when most users hit the version gate (for example go1.27 with TinyGo 0.41.x), and the error gives no way forward.
Both escape hatches already exist:
GOTOOLCHAIN=go1.<max>.xmakes the go command download and run a supported toolchain — TinyGo follows it transparently, verified withGOTOOLCHAIN=go1.26.0 tinygo versionreporting the switched toolchain — and-go-compatibility=false(v0.40.0, #5075) skips the check outright. This mentions both in the too-new case, so the gap between releases self-serves instead of requiring a Go downgrade. The too-old case keeps the plain message.Message-only change;
go build ./builderpasses.