Golden 0.344.0 — bake + publish, 2026-10-26 (the attended release run; D52)
Why: the Sunday 2026-10-25 weekly bake was missed (it was not in that night's brief); the operator ruled D52 = bake
today on v0.344.0 (09 §3 decision 264), with the waiver covering 2026-10-26 only. Controller 0.344.0 was released the
same morning (global floor 09:07:47 UTC, MinAgent 0.158.1). Procedure: documentation/runbooks/RUNBOOK-manual-build.md
§4.0 and §4.1 steps 1–4, in the drill VM on DooPlex. The script came from CC's felhom-agent clone at origin/main
(b890b57; build-golden.sh sha256 645b3b65…, the same file as the 0.331.0 bake).
Previous (../golden-0.331.0-2026-10-18/) |
This bake | |
|---|---|---|
build-golden.sh |
v3.2.0 | same file |
| Controller | felhom-controller:0.331.0 (MinAgent 0.158.1) |
felhom-controller:0.344.0 (MinAgent 0.158.1) |
| Docker engine | the approved set (six pairs) | the same six pairs — the hub's newest approved Docker release is still os-docker-20261004-142842 (read from the hub DB, with its WAL, today) |
| Template | debian-13-standard_13.6-1_amd64.tar.zst |
same (after pveam update; _amd64 filtered) |
| Token | ~/.gitea-token file → file |
from sec (GITEA_PKG_TOKEN, GITEA_PKG_USER), written to a 0600 file and copied file → file, the DooPlex copy shredded |
Pass markers (from bake.log, this folder)
[golden] build-golden.sh v3.2.0 — baking controller gitea.dooplex.hu/admin/felhom-controller:0.344.0
[golden] Docker engine set PINNED to the approved release: containerd.io=2.3.6-1~debian.13~trixie … docker-compose-plugin=5.6.0-1~debian.13~trixie
docker OK (overlay2; data-root /var/lib/docker)
INFO: including mount point rootfs ('/') in backup
INFO: including mount point mp0 ('/var/lib/felhom') in backup
[golden] upload OK (HTTP 201)
GOLDEN_VERSION=0.344.0
GOLDEN_SHA256=767a90fe07ed47c85a3e08a16b85926e30531b65608f9856aa25855b4dd53210
No excluding, no FATAL, no GOLDEN_DOCKER_PKGS not set; the unit Result=success. Round trip: the registry's file
downloaded and hashed = the bake's sha, 637,293,448 bytes (02-round-trip.txt). Token: the unit's properties grep = 0
(00-boot.txt); the committed log grep = 0, with a working control (= 1 on a copy with the token appended, the copy
shredded). Teardown: 03-teardown.txt (CT 9100 purged, token/user/script/log shredded in the VM, VM off, disk back to
virgin). No controller push after the bake.
Vouch — the operator's act (never CC's)
Three fields together (runbook §4.1 step 5), Configuration → Day-0 artifacts:
- golden 0.344.0, sha256
767a90fe07ed47c85a3e08a16b85926e30531b65608f9856aa25855b4dd53210 - agent 0.166.0 (vouched 2026-10-26 10:04:55 CET, unchanged), sha256
3f22c65b78914632fa476292f6b58e5af3ed9e9900f3a5a7a347a9c0bfea9c5c - min_agent 0.158.1 (unchanged)