Skip to content

ci: bootstrap pin moves to 2026.9.2.1 - #546

Merged
Sunrisepeak merged 2 commits into
mainfrom
ci/bootstrap-pin-2026.9.2.1
Sep 2, 2026
Merged

ci: bootstrap pin moves to 2026.9.2.1#546
Sunrisepeak merged 2 commits into
mainfrom
ci/bootstrap-pin-2026.9.2.1

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

The 2026.9.2.1 release is published, mirrored to both hosts and indexed: latest in openxlings/xim-pkgindex points at it (commit ff0996e), and that commit's Publish Index Artifact run is green — which is what xlings install actually consumes.

The pin is bumped only after that sequence. CI installs the pinned version from the index, so a pin that runs ahead of the index is a job that cannot start.

Verified in a clean sandbox before opening this:

$ xlings subos use e544-0902 --sandbox --cmd 'xlings install mcpp@2026.9.2.1 -y; mcpp --version'
  ✓ 1 package(s) installed
mcpp 2026.9.2.1

The release is published, mirrored and indexed: `latest` in
openxlings/xim-pkgindex points at 2026.9.2.1, and its `Publish Index Artifact`
run is green on that commit, which is what `xlings install` consumes.

The pin is bumped only after that sequence, never before it — CI installs the
pinned version from the index, so a pin ahead of the index is a job that
cannot start.
…8 did not state

Section 13 carries the observed transcript rather than the expected one: the
sandbox run on the published 2026.9.2.1, the openkal consumer built for
aarch64-linux-musl and executed through the declared runner, and the release
state with the checks that were recomputed rather than read from a sidecar.

Its load-bearing line is a shell error. `qemu-aarch64-static` is not on PATH in
that SubOS, and the two preceding sections had already run the artifact through
it — which establishes the one chain no e2e covers, from [xlings] deps to the
payload bin/ that runner_lookup searches first.

Section 8 gains consistency, upgrading, and what a person sees. The first two
were implicit in the structure and compatibility paragraphs; stating them
separately is what makes 'no second derivation' and 'no cache invalidated'
checkable claims rather than consequences someone has to notice.
@Sunrisepeak
Sunrisepeak merged commit 1020a97 into main Sep 2, 2026
36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants