Pin the v3 bootstrap source in CI - #36
Merged
Merged
Conversation
This was referenced Sep 15, 2026
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
2 participants
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 pinned v3 compiler checkout still consumed moving
vlang/vcand TCC runtime state. Newer bootstrap inputs now fail while building that older compiler, making the required compatibility matrix fail without any repository change.Check out the
vccommit generated for the pinned V revision and the matching Linux TCC runtime, then use V's local bootstrap build for that lane. The advisory master lane keeps following its current bootstrap.Evidence:
be46d43identifies V5ff8ecbin its commit message; the prior run reached the matched compiler but failed because the unpinned local TCC directory lackedlibgc.a.