Skip to main content

Release Readiness

Featured

Reads a release candidate and its diff, checks migrations, canary coverage, error budget and rollback plan, and returns a ship-or-hold verdict with each blocking risk and its owner.

How it works​

  1. Runs when: a release candidate is cut, or you ask for a verdict on one.
  2. Inventories the release: every pull request, the service it touches, and whether it carries a migration, a config change or code alone.
  3. Answers four gates: migrations (one subagent per migration, checking whether it can be undone and whether anything still reads what it removes), canary coverage, error budget, and rollback plan.
  4. Separates blocking from advisory: a risk blocks only when shipping produces an outcome that cannot be undone inside the rollback window.
  5. You get: ship or hold, with every risk stated as outcome, owning team and evidence. A gate it could not answer is reported as unanswered, not as passed.

What it needs​

  • GitHub: read the release's pull requests and migrations
  • Datadog: read canary metrics and the error budget
  • PagerDuty: read on-call for the rollback owner