Platform
Integrations
GitHub, automation, billing, 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.
CLI client contract
The /api/cli/** routes remain the backend contract for a future ReleaseMind CLI client. There is no currently published SI orbit client after the SI orbit extraction.
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.
billingConflict means competing paid providers only. A free Marketplace install
can coexist with Stripe paid status. Marketplace plan IDs are mapped through
RM_GITHUB_MARKETPLACE_FREE_PLAN_IDS and RM_GITHUB_MARKETPLACE_PAID_PLAN_IDS;
unknown Marketplace plan IDs remain access-only until explicitly mapped.
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.