parse-server: Docker image tags missing

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue Description

Changes made to the docker CI and images pushed to Docker Hub after #7548 don’t conform to a traditional best practices of “stable” docker tags. This is a bug as it worked previously and was broken when the auto release process was added. Any developer who uses docker to keep their parse-server up-to-date as well as other docker images will run into issues with the current configuration. Examples of images on Docker Hub that follow a stable tag:

• NodeJS
• MongoDB
• Postgres

Theres are many resources online that discuss best practices for tagging. Even the docker github actions updates tags like latest by default:

Some notes for an online resource:

Stable tags mean a developer, or a build system can continue to pull a specific tag, which continues to get updates. Stable doesn’t mean the contents are frozen, rather stable implies the image should be stable, for the intent of that version. To keep it “stable”, it’s serviced to keep the evil people from corrupting our systems. (ok, evil can also be a simple mistake that has huge impacts)

An example:

A framework team ships 1.0. They know they’ll ship updates, including minor updates. To support stable tags for a given major and minor version, they have two sets of stable tags.

:1 – a stable tag for the major version. 1 will represent the “newest” or “latest” 1.* version. :1.0 a stable tag for version 1.0, allowing a developer to bind to updates of 1.0, and not be rolled forward to 1.1 :latest which will point to the latest stable tag, no matter what the current major version is.

Steps to reproduce

Attempt to pull the most up-to-date version of the latest tag:

• latest (should be the newest image of the latest version possible)

Actual Outcome

• latest is outdated by over a month and doesn’t look like it’s receiving any updates
• beta doesn’t exist
• alpha doesn’t exist
• x doesn’t exist
• x.y doesn’t exist
• x.y-beta doesn’t exist
• x.y-alpha doesn’t exist
• x.y.z-beta doesn’t exist
• x.y.z-alpha doesn’t exist
• x.y.z-beta.w exists
• x.y.z-alpha.w exists

Expected Outcome

Looking at the current auto-release structure, attempts to pull any of the following tags that should contain the most up-to-date versions of their respective image:

• latest (should be the newest image of the latest version)
• beta (should be the latest beta)
• alpha (should be the latest alpha)
• x (should be the latest of the major semver version)
• x.y (should be the latest of the major/minor semver version)
• x.y-beta (should be the latest beta of the major/minor semver version)
• x.y-alpha (should be the latest alpha of the major/minor semver version)
• x.y.z-beta (should be the latest beta of the specific semver version) - I think you can skip this, but if you really want it…
• x.y.z-alpha (should be the latest alpha of the specific semver version) - I think you can skip this, but if you really want it…
• x.y.z-beta.w (should be the beta.w of the specific semver version)
• x.y.z-alpha.w (should be the alpha.w of the specific semver version)

This same behavior should also be replicated on the Parse Dashboard repo.

Environment

Server

• Parse Server version: ^5.0.0.alpha
• Operating system: Linux
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local docker image

Database

• System (MongoDB or Postgres): N/A
• Database version: N/A
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): N/A

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): N/A
• SDK version: N/A

Logs