Container tag latest should point to stable release

[carroarmato0]

I'm the maintainer of the App template to easily deploy Alby Hub on Unraid.
I was previously using the "latest" tag which at the time was pointing to the v1.13.0 release. Unraid (and other systems) checks if there are updates to the app based on changes to the hash of the latest tag.

At somepoint though, v1.14.0 came out and the latest tag was pointing to it, while 1.14.0 was technically not officially released yet and contained a bug for which I contacted support.

To avoid this situation in the future, would it be possible to have a stable latest release tag? That would make it easier for users to just consume the latstest and greatest release, while still allowing devs to have a latest and greatest development tag?

In Unraid you can let the user choose which branch to choose for normal releases and for development.

[rolznz]

@carroarmato0 sorry about this. I'll do more thorough testing before tagging next time.

The latest tag might still not always be aligned with the latest release on getalby.com, because we manually set what is the latest tag there when we are ready (same as Umbrel and Start9, which will also test tags and update in their own time - they do not just trust the latest tag and automatically give it to all their users.).

[carroarmato0]

@rolznz thanks for the clarification. On Unraid it's actually the same. Unraid will let you know there's "an update available" on the account that the latest tags has changed. Whenever you decide to press the update button will fetch whatever the latest tag is pointing towards at that time.