[Feature] Display version tag where possible, please?

[LeeNX]

What would you like Docksentry to do?
Related to #32 ... I find that I have a much better idea of tag versions of hash, plus seeing and update from one minor to another increasing minor is a good pattern, vs hashes, where I don't have a clue in general.

Looking at the first message from my Telegram bot, Current version: might just be miss labelled? I don't know what this is?

As the second message has the tag version and hash, love the arrow direction. Maybe the info New: 2026-06-28 | Old: 2026-06-28 again does not have a meaningful label to me and could be better in the wrong direction, keeping with the data above and below it, which is old -> new ... What is the date? Release or deploy date?

Why is this useful?
This might be wrongly titled, because when I first saw the update, I was wanting the tag version below the Image or really above the Image hash, but after collecting the screenshot, I see I don't know what the date info is really.

Your setup

• Docksentry version: v1.34.0
• Notification channels used: Telegram / Webhook
• Deployment: Docker run / Docker Compose / podman-compose

[amayer1983]

Good eyes — both were genuinely misleading, fixed in v1.35.0:

• 🗓️ Current version: <date> → that was the image's date, not a version. It now reads 🗓️ Image date: <date>.
• 🗓️ New: … | Old: … → ran backwards vs everything else; now 🗓️ Image date: <old> → <new> (consistent old → new).

To answer "what is the date?" — it's the image's build/created timestamp (from the image metadata), i.e. when that image was published, not your deploy time.

For the actual tag/version you wanted: that's the 🔖 v_old → v_new line added in v1.34.0 — it reads the image's org.opencontainers.image.version label where present (Docksentry's own images always have it; other images ~40% of the time). Regular container update results already show the same arrow. If you'd like the current version shown in the pre-update "Updates Available" list too, just say so — that's an easy add.

[LeeNX]

Image creation date makes sense. Just saw the same date for a few updates, but that was for dockSentry.

Please can we get the old and new tag version in the updates. This is very meaningful for me. Please give me that dopamine hit. ;-)

I understand not all images have the version info. I am going to chase all image publishes to make sure this info is present else I am not going to use their images (let's see how I do with other projects).

[LeeNX]

I wonder if I could drum up support - cloudflare/cloudflared#1682

[amayer1983]

Dopamine incoming 😄 — v1.36.0 adds 🔖 v_old → v_new to each line of the "Updates Available" notification.

• Old version: your local image's org.opencontainers.image.version label (falls back to a SemVer tag if that's how the image is tagged).
• New version: read straight from the remote image's OCI config before anything is pulled — so you see where you're going before you tap update. Multi-arch images resolve to the linux/amd64 config for the label.

Best-effort by design: an image without the label just shows no badge (so your publisher-chasing crusade directly pays off here 💪), and a registry hiccup never affects the check. The remote lookup only runs for the containers that actually have an update, so no slowdown on normal checks.

This is on top of the update result arrow that already existed. Give it a spin on v1.36.0 and let me know it scratches the itch — and if you want the same badge somewhere else (e.g. the webhook payload), say the word.

[LeeNX]

My Wife just asked why I am not coming to bed, I said that @amayer1983 has a new release with features too test ... ;-)

My podman host was on v1.34.1, just deployed v1.36.0, I will for next release. Thanks @amayer1983

[amayer1983]

Ha! Please send my apologies to your wife 😄 — go to bed, the badge will be waiting for you. You won't see it on this update (v1.34.1 → v1.36.0 was detected the old way), but the next time any of your images gets an update you'll get the 🔖 v_old → v_new.

Bonus: your podman host is now on v1.36.0, which also carries the v1.35.0 self-update socket fix (#43) — so your next /selfupdate there should actually recreate the container instead of just pulling. Curious whether that one's happy now too whenever you get to it. Sleep well 🌙

[amayer1983]

Follow-up: the version badge now rides on all channels, not just Telegram (v1.38.0) — Discord embeds show 🔖 v_old → v_new per container, the generic webhook payload carries old_version / new_version fields, and the e-mail summary includes it too. So whichever channel you watch, you get the version story. (Still empty for images without the OCI version label — the publisher-chasing pays off everywhere. 😉)