Skip to content

🚨[Hotfix] Tolerate Cloudflare alias propagation - #89

Merged
maruson08 merged 1 commit into
mainfrom
hotfix/v2.1.0-deployment-propagation
Sep 25, 2026
Merged

maruson08 merged 1 commit into
mainfrom
hotfix/v2.1.0-deployment-propagation

Conversation

@maruson08

Copy link
Copy Markdown
Member

Problem

Automatic deployment run 36149822267 uploaded v2.1.0 and passed its immutable deployment smoke test, but the stable Cloudflare alias had not propagated the new Image → Text route when checked seconds later. The workflow failed on a transient 404 even though the stable alias and production custom domain passed the complete smoke suite shortly afterward.

Fix

  • Retry stable alias and custom-domain smoke checks up to six times with ten-second intervals.
  • Keep immutable deployment validation immediate.
  • Preserve all route, asset, redirect, indexing, canonical, and social-metadata assertions.
  • Add static regression coverage for both aliases and the bounded retry contract.

Validation

  • node tests/cloudflare-bridge.test.mjs
  • npm test
  • git diff --check
  • Commit and PR-title convention validation
  • Current immutable, stable, and custom production endpoints pass the full deployment smoke suite

Closes #88

@maruson08
maruson08 merged commit b82e565 into main Sep 25, 2026
1 check passed
@maruson08
maruson08 deleted the hotfix/v2.1.0-deployment-propagation branch September 25, 2026 14:57
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.

🚨[Hotfix] Tolerate Cloudflare alias propagation

1 participant