Platform
Integrations
GitHub, SI CLI, automation, billing, Launch Studio, and Google Play integrations.
Edit this pageIntegrations
ReleaseMind relies on upstream provider integrations for repository metadata, publishing targets, billing gates, and release automation.
GitHub App
The GitHub App is the source of repository inventory, release metadata, tags, commits, and GitHub Release publishing. Install it on the owner that contains the release repository, then use Repos to link the repo into ReleaseMind.
SI CLI
si orbit releasemind is a thin client for the ReleaseMind backend. It supports interactive auth, repo linking, release create/view/publish, runbook plan/status/gate completion, automation token management, and Play planning/publish commands.
Automation API
Automation tokens use the same backend policy as the dashboard and CLI. Repo-scoped tokens should be used for CI:
POST /api/automation/releases/prepareGET /api/automation/releases/statusPOST /api/automation/releases/publishPOST /api/automation/releases/play/planPOST /api/automation/releases/play/publish
Billing
Stripe and GitHub Marketplace signals are normalized into ReleaseMind billing gates. A billing conflict pauses gated workflows until the account resolves one active billing source.
Launch Studio
Launch Studio generates social launch drafts from release context and stores them as ReleaseMind posts so teams can iterate before publishing externally.
App Studio
App Studio plans Google Play release notes, rollout settings, and publish edits. ReleaseMind does not build Android artifacts; it orchestrates planning and Play Console publish requests from provided package metadata and artifacts.
Secret handling
Use SI Fort for repo runtime secrets and automation token storage. ReleaseMind production secrets are resolved through Fort-backed Viva deploys.