v0.5.3
Apply-email polish. Two small fixes that compound: shrink the captured apply log at the source, then hide what's left behind a spoiler so a clean log doesn't dominate the email.
Changed
- Pass
--quiettodocker compose pullduring apply. Without a TTY, compose's plain progress mode emits every per-layer redraw as a separate newline (e.g.xxxxxxxxxxxx Downloading [=> ] 96.53MB/3.862GBrepeated for every status update). On a multi-GB image that ballooned the capturedapply_logpast 100KB and the resulting hold/applied email past 250KB. With--quiet, stdout is empty on success and errors still surface on stderr — apply logs on a successful pull are now near-empty (typically just the finalContainer X Recreatedline from theupstep). - Apply log section is now collapsed by default in HTML emails. Both per-event mails (
buildAppliedHtmlinsrc/daemon/index.ts) and the daily digest (renderRowinsrc/notify/digest.ts) wrap the apply log<pre>in a<details>element. The<summary>advertises line count and size so the operator can decide at a glance whether it's worth opening (e.g.Apply log (1348 lines · 124.6 KB)). Plain-text bodies are unchanged — the───── apply log ─────divider stays.
Notes
- The
--quietchange only affects apply-time pulls; tag discovery still uses the registry HTTP API (no shell-out, no progress lines to silence). <details>is supported by Gmail web, Apple Mail, Thunderbird, iOS/Android Mail. Outlook desktop renders<details>as flat content (no collapse) — graceful degradation, not a regression.- The combination cuts a typical large applied-email from ~265KB to ~5KB and leaves operators with one-glance triage instead of a wall of progress bars.