Updates And Upgrades
Updates should explain what changed, who is affected, whether migrations are required, and how buyers can safely upgrade.
On this page
Update docs model
| Page | Purpose |
|---|---|
| Changelog | Record user-visible product, docs, provider, schema, and operational changes. |
| Upgrade guide | Explain migration steps, env changes, provider dashboard changes, generated type refresh, and verification commands. |
| Breaking changes | Call out removed routes, renamed env vars, schema changes, provider behavior changes, and data repair needs. |
| Version policy | Explain how releases are named, what support includes, and when buyers should expect manual intervention. |
Upgrade checklist
- Read migration notes before pulling changes into a customized product.
- Review schema, env, provider, cron, and webhook changes before deploy.
- Regenerate generated types after Supabase changes.
- Run targeted tests and pnpm run quality.
- Smoke test auth, admin, billing, email, cron, and public content after upgrade.