Fixed
Duplicate "Updates Available" notification after auto-self-update
When the scheduler restarted via the v1.16.3 self-update-first flow, both the deferred check (on the freshly-booted process) AND the regular cron-tick of the same minute would fire check_all() — the user got two identical "Updates Available" messages, roughly a minute apart in Telegram.
Now the deferred-check resume claims the current minute and the main scheduler loop initialises last_check from it, so the cron-tick for the already-handled minute is skipped.
Three near-identical restart messages
A self-update produced this sequence:
Starting self-update — your container update check will resume right after restart.
🚀 Docksentry started (v1.17.0)
✅ Restarted on the new version. Now checking your containers...
The middle one is redundant. The generic startup notification is now suppressed when a deferred-check marker is present at boot, leaving a cleaner sequence:
🔄 Auto Self-Update / 🗓️ New: ... | Old: ...
Starting self-update — your container update check will resume right after restart.
[restart]
✅ Restarted on v1.17.1 — checking your containers...
🔄 Docker Updates Available
• …
The resume notice now includes the new version (was: vague "on the new version").
Both reported from a real-world v1.17.0 deployment.
docker pull amayer1983/docksentry:latest
docker compose up -d