Docker image tags are confusing and lack clear version mapping

[Duck15]

Is your feature request related to a problem? Please describe.

I'm always frustrated when trying to use TShock Docker images because the tags are confusing and don't correspond to official release versions. Currently, there are many sha256- prefixed tags (e.g., sha256-128bde7551c...) that are not human-readable, and tags like general-devel and i18n provide no clear indication of which TShock version they contain. This makes it difficult to select stable versions for deployment or understand what version is actually running.

Describe the solution you'd like

I would like the Docker image tagging to follow a clear and consistent scheme that matches official TShock releases:

• Each official release version should have a corresponding Docker tag (e.g., 5.9.9.0, 5.9.8.0, etc.)
• latest tag should always point to the most recent stable release
• devel or nightly tags can be maintained for development builds
• Avoid using sha256- prefixed tags as primary identifiers in the tag list

Describe alternatives you've considered

• Using general-devel as a workaround, but this is unpredictable and may not be stable
• Building custom Docker images from source, which adds unnecessary complexity for users who just want to run the official version
• Parsing commit hashes to guess versions, which is impractical and error-prone

Additional context

Screenshot of current confusing tags:

Community discussions (see #3131 and #2698) indicate that other users are also experiencing confusion with the current tagging scheme. Improving this would greatly enhance the user experience for Docker-based deployments.

[hakusaro]

Every release version has a corresponding docker tag to the actual version number, by the way.

[hakusaro]

It would be better, if you are a CN native speaker, to create issues in CN instead of using AI to translate, as this comes off quite hostile.

[Duck15]

彳亍，但是我希望在readme里弄一个 docker部署概览((
我是看到github action ci里有docker字样 才寻思找下版本的（

[hakusaro]

I think it would be better to at least tag latest and document how to do this for now.

[hakusaro]

I do think academically running general-devel tags is not the worst idea.

[timschumi]

I think it would be better to at least tag latest and document how to do this for now.

latest already gets tagged and points to the latest release tag.

As for the sha256- tags I'm not entirely sure where they are coming from, they are not in the list of tagging rules.

[timschumi]

As for the sha256- tags I'm not entirely sure where they are coming from, they are not in the list of tagging rules.

The hash in the tag name matches the subject hash from the attestation, so I assume this will fix it: #3267

[ACaiCat]

Hmmm, maybe we should clean all sha256- tag images

[timschumi]

Hmmm, maybe we should clean all sha256- tag images

I suppose someone with write access would either have to sit on this page for a bit and spam delete or to just script something completely custom. With GitHub there is apparently no in-between, luckily it's apparently only 5 pages to go through.

[ACaiCat]

I wrote one, but my token doesn't have permission to delete org images XD