[Enhancement] Add better image tags

[MrDrMcCoy]

Is your feature request related to a problem?

As convenient as it is to re-use image tags so that users can "just pull", this is not supported in all environments. For example, if one is running Hashicorp Nomad as their container orchestrator, the container will not update without force-pull being set and the user manually initiating a replace operation. This is further encumbered by its inability to detect if there is a new tag at all, thus potentially unnecessarily pulling the same large base image again.

What is your feature request?

Add some sort of additional build number/datestamp/semver tag suffix to each push. This allows users to more easily see that they are out of date and by how far, allowing for better update decisions to be made, rather than having to compare image hashes, etc.

Are there any workarounds?

No response

Additional Context

No response

[Josh5]

Why not use the sha?

[MrDrMcCoy]

The hash doesn't tell you how out of date you are or if the next multi-gig image is really needed. It's just an opaque yes/no for if you're current, which is tedious to manually manage. Ideally, there would be releases we could subscribe to for major updates and bug fixes, which would both notify users and inform them of the tag to pull. It doesn't need to be super detailed.