RELEASE ENGINEERING
Deployment
Deploy changes safely with environment validation, smoke testing, and rollback planning.
Production stability and security notice
Development changes must preserve working functionality, Provider isolation, role-based access, HIPAA auditability, released Mobile compatibility, and integration stability. Never deploy AI-generated or unreviewed code directly to production.
Pre-Deployment Checklist
- Type checking passes.
- Production build passes.
- Environment variables are present and correct.
- Manual SQL has been reviewed, backed up, and scheduled where required.
- Prisma Generate was run after schema changes.
- Provider isolation and role checks were tested.
- External integration environment is correct.
- Rollback steps are documented.
Post-Deployment Checks
| Topic | Standard |
|---|---|
| Authentication | Users can log in and Provider scope is correct. |
| Core workflows | Critical daily workflows still operate. |
| API health | Routes respond without unexpected errors. |
| Database | New fields, indexes, and relations behave as expected. |
| Audit | Relevant actions create audit evidence. |
| Integrations | Sandata, storage, email, and notifications use the correct environment. |
| Mobile compatibility | Released Mobile versions continue to work with the API. |