Skip to content

fix: stop emitting only :latest Docker tag (policy compliance)#47

Draft
ashsolei wants to merge 1 commit into
mainfrom
chore/fix-tags-override
Draft

fix: stop emitting only :latest Docker tag (policy compliance)#47
ashsolei wants to merge 1 commit into
mainfrom
chore/fix-tags-override

Conversation

@ashsolei

Copy link
Copy Markdown

Summary

Removes the tags-override: override in .github/workflows/ci-docker.yml that suppressed the
reusable workflow defaults and caused this fork to publish only the mutable
:latest tag from its CI.

Why

iAiFy policy tags-no-bare-latest
forbids Docker image builds that emit only :latest. Without a
SHA-prefixed or semver tag, rollbacks lose meaning, audit cannot identify
which image ran, and cosign/SBOM attestations have nothing stable to bind to.

What changed

Deleted the tags-override: block so the reusable
Ai-road-4-You/enterprise-ci-cd/.github/workflows/ci-docker.yml applies
its default tag strategy:

type=sha,prefix=sha-
type=semver,pattern={{version}}
type=semver,pattern={{major}}.{{minor}}
type=raw,value=latest,enable={{is_default_branch}}

Test plan

  • CI green on this PR.
  • After merge: next image push carries both sha-<short> and latest.

Policy

Closes the offender slot for this repo in the
bare-:latest audit.

🤖 Generated with Claude Code

Removes the `tags-override:` override in .github/workflows/ci-docker.yml that suppressed the
reusable workflow default and emitted only the mutable `:latest` tag.
Falling back to the default lets ci-docker.yml emit:

  type=sha,prefix=sha-
  type=semver,pattern={{version}}
  type=raw,value=latest,enable={{is_default_branch}}

so every pushed image carries an immutable identifier alongside the
convenience latest tag. Enforces Ai-road-4-You/policy-checks
policies/workflow/tags-no-bare-latest.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented May 13, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dc0eb5ae-6adb-4485-b075-225d05a2fb01

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/fix-tags-override

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant