chore: disable publishing in docker-build-and-push.yml#19
Merged
Conversation
This legacy, manual-dispatch-only workflow tags images by branch name and is redundant with build-vibedata-image.yml (the canonical auto/multi-arch/ signed pipeline). A past manual dispatch from `main` is what left the stale obot-vibedata:main tag in the registry. Keep the file for reference but stop it publishing: set push: false and guard the sign/tag steps and the registry image-scan job (all of which require a pushed image) behind `if: false`. The workflow now only builds the image to validate the Dockerfile. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
docker-build-and-push.ymlis a legacy,workflow_dispatch-only workflow that tags images by branch name. It's redundant withbuild-vibedata-image.yml(the canonical pipeline: auto on push to main, multi-arch, cosign-signed, version-resolved from.accelerate/upstream-sync.json).A past manual dispatch of this workflow from
mainis what published the stale, divergentobot-vibedata:maintag — the one that confused the Studio coding agent.What (keep the file, stop it publishing)
push: true→push: false— builds the image to validate the Dockerfile, but pushes nothing.if: false(they require a pushed image): Install Cosign / Sign Images, Copy to latest tag, and the entireoss-image-scanjob (scans the registry image).build-vibedata-image.yml.File is retained per request — not deleted.
Result
This workflow can no longer publish, sign, retag, or push
obot-vibedataunder any trigger.obot-vibedata:latest/:vX.Y.Z-vibedatacontinue to come solely frombuild-vibedata-image.yml.🤖 Generated with Claude Code