Release & rollback
Checklists, health probes, progressive rollout—rollback must cover version, config, and whether migrations are reversible.
Category · Release & change
5 skills Category 16 of 20
This category covers how change reaches production safely: standard release/rollback playbooks, blue/green and canary with metric gates, feature-flag lifecycles, and DR drills. Strongly related to database migrations and backups for reversible changes.
In the hub it sits in the continuous delivery band. The five entries match the main hub.
Checklists, health probes, progressive rollout—rollback must cover version, config, and whether migrations are reversible.
Two environments, instant traffic switch, DB compatibility—fast cutback; mind sessions and connection pools.
Small slice with error/latency gates; automatic or manual promotion; quick removal of bad canaries.
Per-user/tenant rollout, defaults, and cleanup—avoid long-lived half-on flags that rot code paths.
Periodic regional-failure drills with measured RTO/RPO; feed action items into runbooks.