Three items from the #2 thread.
Added
/selfupdate latest and /selfupdate stable
Previously /selfupdate only accepted an exact X.Y.Z version or previous, so a container running a fixed version tag (e.g. :1.19.0) had no in-band way to rejoin the rolling :latest line. Reported by @famewolf — his host was stuck on :1.19.0 and /selfupdate latest was rejected.
Plain /selfupdate warns when you're on an outdated fixed tag
A container running :1.19.0 checks that immutable tag and correctly reports "up to date" even when a much newer release exists — which is misleading and was genuinely dangerous (@famewolf's :1.19.0 host kept losing its config to the pre-v1.22.0 bug, with no signal it was stuck on a buggy version). Now, when the current tag is a fixed X.Y.Z and the upstream CHANGELOG advertises a newer release, /selfupdate says so and offers three ways out: /selfupdate <new>, /selfupdate latest, or switching the compose image to :latest. Only triggers on a plain /selfupdate; an explicit /selfupdate X.Y.Z is never second-guessed; falls back silently if the CHANGELOG can't be reached.
Fixed
Auto-detect "Import selected" no longer imports stacks you didn't pick
Reported by @famewolf: he opened the auto-detect modal to browse, checked nothing, clicked "Import selected" — and a multi-container stack got imported anyway, because v1.21.2 pre-checked multi-container stacks by default. Nothing is checked by default now; "Import selected" imports only what you explicitly tick, and clicking it with nothing selected shows a "Nothing selected" toast instead of silently creating a group.
Upgrade
docker pull amayer1983/docksentry:latest
docker compose up -dTip: use image: amayer1983/docksentry:latest (not a pinned :X.Y.Z) so you track new releases automatically. If you're on a pinned tag, a plain /selfupdate will now tell you and offer /selfupdate latest.