controller v0.68.1: boot-id recreate ALL deployed drive-backed apps (state-independent)
E1 caught it: filtering on State!=stopped missed apps docker hadn't auto-restarted yet at the one-shot instant (5 apps exited after host reboot). Now recreates every deployed present drive-backed app regardless of state (deployed=should run). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -1,5 +1,14 @@
|
||||
## Changelog
|
||||
|
||||
### v0.68.1 — boot-id recreate ALL deployed drive-backed apps (state-independent) (2026-06-15)
|
||||
|
||||
Fix caught live in the E1 host-reboot test: `shouldRecreateOnBoot` filtered on container state
|
||||
(`State != stopped`), so apps docker hadn't auto-restarted yet at the one-shot boot-id instant were
|
||||
MISSED (5 apps stayed exited after a host reboot). The boot-id recreate now recreates EVERY deployed
|
||||
drive-backed app whose drive is present, independent of current state (`app.yaml` deployed = should run)
|
||||
— truly deterministic. Test updated.
|
||||
|
||||
|
||||
### v0.68.0 — storage lifecycle on the intermediary model: H2/H3/M1/M3 + deterministic boot-id (2026-06-15)
|
||||
|
||||
Pairs with agent v0.36.0. Finishes the storage lifecycle on the new mount model.
|
||||
|
||||
Reference in New Issue
Block a user