What will happen if we publish a release like 2.10.0?

Oh dear, good point 🙈️

Changed it to the following

CI_COMMIT_TAG="v2.10.0"
short_tag=${CI_COMMIT_TAG%.*}
echo "$short_tag"
v2.10

And what about 10.0.0? Same thing…

And docs must get an update: https://woodpecker-ci.org/docs/administration/deployment-methods/docker-compose#docker-images

Deployment of preview was torn down

3.0.0.rc.0 and other rc versions would still override major versions as explained in #4597.
Can't get why we need to drop latest. We could suggest people to use pinned version, if they want to use latest fine.

3.0.0.rc.0 and other rc versions would still override major versions as explained in #4597.

Sure but in this case users opted in to use this version on purpose and not by getting a background update due to a rolling tag.

Can't get why we need to drop latest. We could suggest people to use pinned version, if they want to use latest fine.

Even though some/most might do, the "a major upgrade happened and everything broke" issues will never stop this way, also because people often don't set a tag at all and hence will get latest implicitly.
By removing latest, you workaround this problem actively by forcing users to specify a tag they want.

If you think about it, why should there ever be a tag crossing major version automatically? This will always result in a functional disaster. Admins have to adjust the config anyhow for a major upgrade, so arguing with "it reduces admin work" doesn't work. But it pro-actively prevents issues for admins and issues posted to the project. Does that make sense?