[FEATURE_REQUEST] Show actual app version for floating tags

[kuzabi]

Is your feature request related to a problem? If so, please describe.

For containers using floating tags such as:

image: lissy93/dashy:latest

Dockhand correctly detects an update by comparing image digests, but the UI does not show the actual application version currently running.

Many images already provide this via OCI labels, for example:

org.opencontainers.image.version=4.6.5
org.opencontainers.image.source=https://github.com/lissy93/dashy

This makes it hard to understand which release notes are relevant before clicking Update.

Describe the solution you'd like

When org.opencontainers.image.version is available, show it in the container/update view.

Example:

Image: lissy93/dashy:latest
Running version: 4.6.5
Available version: 4.6.6
Update available

Ideally, when the remote image also exposes org.opencontainers.image.version, Dockhand could display both:

Current: 4.6.5
Target: 4.6.6
Digest: old → new

and popup with the relevant release notes when available.

Suggested fallback

1. org.opencontainers.image.version
2. configured tag
3. digest-only behavior as today

This would keep the current digest-based update mechanism for latest/stable, while providing enough context to make an informed manual update decision.

Priority

Medium (Would be very useful)

Is this something you would be keen to implement

None

[lissy93]

Hmm, this should already be in place 🤔

Inspecting the current :latest image does seem to have all the right OCI tags, including the right version

The Dockerfile accepts version:

dashy/Dockerfile

Line 33 in f956514

org.opencontainers.image.version="${VERSION}" \

And the docker workflow does correctly attach the version:

dashy/.github/workflows/docker.yml

Line 168 in f956514

VERSION=${{ steps.version.outputs.value }}

I'm not super familiar with Dockhand, but i did just give it a try on the :latest version of Dashy, and it does seem to show the version? Or am I misunderstanding?

[lissy93]

I think this should all be working, but just to be safe I've got an update ready in #2325, whereby if for any reason the workflow doesn't have a git tag to deploy from, then it will read the version directly from the package.json, and attach this as the OCI version's value.

Only thing I can think of is something funny happened when GitHub Actions went down last week.

Or let me know if I've totally misunderstood, and I'll re-open this