#9943 ci: Prevent backport releases from overwriting `latest` Docker Hub tag Pull request opened by edgarrmondragon Description Before (without

--latest-version

): $ ./scripts/generate_docker_tags.py \ -r docker.io \ -v v3.9.2 \ -p 3.10 \ -d 3.10 \ --git-sha $(git rev-parse HEAD) v3.9.2-python3.10 v3-python3.10 v3.9-python3.10 SHA-27ec4d0b7ac2fb0ebb54ec6083e8f46ff84f4de2 v3 v3.9 v3.9.2 latest-python3.10 latest After: $ ./scripts/generate_docker_tags.py \ -r docker.io \ -v v3.9.2 \ -p 3.10 \ -d 3.10 \ --git-sha $(git rev-parse HEAD) \ --latest-version v4.1.2 v3.9.2-python3.10 v3-python3.10 v3.9-python3.10 SHA-27ec4d0b7ac2fb0ebb54ec6083e8f46ff84f4de2 v3 v3.9 v3.9.2 Checklist • I have read the contribution guide Was generative AI tooling used to co-author this PR? • Yes (please specify the tool below) Related Issues • #9941 Summary by Sourcery Adjust Docker image tagging to avoid backport releases overwriting the latest tag on Docker Hub. New Features: • Add support in the Docker tag generation script to accept the current latest published version and conditionally generate latest tags based on version comparison. Enhancements: • Update the build workflow to fetch the latest published release version and pass it to the Docker tag generation script so that latest tags are only applied to non-ghcr.io registries when building the overall latest release. meltano/meltano