Container tag latest should point to stable release

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.

The issue mentions the App template, Unraid, container tags, and the v1.13.0 and v1.14.0 releases, but names no repository files, tests, or entry points. First trace how release images and tags are published, then determine how stable and development tags should be separated. Done means the stable latest tag no longer points to unreleased builds while a development tag remains available.

Written by the indexing model from the issue text.