9.11.10-rc1 published as release on Docker Hub

I maintain a small Docker installation of Mattermost (only used for internal chatting) and built it on the template from this repository. I’ve set MATTERMOST_IMAGE_TAG to release-9.11 assuming that this would be way to receive the releases in this ESR sequence. (I use the team edition and I know that technically this is not ESR.) This has worked fine so far, but I just noticed that my last run through my upgrade routine increased the Mattermost version as announced in the “about” dialogue to 9.11.10. That was a surprise because this is not a published release. The docker file on Docker Hub (here) reveals that this image was built on version 9.11.10-rc1. The site does not show problems so far but I did not expect a RC version to be published on Docker Hub using a tag named release-*.

Could you let me know which policy you follow for a ‘release’ tag on Docker Hub? I would find it very useful if there was a way of automatically progressing through patch releases that uses official releases only and that is restricted to a given minor release such as 9.11.

Also, I am now wondering whether I should (and indeed can) go back to 9.11.9 when the site has been running on 9.11.10-rc1 for a while (so I have no sufficiently recent database backup to go back to).

Start by reviewing the release-9.11 image metadata on Docker Hub and the repository's Docker image publishing path, using MATTERMOST_IMAGE_TAG as the relevant entry point. Determine why 9.11.10-rc1 received a release-* tag and document the intended policy for official patch images, including whether rollback is supported.