Release Operations and Deployments
Run safe application releases, verify environment readiness, and know which commands and routes matter when something goes wrong.
Audience: Platform admins, release operators, and support leadsOwner: Platform OperationsUpdated March 2026Review cadence: MonthlyNext review: April 15, 2026
This guide is past its review date. Validate the workflow before relying on it operationally.
Deployment Surface
Production deployment is branch-driven and Vercel-backed. Releases should only promote reviewed, validated changes.
Primary references:
- `main` for release promotion
- `develop` for integration
- `docs/runbooks/deployment-vercel.md` for environment and workflow details
Required Verification Commands
Before approving release promotion, run the project validation set in the touched workspace:
If the release changes database shape, verify migration readiness before deployment.
- `npm run lint`
- `npm run typecheck`
- `npm test`
- `npm run build`
Production Validation Routes
After deployment, validate the highest-risk routes first:
- `/`
- `/pricing`
- `/signup`
- `/dashboard`
- `/dashboard/admin`
- `/s/:storeSlug`
- `/checkout`
Related Docs
- `/docs/admin-dashboard-and-operations`
- `/docs/support-operations-and-escalation`