Added
Version numbers in /history
Closes #22. Requested by @famewolf. Two layers, both opt-in by data availability:
A. Docksentry self-update — precise
At self-update time we know our current version from version.VERSION. The new version isn't known until the new container boots. Two-step write:
_save_selfupdate_history()writes… (selfupdate v1.18.5 → ?)at the swap- Post-boot fixup in
main.pydetects the deferred-check marker, finds the last entry with→ ?), and patches the?with the freshly-booted process'sVERSION
Result:
✅ docksentry — 2026-06-01 14:11:10
🗓️ 2026-05-31 → 2026-06-01 (selfupdate v1.18.5 → v1.18.6)
B. Other containers — best-effort from OCI labels
Reads org.opencontainers.image.version before and after each pull. Appends (v{old} → v{new}) to the detail line when both labels exist and differ.
Empirical coverage on a 15-container real-world stack: ~40 %.
| Has label | Doesn't |
|---|---|
| n8n, mariadb, adguardhome, gitlab, paperless-ngx, open-webui | nginx-proxy-manager, redis, postgres, nextcloud, portainer, influxdb |
Label values are normalized — single leading v is stripped (so adguard's vv0.107.73 becomes v0.107.73 on display), and obviously-bogus values (12-char image IDs, branch names like main/latest/master) are discarded.
Containers without a usable label render the same as before (date + size only) — no regression for the 60 % that don't carry the label.
✅ n8n — 2026-05-30 18:01:23
🗓️ 2026-05-15 → 2026-05-30, 📦 1.5 GB (v2.14.2 → v2.15.0)
docker pull amayer1983/docksentry:latest
docker compose up -d