release 1.1.2v1.1.2

Also records the host config the chain depends on. The schedule and the
storage layout existed only on the VM, so a rebuilt host would have lost
both, and the README's inline copy of the schedule had already drifted
from what actually runs. crontab.example is byte-identical to the
deployed crontab; fstab.example carries the two-disk layout and the
dockerd mount-namespace trap that makes moving the registry store
non-obvious.

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

1 files changed, 34 insertions, 0 deletions

diff --git a/ChangeLog.md b/ChangeLog.md
index cb817ed..1cdbe3d 100644
--- a/ChangeLog.md
+++ b/ChangeLog.md
@@ -4,6 +4,40 @@ All notable changes to this project are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/), versioning is
 [SemVer](https://semver.org/).
 
+## [1.1.2] - 2026-09-22
+
+Disk exhaustion on the build host, from three directions. The nightly
+`-current` chain had been failing for ten nights with "no space left on
+device", and because each stage is gated on the previous one's digest, the
+later stages skipped silently: the `-current` tags sat six days stale while
+`15.0` rebuilt fine and nothing reported an error.
+
+### Added
+- `image-builder/registry-gc.sh`: reclaim unreferenced blobs from the
+  registry store, which never shrinks on its own. Stops the registry for a
+  stable blob graph, refuses to run against OCI-index manifests (distribution
+  2.8.x deletes their children), and verifies a tag still resolves afterwards.
+- `image-builder/crontab.example` and `image-builder/fstab.example`: reference
+  copies of the host schedule and storage layout, recorded so a rebuilt VM is
+  reproducible. They previously existed only on the VM.
+
+### Changed
+- Each build now prunes its own superseded image right after pushing, instead
+  of leaving it resident until a daily prune. A replaced `sbo-full:current` is
+  ~33G of dead weight that the next variant had to build around.
+- The registry store belongs on a different disk from the docker volume. It
+  grows with every push while the build needs a large transient peak at a
+  fixed hour; sharing one volume pits a slow leak against a hard failure.
+  `fstab.example` documents the layout, including the dockerd mount-namespace
+  trap when moving an existing store.
+- The README points at `crontab.example` rather than repeating the schedule,
+  which is how the inline copy had gone stale.
+
+### Fixed
+- `bootstrap.sh`, `build-full-image.sh` and `build-sbo-testbuild.sh` abort
+  early when the docker daemon is unreachable, instead of failing deeper in
+  with a less obvious error.
+
 ## [1.1.1] - 2026-07-16
 
 ### Fixed