build: pin zot v0.2.42 + sync release runbook to 0.11.0 #105

Merged

clawdie merged 2 commits from update-zot-pin-and-release-runbook into main

2026-06-22 07:27:38 +02:00

clawdie commented

2026-06-22 06:27:58 +02:00

Owner

Continues Codex's chore/zot-0.2.42-pin work, completed and scoped.

1. zot pin v0.2.29 → v0.2.42 — consistently across build.cfg, the preflight hint (build.sh), the staging hint (stage-zot-iso.sh), and LIVE-COLIBRI-REBUILD.md.

2. Release runbook 0.10.0 → 0.11.0 — build.cfg already targets ISO_VERSION=0.11.0; the runbook lagged. Scoped to RELEASE-BUILD-RUNBOOK.md only.

Deliberately NOT changed (avoid dangling/wrong info):

Download-URL docs (FLASHING.md, README.md, TESTING.md, BUILD.md, skills/iso-publish) still reference the hosted clawdie-quindecim-0.10.0.img.xz — flipping these to 0.11.0 now would point at a file that isn't published yet. They become a publish 0.11.0 follow-up.
CHANGELOG.md 0.10.0 entries (historical).

Validation: ./scripts/check-format.sh clean; sh -n on build.sh + stage-zot-iso.sh.

Two caveats for the build host (not verifiable from this checkout):

Confirm v0.2.42 is a real upstream zot tag and rebuild zot/bin/zot before the release build (preflight will hard-fail if the binary is missing).
A zot bump may shift the event format validated in colibri#146 (the rpc transcript) — re-check glasspane against v0.2.42 output if anything moved.

Needs a build-host check before merge — don't self-merge.

🤖 Generated with Claude Code

Continues Codex's `chore/zot-0.2.42-pin` work, completed and scoped. **1. zot pin `v0.2.29 → v0.2.42`** — consistently across `build.cfg`, the preflight hint (`build.sh`), the staging hint (`stage-zot-iso.sh`), and `LIVE-COLIBRI-REBUILD.md`. **2. Release runbook `0.10.0 → 0.11.0`** — `build.cfg` already targets `ISO_VERSION=0.11.0`; the runbook lagged. Scoped to `RELEASE-BUILD-RUNBOOK.md` only. **Deliberately NOT changed (avoid dangling/wrong info):** - Download-URL docs (`FLASHING.md`, `README.md`, `TESTING.md`, `BUILD.md`, `skills/iso-publish`) still reference the hosted `clawdie-quindecim-0.10.0.img.xz` — flipping these to 0.11.0 now would point at a file that isn't published yet. They become a `publish 0.11.0` follow-up. - `CHANGELOG.md` 0.10.0 entries (historical). **Validation:** `./scripts/check-format.sh` clean; `sh -n` on `build.sh` + `stage-zot-iso.sh`. **Two caveats for the build host (not verifiable from this checkout):** 1. Confirm `v0.2.42` is a real upstream zot tag and rebuild `zot/bin/zot` before the release build (preflight will hard-fail if the binary is missing). 2. A zot bump may shift the event format validated in colibri#146 (the rpc transcript) — re-check glasspane against v0.2.42 output if anything moved. Needs a build-host check before merge — don't self-merge. 🤖 Generated with Claude Code

clawdie added 2 commits 2026-06-22 06:28:00 +02:00

build: pin zot v0.2.29 -> v0.2.42 ec89eb58bd

Bumps the zot agent tag the image ships, consistently across build.cfg,
the preflight hint (build.sh), the staging hint (stage-zot-iso.sh), and the
live-rebuild doc. Continues work started by Codex (chore/zot-0.2.42-pin).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs: sync release runbook to 0.11.0 / zot v0.2.42 67c8b9ee6d

build.cfg already targets ISO_VERSION 0.11.0; the runbook still said 0.10.0.
Scoped to the release-cutting doc only — download-URL docs (FLASHING/README/
TESTING) stay at 0.10.0 until 0.11.0 is actually published, and CHANGELOG
history is untouched.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>