Skip to content

chore: stop publishing to Docker Hub - #19

Merged
MehranMazhar merged 1 commit into
mainfrom
chore/drop-docker-hub-publish
Sep 18, 2026
Merged

MehranMazhar merged 1 commit into
mainfrom
chore/drop-docker-hub-publish

Conversation

@MehranMazhar

Copy link
Copy Markdown
Member

Every Clutch service in every compose file (clutch-deploy) pulls ghcr.io/clutchprotocol/*. Nothing deployed reads from Docker Hub — publishing there has been write-only since it was added.

It costs two secrets (DOCKERHUB_USERNAME, DOCKERHUB_TOKEN) that have to be re-added by hand every time a workflow moves between repos. That is exactly what broke the demo app's build after the clutch-hub-sdk-js merge on 2026-09-18 — a real incident, not a hypothetical.

Not in this PR: deleting the Docker Hub repo, or touching the public docs that link to it (clutch-docs/docs/reference/docker-images.md and others). Those are a separate, slower decision — several doc pages link there today.

Same pass, same defect fixed elsewhere first

trigger-stage-deploy carried continue-on-error: true. With the dispatch token missing, the job failed, the run still reported green, and stage kept serving the previous image with nothing saying so — the same failure shape as an nginx include matching no files (clutch-deploy/docs/ALERTING.md).

The token is now checked before the dispatch, with a message naming what a failure means at that moment: the image was pushed, stage will not deploy it. A closing step also states that an accepted dispatch is not a completed deploy — a green tick here means the request was accepted, not that stage is running the new image.

🤖 Generated with Claude Code

Every Clutch service in every compose file (clutch-deploy) pulls
ghcr.io/clutchprotocol/*. Nothing deployed reads from Docker Hub -- publishing
there has been write-only since it was added, and it costs two secrets
(DOCKERHUB_USERNAME, DOCKERHUB_TOKEN) that have to be re-added by hand every
time a workflow moves between repos. That is exactly what broke the demo
app's build after the clutch-hub-sdk-js merge on 2026-09-18.

Not deleting the Docker Hub repo itself, and not touching the public docs that
link to it -- that is a separate, slower decision.

Same pass, same defect: trigger-stage-deploy carried `continue-on-error: true`.
With the dispatch token missing, the job failed, the run still reported green,
and stage kept serving the previous image with nothing saying so -- the same
failure shape as an nginx include matching no files (see
clutch-deploy/docs/ALERTING.md). The token is now checked before the dispatch,
with a message naming what a failure here means: the image WAS pushed, stage
will NOT deploy it. A closing step also says that an accepted dispatch is not
a completed deploy, so a green tick on this job is not read as "stage is
running the new image".

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@MehranMazhar
MehranMazhar merged commit c3e301f into main Sep 18, 2026
1 check passed
@MehranMazhar
MehranMazhar deleted the chore/drop-docker-hub-publish branch September 18, 2026 14:23
MehranMazhar added a commit that referenced this pull request Sep 18, 2026
Missed in #19. Said CI publishes to "GHCR + Docker Hub", which stopped being
true in that same PR.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
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