ReleaseKit
Dashboard

Reference

CLI

The public ReleaseKit command line surface.

The CLI creates ReleaseKit candidates. Hosted builders handle checkout, build, signing, artifact upload, and logs.

Install

install
npm install -g @sandbox-technologies/release-kit

You can also run commands with npx @sandbox-technologies/release-kit@latest.

Commands

CommandPurpose
release-kit loginSign in and select the active project
release-kit listList projects available to the local CLI session
release-kit select [project]Change the active project
release-kit whoamiShow the active project
release-kit previewCreate an artifact-only Preview candidate from the current branch
release-kit publish productionCreate a gated Production candidate and converge Nightly users to the final build
release-kit publish nightlyCreate a gated Nightly / Early Access prerelease candidate
release-kit apple setupUse downloaded dashboard credentials to finish Apple signing setup on macOS
release-kit logoutRemove local CLI credentials
release-kit doctorCheck local CLI wiring
release-kit completion <shell>Print shell completion scripts for Tab suggestions

Examples

login
release-kit login
production
release-kit publish production
nightly
release-kit publish nightly --minor
preview
release-kit preview
apple signing
# Download setup credentials from the ReleaseKit dashboard first
npx -y @sandbox-technologies/release-kit@latest apple setup
tab completion
release-kit completion zsh > ~/.zsh/completions/_release-kit

preview 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

OptionDescription
--patchPatch bump for Production or Nightly
--minorMinor bump for Production or Nightly
--majorMajor bump for Production or Nightly
--branchSource branch to build. For Production or Nightly, check out this branch before running publish.
--commitSource commit SHA for Preview or advanced already-versioned Production/Nightly candidates
--no-version-commitAdvanced: skip the Production/Nightly version commit when the selected commit already contains the app version
--release-kit-urlReleaseKit API URL
--yesSkip confirmation prompts

Safety checks

ReleaseKit applies lane policy on the server.

CheckWhat ReleaseKit prevents
Version policyPublishing outside the patch/minor/major flow
Artifact policyPromoting before required artifacts exist
Branch policyPublishing a branch into the wrong lane
Latest commitPromoting a stale Production commit
ApprovalUpdating Production or Nightly without human approval

Preview candidates are artifact-only and never update an app update feed.