-
v1.8.1 — unblock v1.8.0: fix the $HOME-relative pi stage assertion
Lint / actionlint (push) Successful in 16sLint / hadolint (push) Successful in 13sPublish Docker Image / resolve-versions (push) Successful in 10sPublish Docker Image / base-decide (push) Successful in 16sPublish Docker Image / build-base (push) Has been skippedPublish Docker Image / smoke-studio (push) Successful in 5m20sPublish Docker Image / smoke (push) Successful in 14m40sPublish Docker Image / build-variant-studio (push) Successful in 21m51sPublish Docker Image / build-variant (push) Successful in 15m59sPublish Docker Image / update-description (push) Successful in 6sPublish Docker Image / promote-base-latest (push) Successful in 17sjoakimp released this
2026-08-15 13:21:36 +02:00 | 96 commits to main since this releasev1.8.0 never shipped — smoke (67/68) and smoke-studio (70/71) each failed one
assertion, so build-variant and everything downstream skipped and latest stayed
on v1.7.0. Image content is unchanged from what v1.8.0 intended: same pins
(pi 0.84.2, pi-atelier v0.8.1).The assertion was wrong, not the product. It grepped for a literal
stage=/home/developer/... but run() usesdocker run --entrypoint=""and no
Dockerfile sets USER or ENV HOME, so it executed as root with HOME=/root, where
the correctly $HOME-relative stage resolves to /root/.mempalace/pi-stage/.
Now asserts the user-independent invariant (stage beside the resolved palace),
plus a companion that supplies HOME=/home/developer rather than assuming it.Also: smoke_only workflow_dispatch input, so smoke assertions can be validated
against HEAD without cutting a tag — the gap that let a broken assertion sit
unrun for three days. Validated by dispatch run #119: 69 passed, 0 failed, with
build-variant/promote/update-description correctly skipped.And run() no longer discards output, so a red ❌ shows what the container said.
Downloads