-
changelog: release v1.8.11 — the mail nobody could deliver, and the ship that skipped a file
Lint / hadolint (push) Successful in 13sLint / actionlint (push) Successful in 17sPublish Docker Image / resolve-versions (push) Successful in 19sPublish Docker Image / base-decide (push) Successful in 10sPublish Docker Image / build-base (push) Successful in 53m20sPublish Docker Image / smoke (push) Successful in 4m48sPublish Docker Image / smoke-studio (push) Successful in 4m58sPublish Docker Image / build-variant-studio (push) Successful in 17m0sPublish Docker Image / build-variant (push) Successful in 26m43sPublish Docker Image / update-description (push) Successful in 7sPublish Docker Image / promote-base-latest (push) Successful in 24sjoakimp released this
2026-08-27 23:39:39 +02:00 | 62 commits to main since this releaseNames three things riding in via floating refs, since the rule this
fleet adopted (v1.8.9) is to name a behaviour change before tagging,
not after:- mempalace-toolkit b2b50af -> 21023e7: the rsync --checksum ship fix
(a real behaviour change to every remote-mode client) and RFC 003
§7.13 (docs only). - skillset 6eb20af -> a12fe5e: mermaid-diagrams cutU normalisation and
the mempalace skill's from_agent identity rule, plus the vendored
fallback snapshot re-pinned to match (this pi-devbox commit).
Dependency audit run by direct command against every component, not
assumed: pi/mempalace/pi-atelier/pi-studio/pi-toolkit/pi-extensions/
pi-fork/pi-observational-memory all confirmed unchanged since v1.8.10.
pi-studio's apparent SHA drift on ls-remote turned out to be an
annotated-tag-object hash vs its underlying commit hash, not real
drift -- checked with ^{commit} before writing it down as 'none'.Downloads
- mempalace-toolkit b2b50af -> 21023e7: the rsync --checksum ship fix