3-month soak check on the v7.3.0 update-check feature — **final scheduled check**. ## Checks - [ ] Cumulative reliability: `docker logs docker-dash --since 90d 2>&1 | grep -E "update-check"` — success vs failure ratio - [ ] Cron drift: parse "Update check refreshed" timestamps, verify gaps stay roughly 12h (allow ±1h jitter) - [ ] DB growth: `update_check_cache` value size unchanged vs 2-month check (small KB) - [ ] Has the user been on the latest release for any meaningful stretch of these 90 days? Cross-check `current` vs GitHub-latest at each historical point ## Decision Based on 3-month data, decide: - [ ] **Stable, no further checks needed** — close all 4 soak issues with summary - [ ] **Schedule a quarterly reminder** if a real risk emerged Add cumulative numbers from all 4 checks (#7, #8, #9, this one) as a closing comment.
3-month soak check on the v7.3.0 update-check feature — final scheduled check.
Checks
docker logs docker-dash --since 90d 2>&1 | grep -E "update-check"— success vs failure ratioupdate_check_cachevalue size unchanged vs 2-month check (small KB)currentvs GitHub-latest at each historical pointDecision
Based on 3-month data, decide:
Add cumulative numbers from all 4 checks (#7, #8, #9, this one) as a closing comment.