chore: disable maintenance mode post-release#2036
Conversation
The decomplexify cutover migrations + backfill completed successfully at 2026-05-14 19:50 UTC. BE PR #747 + FE PR #1984 merged. Flipping maint off so users come out of the /maintenance redirect. Why this needs a separate PR: PR #1985 (enable maint) was merged into main but never synced to dev. When PR #1984 merged dev -> main, the 3-way merge kept main's true (dev didn't touch the line).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe maintenance configuration default for full-app redirection is toggled from enabled to disabled. The ChangesMaintenance Feature Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Comment |
Code-analysis diffPainscore total: 5648.74 → 5648.74 (0) |
🧪 UI test report — ✅ all greenSuites
📊 Coverage (unit)
⏱ 10 slowest test cases
|
URGENT — post-cutover maint-off
The decomplexify cutover (PR #1984 + peanut-api-ts#747) is live. Flipping
enableFullMaintenanceback tofalse.Why this is separate: PR #1985 (maint=true) was merged into
mainonly, never back-merged todev. So PR #1984's dev→main merge kept main'strue(3-way merge: dev didn't change the line, main did → result keeps main's value).One-line change. Merge ASAP.