Describe the bug
The change to COMPOSE_VER (bumped to 2.27.2) merged in 60eaa92 has not been reflected in the images published to Docker Hub, even though new tags have been pushed since the merge.
To Reproduce
Pull any tag published after the merge and check the Docker Compose version:
docker run --rm cimg/base:current docker compose version
It still reports 2.27.1 instead of 2.27.2.
Expected behavior
Images published after the merge of 60eaa92 should include Docker Compose 2.27.2.
Workarounds
Install Docker Compose 2.27.2 manually in the job as an additional step.
Screenshots and Build Links
Merged commit: 60eaa92
Additional context
The change was made in Dockerfile.template. My understanding is that gen-dockerfiles.sh and the release process need to be run by a maintainer for the change to make it into the published images. Please could you trigger that?
Describe the bug
The change to
COMPOSE_VER(bumped to2.27.2) merged in 60eaa92 has not been reflected in the images published to Docker Hub, even though new tags have been pushed since the merge.To Reproduce
Pull any tag published after the merge and check the Docker Compose version:
It still reports
2.27.1instead of2.27.2.Expected behavior
Images published after the merge of 60eaa92 should include Docker Compose
2.27.2.Workarounds
Install Docker Compose
2.27.2manually in the job as an additional step.Screenshots and Build Links
Merged commit: 60eaa92
Additional context
The change was made in
Dockerfile.template. My understanding is thatgen-dockerfiles.shand the release process need to be run by a maintainer for the change to make it into the published images. Please could you trigger that?