Release Runbooks

ReleaseMind attaches a runbook to each GitHub release post so the dashboard, SI CLI, and automation API all evaluate the same release gates before final publish.

Default gates

The default GitHub release runbook tracks:

• patch version bump
• validation and tests
• documentation updates
• release approval
• GitHub draft creation
• final publish
• post-publish verification

Required pre-publish gates must be complete before the dashboard enables final GitHub publishing.

Dashboard

The post detail page shows the runbook checklist next to the GitHub release status. Completing a gate records the actor, timestamp, and evidence text.

SI CLI

SI operators can inspect and update the same runbook from si orbit releasemind:

si orbit releasemind runbook status \
  --repo Aureuma/example-repo \
  <post-id> \
  --json

si orbit releasemind runbook complete \
  --repo Aureuma/example-repo \
  <post-id> \
  tests \
  --evidence "cargo test -p rm-api runbook"

Evidence

Evidence should reference reproducible commands, dashboard checks, deployment IDs, or release URLs. Use SI Fort for runtime secret access during validation; do not paste secret values into runbook evidence.