v0.270.0: no update for a current app (R-679); an interrupted install is reported (R-681); a restore brings back the pinned version's health check (R-669); R-674
gates / gates (push) Successful in 24s

Five red-proofs. MinAgent 0.131.0 unchanged.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
2026-09-24 16:49:43 +02:00
parent 7c6140d95b
commit 504eae018b
23 changed files with 1121 additions and 16 deletions
+23
View File
@@ -1,3 +1,26 @@
## v0.270.0 — no update for a current app; an interrupted install is reported; a restore brings back the right health check (2026-09-24, R-679, R-681, R-669, R-674)
**MinAgent: 0.131.0** (unchanged). Needs hub v0.123.0 (unchanged; R-681 rides the existing `app_deploy_failed`).
New strings: yes (hu + en).
- **R-679:** an Update pressed on an app already at the catalog head is refused BEFORE anything moves —
`409 already_current`, „Ez az alkalmazás már a legfrissebb elérhető változatot futtatja — nincs mit
frissíteni." / "This app is already running the newest version available — there is nothing to update."
"Current" is `CatalogOrder`'s verdict, so a re-tested digest for a floating tag still updates. Measured:
navidrome at the head was pressed four times, each a dump, a pull and a restart. (A test comment had called a
same-version Update "the repair path"; Restart is that path.)
- **R-681:** an install cut off by a controller restart is finished through the failure path and REPORTED: an
install marker is written before the compose-up and removed when the install ends; a marker found at start →
`compose down` (volumes kept), the stale pin records cleared, `app_deploy_failed` with the reason, and the
apps page says „A telepítés egy újraindítás miatt félbemaradt…" until the next install. An install that had
finished (its record says deployed) only loses the marker.
- **R-669:** the recovery unit captures the PINNED version's `.felhom.yml` (`applied-meta`), not the stack dir's
file the sync may already have replaced with a newer or failing step's; a restore makes the restored file the
applied record. Measured 2026-09-24: the undo judged the correct old version with the failed step's probe
and held the app.
- **R-674:** the ladder log says "AT THE HEAD" when the pin equals the newest step, not "older than the ladder".
- Red-proofs: five (REPORT).
## v0.269.1 — an installed app keeps the image it runs until an Update moves it (2026-09-24 night, Part B live finding)
**MinAgent: 0.131.0** (unchanged). Needs hub v0.123.0 (as v0.269.0). New strings: none.