-
v1.8.3: mempalace 3.7.1, refreshed vendored skill snapshot, mempalace-census on PATH
Lint / hadolint (push) Successful in 8sLint / actionlint (push) Successful in 23sPublish Docker Image / resolve-versions (push) Successful in 13sPublish Docker Image / base-decide (push) Successful in 11sPublish Docker Image / build-base (push) Successful in 53m49sPublish Docker Image / smoke (push) Successful in 7m22sPublish Docker Image / smoke-studio (push) Successful in 18m6sPublish Docker Image / build-variant (push) Successful in 19m6sPublish Docker Image / update-description (push) Successful in 6sPublish Docker Image / promote-base-latest (push) Successful in 11sPublish Docker Image / build-variant-studio (push) Successful in 27m5sjoakimp released this
2026-08-16 23:59:21 +02:00 | 90 commits to main since this releasemempalace 3.6.0 -> 3.7.1, verified against the 3.7.1 source rather than its
changelog: no mass re-mine (legacy drawers lack chunk_total and both decision
sites trust them), NORMALIZE_VERSION unchanged at 2, chromadb stays <2 so no
index-format migration, no auto-migration exists, and downgrade remains possible.
Two behaviour changes: ALLOW_PEER_WRITER no longer works on local/chroma
palaces, and writer-lock setup failures now fail closed.The fleet primary was upgraded to 3.7.1 on a uv-managed CPython 3.12.13 and
restarted BEFORE this tag, because 3.7.1 refuses mutating tools when the served
library drifts and mempalace_reconnect cannot clear that.Vendored mempalace skill snapshot refreshed to skillset 936fed8, closing a gap
where the image-baked copy shadowed the skillset for two commits.mempalace-census gains the /usr/local/bin symlink its siblings already had.
Two new smoke assertions, both confirmed to fail against v1.8.2.Downloads