Repository navigation
chore: bootstrap from 2026.11.22.1; the plan's findings after the release - #1003
Merged
Merged
Conversation
…ease 2026.11.22.1 is released, mirrored and indexed, and carries the companion choice whose absence kept the pin at 2026.11.13.1 (2026.11.21.1 gave an installed gcc@16.1.0 no binutils once xim's recipe moved).
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
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.
.xlings.jsonmoves to 2026.11.22.1, which is released, mirrored and indexed (latestin xim-pkgindex since #1250). That release carries the companion choice. Without it, 2026.11.21.1 gave an installed gcc@16.1.0 no binutils once xim's recipe moved, which is why the pin stayed at 2026.11.13.1.b10069.2:mwrap-b10069.1was tagged and never released (its release gate ran on a changed runner image), and the release gate now passes the job's token.