Conversation
- Treat BUILDING/QUEUED/INITIALIZING as transitional (pass, not fail) since Vercel keeps the previous READY deployment serving traffic - Emit ctx.fail() in per-project catch blocks instead of just logging, so failures are never silently swallowed as success - Add post-loop fallback for zero checked projects - Cap iteration to first 10 projects to match monitoring-alerting check and avoid Vercel rate limits - Remove unused VercelDeployment import Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
CANCELED deployments don't take down the app — Vercel keeps serving the previous READY deployment. Also removed unreachable checkedCount guard since the loop always executes at least once (projects is guaranteed non-empty at that point). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…onal CANCELED is a terminal state, not in-progress. Remove from transitionalStates and handle as its own branch with medium severity, consistent with monitoring-alerting.ts treating it as a failure. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
feat(vercel): add App Availability check
PR SummaryMedium Risk Overview Registers the new Reviewed by Cursor Bugbot for commit fe3c497. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
🎉 This PR is included in version 3.18.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
2 participants
This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.