From 8ba6d26dd32b5f570c303664f6d6bf4403d82f9d Mon Sep 17 00:00:00 2001 From: Adam Date: Fri, 2 Oct 2026 14:35:24 +0000 Subject: [PATCH] docs(operations): exact frontend rollback commands Spell out the Vercel project, how to find the live and previous production deployments, the rollback command, the VPS helper that wraps them, and the promote step Vercel requires before new deploys go live again. Co-Authored-By: Claude Opus 5.5 (1M context) --- docs/operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/operations.md b/docs/operations.md index 9e8d4f149..98aa238c3 100644 --- a/docs/operations.md +++ b/docs/operations.md @@ -172,7 +172,7 @@ Vercel build variables for Sentry source maps: `SENTRY_AUTH_TOKEN` (an organizat Choose rollback before changing production: -- Frontend: promote the previous known-good Vercel production deployment, or revert the commit on `main` and let Vercel redeploy. +- Frontend: promote the previous known-good Vercel production deployment (about 10 seconds), or revert the commit on `main` and let Vercel redeploy (one to two minutes). The Vercel project is `debate-navigator`. `vercel inspect debate.pi-stack.org` shows the live deployment, `vercel ls debate-navigator --environment production --status READY` lists the earlier ones, and `vercel rollback --yes` switches back. On Adam's VPS, `~/ops/rollback/rollback vercel debate-navigator` does all three. After a rollback, Vercel stops putting new `main` deployments live until one is promoted with `vercel promote `, so promote the fixed deployment once it is ready. A frontend rollback does not touch Supabase: if the bad change came with a migration or function deploy, the old frontend must still work with the new backend. - Edge Function: retain the deployed source or artifact baseline and its environment assumptions. - Migration: prefer forward corrective migrations. Do not assume an irreversible schema or data change can be rolled back. - Configuration: record the prior value without exposing secrets.