Skip Docker release publishing for existing tags

[fqjony]

Summary

• Detect an existing resolved release tag during Docker release configuration.
• Keep build and scan checks, while skipping GitHub Release, Docker Hub, GCP, ACR, and Slack publication for an existing release tag.
• Preserve manually dispatched non-release GCP and ACR publishes.

Validation

• bash tests/docker-ops-build-args.sh
• Ruby YAML parse for .github/workflows/docker-ops.yml
• dev.kit repo

[Copilot]

Pull request overview

This PR updates the docker-ops reusable workflow to detect when the resolved release version already exists as a Git tag and, in that case, skip all release publishing steps while still running build/scan checks. It also updates the workflow documentation to describe this behavior and refreshes generated repo context metadata.

Changes:

• Add a “release tag exists” check during configuration and expose it as release_exists for downstream job gating.
• Skip GitHub Release, Docker Hub publishing (including manifest), GCP publish, ACR publish, and Slack notification when release_exists is true.
• Document the new skip behavior and refresh .rabbit/context.yaml generator metadata.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
docs/workflows/docker-ops.md	Documents the new “skip publishing when tag exists” behavior on release branches.
.rabbit/context.yaml	Updates generated dev.kit version/timestamp metadata.
.github/workflows/docker-ops.yml	Adds tag existence detection and gates publishing jobs based on release_exists.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.