Authenticate first
Run si orbit releasemind auth login and complete the browser login.
Confirm the session with si orbit releasemind auth status --json.
The CLI uses the same ReleaseMind backend session as the dashboard.
Link and inspect the repo
Run si orbit releasemind doctor OWNER/REPO --json to check GitHub App access.
Use si orbit releasemind repo ensure-link OWNER/REPO --json when the repo is visible through the app but not linked yet.
If the repo is missing, update the GitHub App installation and resync in Repos.
Create and publish
Create a reviewed draft with si orbit releasemind release create v1.2.0 -R OWNER/REPO --draft --json.
Use --notes when you already have approved release notes and want ReleaseMind to use them directly.
Inspect release gates with si orbit releasemind runbook status -R OWNER/REPO POST_ID --json.
Record reproducible gate evidence with si orbit releasemind runbook complete -R OWNER/REPO POST_ID tests --evidence "corepack pnpm check".
Publish with si orbit releasemind release publish -R OWNER/REPO POST_ID --json.
Verify the result
Run si orbit releasemind release view -R OWNER/REPO POST_ID --json.
Confirm status is published and the release_url points to /releases/tag/<tag>.
If publishing is rerun, ReleaseMind returns the existing published release state.
Review and introspect
CLI releases should stay as reviewable as dashboard releases.
- Did you review the notes before publishing?
- Is the repo linked to the GitHub installation that owns the tags?
- Are required runbook gates complete with useful evidence?
- Does the returned release URL point at the expected tag?