Repository navigation
ci(router): accept a later successful web deploy that includes this commit - #165
Conversation
…ommit A newer push supersedes a queued web deploy in its concurrency group, so a router run waiting for its own commit's web deploy saw it cancelled and gave up (#162's router never shipped). Ship once any successful web deploy of this commit or a descendant exists; still refuse if this commit's own web deploy failed. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 34 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe push-only router workflow now waits for a successful web deployment for the same commit or a qualifying successful deployment from ChangesRouter deployment wait
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The router waits for a qualifying successful web deployment and times out after bounded polling. No concrete merge-blocking issue is established; it appears ready subject to normal checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the deploy queue, Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6316b05bbb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
All reported issues were addressed across 1 file
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
- Check out the revision whose web deploy succeeded (this commit or the later one that contains it), so router and pages always match. - Only look for a later deploy after this commit's own deploy was read and is not a failure; a transient lookup error just retries. - An identical SHA is accepted through the same path. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 0893a66. Configure here.
…nding Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Preview deployed!
This is a Cloudflare Workers preview version of this PR's build. |

Bug (from #154, mine)
The router waits for its own commit's web deploy. A newer push supersedes a queued web deploy in the
deploy-web-productiongroup, which keeps one pending run, so that run ends cancelled. The router then exits with "did not succeed". That's what happened to #162's router: it never shipped.Fix
The router ships once any successful web deploy includes this commit: its own, or a later
mainpush whose head isaheadof oridenticalto this commit (via the compare API). It still refuses if this commit's own web deploy actually failed (failure,timed_out,startup_failure). A cancelled run means it keeps waiting for a descendant. Manual dispatch is unchanged.actionlintis clean.🤖 Generated with Claude Code
Note
Medium Risk
Changes production deploy ordering and which git SHA the router ships; mis-handling compare or checkout could still desync router and web or block deploys.
Overview
Fixes router deploys that never shipped when this commit’s web deploy was cancelled because a newer push superseded it in the
deploy-web-productionconcurrency group.The wait step now proceeds once any successful
mainweb deploy includes this commit: own SHA on success, or the latest successful run whose head is ahead or identical per the compare API. It still fails fast if this commit’s own web run ended in failure, timed out, or startup failure. On success it writessteps.wait.outputs.shaand checkout uses that ref so the router deploy matches the web pages revision, not a router-only SHA that might be ahead or behind.Reviewed by Cursor Bugbot for commit b14f49b. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by cubic
Fixes the router deploy job so it ships once any successful web deploy includes this commit, instead of waiting only for its own commit's deploy.
Written for commit b14f49b. Summary will update on new commits.
Agent Relay sessions
claudesession1e2adfbe· opened viagh pr create· last active 2026-10-08