fix(docker): java-25 floating tag not updated on dotcms/dotcms-dev image

Problem Statement

When the 26.02.27-01_java-25 dev image was pushed to dotcms/dotcms-dev, the floating java-25 tag was not promoted to point to the new image. The java-25 tag is currently 2 days older than the versioned 26.02.27-01_java-25 tag, meaning consumers pinning to java-25 are silently pulling a stale build.

The same workflow on the non-dev image (dotcms/dotcms) is functioning correctly — the floating tag is updated on each publish run as expected. This appears to be a CI/publishing pipeline issue specific to the dotcms-dev image workflow.

Steps to Reproduce

1. Pull dotcms/dotcms-dev:java-25
2. Note the digest — it does not match dotcms/dotcms-dev:26.02.27-01_java-25
3. Compare with dotcms/dotcms:java-25 — that floating tag is current

Acceptance Criteria

• The java-25 floating tag on dotcms/dotcms-dev is promoted to match the latest versioned tag on every publish run
• The CI/CD pipeline for dotcms-dev mirrors the floating-tag promotion behavior of dotcms/dotcms

dotCMS Version

26.02.27-01_java-25 (dotcms/dotcms-dev)

Severity

Medium

Links

• Docker Hub: https://hub.docker.com/r/dotcms/dotcms-dev/tags?name=java-25

Start by locating the CI/CD publishing workflow for the dotcms-dev image and compare it with the working workflow for dotcms. Trace how the versioned 26.02.27-01_java-25 tag is published and promoted, then verify that java-25 receives the same digest on every publish run.