0xJacky a45f250169 fix(ci): stop stale images being redeployed over newer ones ...

The demo was serving an image five commits old even though CI had deployed the
current one. Two causes, and the first was mine.

Every manual deploy pasted a literal image SHA, and I kept reusing the same one
while iterating on Worker code — quietly rolling the container back over what
CI had already deployed. deploy-published.sh now defaults to the image for the
current commit, so the common case needs no SHA at all, and it verifies the
image exists before deploying. That guard earned its keep immediately: the very
next invocation caught a hand-typed SHA that did not correspond to any commit.

Only an explicit "manifest unknown" is fatal. Reaching Docker Hub fails
intermittently with a transport EOF, and treating that as a missing image would
block deploys on a network blip, so other errors warn and continue — Cloudflare
rejects a genuinely missing image clearly enough on its own.

Second cause: build.yml is path-filtered and cloudflare/** was not listed, so a
Worker-only change never reached deploy-demo. The Worker would sit undeployed
until some unrelated commit happened to trigger a build.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-02 14:30:15 +08:00

3.8 KiB

Executable File

Raw Permalink Blame History

View Raw