Repository navigation
Allow Cloudflare readiness checks to wait through propagation - #12
Merged
Merged
Conversation
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
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.
The staging deploy 41457815092 failed after Cloudflare accepted the Worker because
/healthzstill served the previous deployment marker during the 15-second readiness window. The new marker appeared afterward.Allow 12 retries at the existing 5-second interval for Worker and Pages readiness. Checks still require the exact deployment marker, stop after a bounded number of attempts, and retain per-request/body deadlines. Successful checks finish immediately.
Validation adds a 25-second propagation regression and retains the failure case for a persistently wrong version; full GitHub
pnpm verifyruns before staging is retried.