Reference
CLI
The public ReleaseKit command line surface.
The CLI creates ReleaseKit candidates. Hosted builders handle checkout, build, signing, artifact upload, and logs.
Install
npm install -g @sandbox-technologies/release-kitYou can also run commands with npx @sandbox-technologies/release-kit@latest.
Commands
| Command | Purpose |
|---|---|
release-kit login | Sign in and select the active project |
release-kit list | List projects available to the local CLI session |
release-kit select [project] | Change the active project |
release-kit whoami | Show the active project |
release-kit preview | Create an artifact-only Preview candidate from the current branch |
release-kit publish production | Create a gated Production candidate and converge Nightly users to the final build |
release-kit publish nightly | Create a gated Nightly / Early Access prerelease candidate |
release-kit apple setup | Use downloaded dashboard credentials to finish Apple signing setup on macOS |
release-kit logout | Remove local CLI credentials |
release-kit doctor | Check local CLI wiring |
release-kit completion <shell> | Print shell completion scripts for Tab suggestions |
Examples
release-kit loginrelease-kit publish productionrelease-kit publish nightly --minorrelease-kit preview# Download setup credentials from the ReleaseKit dashboard first
npx -y @sandbox-technologies/release-kit@latest apple setuprelease-kit completion zsh > ~/.zsh/completions/_release-kitpreview uses the current git branch, current commit, and an automatic timestamped version. publish asks for a patch, minor, or major bump unless you pass one as a flag.
Production and Nightly publish commands update the configured app version file, commit that bump, push it to the selected branch, then create the ReleaseKit candidate from the pushed commit. Production approval also publishes the final build on the Nightly channel. The next Nightly publish uses that final build as its baseline, so Nightly only starts a new prerelease train when you explicitly publish one.
For CI, set RELEASE_KIT_TOKEN to a project API key instead of using browser login.
Options
| Option | Description |
|---|---|
--patch | Patch bump for Production or Nightly |
--minor | Minor bump for Production or Nightly |
--major | Major bump for Production or Nightly |
--branch | Source branch to build. For Production or Nightly, check out this branch before running publish. |
--commit | Source commit SHA for Preview or advanced already-versioned Production/Nightly candidates |
--no-version-commit | Advanced: skip the Production/Nightly version commit when the selected commit already contains the app version |
--release-kit-url | ReleaseKit API URL |
--yes | Skip confirmation prompts |
Safety checks
ReleaseKit applies lane policy on the server.
| Check | What ReleaseKit prevents |
|---|---|
| Version policy | Publishing outside the patch/minor/major flow |
| Artifact policy | Promoting before required artifacts exist |
| Branch policy | Publishing a branch into the wrong lane |
| Latest commit | Promoting a stale Production commit |
| Approval | Updating Production or Nightly without human approval |
Preview candidates are artifact-only and never update an app update feed.