chore: pause Vercel auto-deploy mid-term after 2 undiagnosed build failures - #289
Conversation
…ilures Two consecutive Vercel preview deployments failed (different deployment IDs, different commits) with only a generic "Deployment has failed" message. The exact same commits build cleanly via `pnpm run build` locally, and neither the GitHub Checks API nor `npx vercel inspect --logs` (requires an interactive account login not available here) surfaced any further detail — this looks platform-side, not a code regression. Vercel is not a required branch-protection check, so this was purely about stopping a noisy, undiagnosable failure status rather than unblocking anything. Disabled via vercel.json's documented `git.deploymentEnabled: false` (the standard, reversible, dashboard- free way to pause git-triggered deployments). GitHub Pages — already documented as the always-on fallback mirror — is promoted to primary in README.md/CLAUDE.md for the duration. TODO.md tracks re-enabling once someone with Vercel dashboard/CLI access diagnoses the cause. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 35 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. 📝 WalkthroughWalkthroughThe change disables Vercel Git deployments, makes GitHub Pages the primary always-on deployment, and documents the pause, its triggering failures, and conditions for re-enabling Vercel deployments. ChangesVercel deployment pause
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
🏁 CodeAnt Quality Gate ResultsCommit: ✅ Overall Status: PASSEDQuality Gate Details
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Around line 38-41: Update the surrounding README introduction to remove the
claim that both hosted builds auto-deploy from main, keeping the GitHub Pages
primary deployment statement and Vercel paused status consistent with the
deployment table and tip.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: be6e4aa7-c02a-47e6-97fd-f6d53f91801e
📒 Files selected for processing (4)
CLAUDE.mdREADME.mdTODO.mdvercel.json
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Root-caused the 2 Vercel build failures that prompted the mid-term pause: not a platform issue, but a real missing-export bug (services/ai/localEmbeddingService.ts imported ensureInferencePool() from workerBusManager.ts, which never actually defined it — invisible to Vitest because the consumer test mocks the whole module). The fix landed in the worker-generation-consolidation PR chain (PR #288). Reverts git.deploymentEnabled to the default (enabled) now that the actual cause is fixed and verified via a clean local `build:edge` reproduction of Vercel's exact build command. TODO.md's entry updated from "paused, cause unknown" to a resolved write-up, including the `pnpm run build` vs `pnpm run build:edge` command-mismatch lesson that delayed finding this. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…EAD, not main) The previous commit's `git checkout -- README.md CLAUDE.md` restored from this branch's own HEAD (which still had the "paused" wording from the first commit), not from main — so the pause note survived uncommitted. Re-applied via `git checkout main -- ...` this time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
package.json bumped; src-tauri/tauri.conf.json, src-tauri/Cargo.toml, src-tauri/Cargo.lock (workspace-member entry, no checksum to break), and public/sw.js's APP_VERSION synced via the existing sync-tauri-version.mjs / sync-sw-version.mjs scripts plus one direct lockfile edit. README version badge updated. New CHANGELOG.md [1.24.3] entry finalizes the Unreleased worker-generation consolidation section: corrects the stacked-PR count (4 -> 5, #286-288 + #290-291), folds in independent #289 (Vercel auto-deploy pause), and adds two additional fixes from this session's merge-queue recovery (abort-listener leak in duckdbClient.ts, pool re-registration failure guards in workerBusManager.ts) that weren't yet documented. Tag creation and GitHub Release publishing follow in a separate step, per explicit maintainer authorization for this recovery. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
1 participant
Summary
vercel.json: addedgit.deploymentEnabled: false— the documented, reversible, dashboard-free way to pause git-triggered Vercel deployments.README.md/CLAUDE.md: promoted GitHub Pages to primary live target for the duration; noted Vercel is paused and why.TODO.md: tracked entry to re-enable once someone with Vercel dashboard/CLI access diagnoses the root cause.Why: two consecutive Vercel preview deployments failed (different deployment IDs, different commits — see PR #288) with only a generic "Deployment has failed" message. The exact same commits build cleanly locally via
pnpm run build, and neither the GitHub Checks API nornpx vercel inspect --logs(needs an interactive account login I don't have here) surfaced further detail — this looks platform-side rather than a code regression.Vercel is not a required branch-protection check (confirmed: only Security Audit, Build, Quality Gate ×2 are required), so this doesn't unblock any merge gate — it was purely to stop a noisy, undiagnosable failure status from showing up on every PR. GitHub Pages is already documented as the always-on fallback mirror, so live availability is unaffected.
Test plan
vercel.jsonvalidated as well-formed JSONpnpm exec vitest run tests/unit/checkDocMetrics.test.ts— 21/21 passing (canonical-Vercel-URL drift gate unaffected, since the URL itself didn't change)gh api .../branches/main/protectionthatVercelis not inrequired_status_checks.contexts🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation
Infrastructure