Best for
- The routine deploys that should stay routine
- Releases with a schema change that needs extra care
- Keeping every release identically disciplined
What you give it
- The release candidate and the word to go
What you get back
- Gates run and respected before anything ships
- The update applied with the previous release preserved
- Migrations applied per your rules, and live verification after
How it works
- Runs your blocking gates: suite, build, any project-specific checks.
- Deploys the update by your documented procedure, preserving the prior release.
- Applies approved migrations at the documented point, logging results.
- Reloads services and verifies health, version and a smoke path.
- Stops and reports at the first failure, with the system's actual state.
Example
You: Deploy this week's release to production.
Result: Gates green, delta uploaded, one approved migration applied, services reloaded with the old release retained, health and version verified — summary filed, rollback path confirmed intact.
Limits — please read
- Unapproved schema changes stop the release — approval is upstream.
- It preserves the rollback path; having one is your procedure's job.
- Zero-downtime depends on your architecture, not this skill.