Fixed
/selfupdate latest (and stable) now actually moves you back onto the rolling tag (#2, @famewolf).
Closes the SET/UNSET asymmetry: /selfupdate <version> could pin a tag, but returning to :latest was a dead end — when the rolling tag's digest already equalled the pinned version's, the self-update short-circuited to "already up to date" and the container stayed on the pinned tag, never tracking latest again. You had to edit compose on the host.
Now, when you explicitly ask for latest/stable and the container is on a different tag, Docksentry re-tags and recreates even on an unchanged digest, so the image reference becomes the rolling tag. Asking for latest while already on :latest still does nothing.
Contributors
famewolf