release: v1.13.0 — CHANGELOG heading, components table, BASE_REBUILD_DATE
Lint / hadolint (push) Successful in 10s
Lint / skill-floor (push) Successful in 11s
Lint / doc-drift (push) Successful in 17s
Lint / actionlint (push) Successful in 34s
Lint / skill-frontmatter (push) Successful in 15s
Publish Docker Image / lint-gate (push) Successful in 26s
Publish Docker Image / resolve-versions (push) Successful in 14s
Publish Docker Image / base-decide (push) Successful in 15s
Publish Docker Image / build-base (push) Successful in 44m19s
Publish Docker Image / smoke (push) Successful in 5m26s
Publish Docker Image / smoke-studio (push) Successful in 11m12s
Publish Docker Image / build-variant (push) Successful in 19m25s
Publish Docker Image / update-description (push) Successful in 15s
Publish Docker Image / promote-base-latest (push) Successful in 17s
Publish Docker Image / build-variant-studio (push) Successful in 17m51s

This commit is contained in:
2026-10-25 13:45:18 +01:00
parent 644be67ea2
commit 7737156aad
2 changed files with 36 additions and 2 deletions
+35 -1
View File
@@ -11,7 +11,41 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
---
## Unreleased
## v1.13.0 — 2026-10-25
Minor release. Headline: the **`pi-devbox-firstboot` skill** (first-boot
acceptance scoped by published state) and two fixes our own repos carry: the
**mailbox no longer lists long-answered asks as owed** against the 3.11.0
central palace (mempalace-toolkit `c04d488`), and the **AWS SSO keeper stays
idle when nothing in the session uses Bedrock** (pi-extensions `f032195`). Also
`confirm-destructive` steps aside for another bash gate, a skill-frontmatter
lint job, and the CI smoke-image reclaim fix.
Surveyed 2026-10-25, each upstream queried directly. Unchanged since v1.12.2:
pi `1.4.0` (npm `latest`), mempalace `3.11.0` (PyPI `latest`), pi-atelier
`v0.16.0` (`3b42825`, newest tag), pi-observational-memory `022da5e`
(= `master`), pi-fork `e69725c` (= `master`), pi-studio `v0.11.1` (`8a410b4`,
= `main`, newest tag), pi-toolkit `7c05901`, Node `v24.22.1` (newest 24.x; Node
26 is not LTS yet). The skillset snapshot needs no refresh
(`vendor-mempalace-skill.sh --check`: OK, still `96b840e`). The base image is
rebuilt, because `rootfs/` changed and the mempalace-toolkit SHA is part of the
base hash, so apt and the base tools pinned to `latest` re-resolve. Of those,
gosu, gitea-mcp and tealdeer moved upstream (table below). nvim `0.12.6`, fzf
`0.74.5`, git-lfs `3.8.1`, gitleaks `8.30.1`, bat `0.26.1`, eza `0.23.5`, zoxide
`0.10.0`, uv `0.13.5`, micro `2.0.15`, typst `0.15.1`, yq `4.54.1`,
agent-browser `0.39.2` and playwright `1.64.1` match their newest releases.
Each was compared against the v1.12.2 image on tor-ms22. The new download
assets for both architectures exist (HTTP 200).
### Components that move with this release
| Component | Baked in v1.12.2 | v1.13.0 | Why |
|---|---|---|---|
| **mempalace-toolkit** | `d5a03f4` | **`c04d488`** | mailbox fix, see *Fixed* below |
| **pi-extensions** | `4c1d28d` | **`f032195`** | `7237855` (bash gate, *Changed*) + `f032195` (aws-sso, *Fixed*) |
| gosu (base) | `1.19` | **`1.20`** (or later: `latest` at build time) | Go security update (GO-2026-6686); upstream sees no realistic attack path in gosu |
| gitea-mcp (base) | `v1.10.0` | **`v1.11.0`** (or later) | additive: `project_write` column options, `get_file_contents` `ref`/`path` optional; Go 1.27.3 security fixes |
| tealdeer (base) | `1.9.0` | **`1.9.1`** (or later) | patch release |
### Added