{"slug":"business/release-readiness","title":"Release Readiness Playbook","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/release-readiness.mdx","bytes":1583,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nUse this playbook for any meaningful production release across frontend, Workers, schema, or connector behavior.\n\n## Scope The Release\n\nIdentify which surfaces are changing:\n\n- `apps/web`\n- one or more `services/*`\n- `packages/*`\n- `sql-migrations/`\n- Cloudflare config or secrets\n\n## Before The Release Window\n\n1. Confirm owner, reviewer, and rollback owner.\n2. Confirm the exact user flows or tenants affected.\n3. Review schema compatibility and rollout order.\n4. Decide whether the release is:\n   - code only\n   - config only\n   - migration plus code\n\n## Pre-Release Checklist\n\n- validation commands pass\n- secrets and env vars are present in the target environment\n- smoke-test plan is written down\n- rollback path is known\n- incident contact path is ready if impact occurs\n\n## Release Execution\n\n1. Deploy in dependency order.\n2. Keep migrations additive where possible.\n3. Verify health checks immediately after deploy.\n4. Run the agreed smoke tests on critical routes and tenant-scoped flows.\n\n## Post-Release Monitoring\n\nWatch for one stability window:\n\n- 5xx rate\n- queue backlog and DLQ depth\n- auth and tenant-resolution errors\n- webhook verification failures\n- connector sync regressions\n\n## Exit Criteria\n\n- deployment is healthy\n- smoke tests pass\n- no unexpected DLQ or retry spike\n- rollback is no longer likely\n\n## Related Docs\n\n- [../runbooks/deployment-and-rollback.md](../runbooks/deployment-and-rollback.md)\n- [../runbooks/incident-response.md](../runbooks/incident-response.md)\n- [../GO_LIVE_CHECKLIST.md](../GO_LIVE_CHECKLIST.md)\n"}