Files

T

gates / gates (push) Successful in 29s

Details

More apps update themselves at night (30+2 -> 35+3); the same-name security-fix gap measured (R-740, decision for the operator)

- Twelve steps published on both venues (catalog): first ladders for calibre-web, gitea, wger,
  crafty-controller, uptime-kuma, zipline (two steps); within-major emby, ghost, home-assistant,
  outline, rallly. immich's step v3.0.3 -> v3.2.2 re-proven at 768M (Part D).
- Part C: the night leg skips a digest-only change AND the catalog never records a same-tag re-test,
  so a same-name upstream fix reaches no box. Row R-740; the decision in STATUS; `09` decision 30
  carries a dated note (the decision itself unchanged).
- Rows: 369 -> 377. Opened R-735..R-742; closed R-735, R-738, R-742; narrowed R-462, R-624, R-446,
  R-440, R-734, R-732. The currency audit gains §1b (and corrects its 31+1 to 30+2).

Evidence: documentation/audits/more-night-apps-2026-09-30/. Report: REPORT-more-night-apps-2026-09-30.md.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

2026-09-30 20:27:28 +02:00

4.6 KiB

Raw Blame History

STATUS — what works, what's broken, what's next

Ready for the first real tester (Tester-2): yes. You confirmed the tunnel route and the connect mails (2026-09-30).

Updated 2026-09-30 (evening). Both demo boxes run controller 0.283.1 and host agent 0.138.0. Hub 0.126.0. New installs get golden 0.283.1 with agent 0.138.0. No controller, agent or hub release today.

Tester-2 — read only, from the hub. The customer record exists. Tester-2's box has not registered yet, so there are no apps to read.

One decision for you

Question: should a box also take, at night, a security fix that the app's maker ships under the same name? Database images like postgres:18-alpine or redis:7-alpine get fixes without a new name. Seven of the eight such names we use on Docker Hub got a new push in the last 30 days.

Today no box gets these fixes at all — not at night, and not by the Update button either. The reason: the catalog only records a test when the name changes, so the box never learns that a newer, tested image exists. The page says "up to date".

Option A — the night takes a tested fix. The catalog re-tests the same name at the new image (bench and scratch box, as today), and records it. The box then takes it at night by itself, with its backup and undo. Measured: the box already does this with no change; only the catalog side is new work (about one evening to build). Cost after that: about 20 app re-tests a month, machine time only, run by day.
Option B — keep it manual, say so honestly. No new work. The fixes arrive only when we move an app to a new name. Database engines rarely change name, so their fixes may wait for months. I would correct the text of the earlier decision, which says the night would take them.

If nothing is decided: nothing breaks. Database images stay at the build of the day we tested them. Who is blocked: nobody today. My recommendation: A, database and redis names first — that is where security fixes land, and the box side already works.

What I did, and it worked

More apps update themselves at night: 35 now (plus 3 when a full copy exists), up from 30 (+2) at the start of the evening. New: gitea, wger, crafty-controller, uptime-kuma, zipline. calibre-web counts as "with a full copy", because its update rewrites the book library's own database file.
Twelve updates tested and published, each on the test bench and on the scratch box: calibre-web, gitea, wger, crafty-controller, uptime-kuma, zipline (their first tested updates; zipline in two steps), and emby, ghost, home-assistant, outline, rallly. Each of these apps is now on its maker's newest version in its line.
calibre-web (books) and gitea now have tests. calibre-web: a book goes in through its Upload button and is read back. gitea: its first-run form is filled in the way a household does it.
immich's older in-between update is fixed. It still gave the database 512 MB and it does reload the big list of places. Tested again with 768 MB and no swap: 0 kills. No box runs immich today.

What broke, and what I did

wger: an update would have broken it. After the update the app looked fine, but nobody could log in. Its database was never upgraded, because the catalog forgot one setting. Fixed in the catalog, and tested again: it works. No box runs wger.
zipline: its newest version cannot be reached in one jump. The scratch box saw it fail and put the old version back by itself in 20 seconds — the undo worked on a real failure. Going through the version in between works; that is now the path.
The scratch box's disk filled with old app images. Removing an app or updating it never deletes the old image. On a household box this would slowly fill the disk until updates are refused. Written down; not fixed today.
For a few seconds after a fresh install, calibre-web's well-known default login works. The box changes it right after, but the app is already reachable. Written down; not fixed today.
wanderer cannot run on the test bench, so it was not tested. Written down.

Rows. Tonight: 3 closed (all three found and fixed tonight), 6 narrowed, 8 opened. The list went from 369 to 377 rows. (The brief said 366; the afternoon session had already added three.)

What needs you

The decision above (same-name security fixes). If you do nothing, nothing changes.
The image clean-up on a box will need your word on what the box keeps (the running image and the one before it, for the undo). If you do nothing, disks fill slowly; nothing breaks tonight.
No golden bake is due. The weekly bake stays around 7 October.