fix(build): jib pushes only the version tag, never :latest

[tcheeric]

Why

During the gateway-customer 0.26.0 release (2026-10-11 11:49:38Z) the jib config pushed :latest as well as the version tag. Staging pulls :latest, so a release build could change what staging runs without a deploy. It was restored within 17 s and the host never pulled it (see the Redeploy 10 notes). This repo has the same pattern.

Change

<to><image> is now <repo>:${project.version}, and the extra <tags> (latest) is gone. Promoting to :latest stays an explicit deploy step.

Evidence

mvn -Dmaven.repo.local=<scratch> ... jib:buildTar, RepoTags from the tarball's manifest.json. Nothing was pushed to the registry.

    base-phoenixd-java-phoenixd-mock rc=0 "RepoTags":["docker.398ja.xyz/phoenixd-mock:latest","docker.398ja.xyz/phoenixd-mock:0.3.3"]
    after-phoenixd-java-phoenixd-mock rc=0 "RepoTags":["docker.398ja.xyz/phoenixd-mock:0.3.3"]
    base-phoenixd-java-phoenixd-rest rc=0 "RepoTags":["docker.398ja.xyz/phoenixd-rest:latest","docker.398ja.xyz/phoenixd-rest:0.3.3"]
    after-phoenixd-java-phoenixd-rest rc=0 "RepoTags":["docker.398ja.xyz/phoenixd-rest:0.3.3"]

(base = origin/develop, after = this branch)

Do not merge without review.

[github-actions]

Qodana Community for JVM

5 new problems were found

Inspection name	Severity	Problems
Constant values	🔶 Warning	3
AutoCloseable used without 'try'-with-resources	🔶 Warning	1
Simplifiable conditional expression	🔶 Warning	1

☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions