Release Management

Releases of the example service follow a checklist to make sure nothing is missed between a change being merged and it reaching production.

• Change reviewed and approved by a second engineer
• Automated test suite passing
• Deployed to the test environment and verified
• Release notes drafted
• Deployed to production and health checks confirmed green

Releases are batched on a regular cadence rather than deploying every merged change immediately, except for emergency patches which follow the separate process described in Emergency Patching Events.