@vexor-push/code-push-cli

PNPM-safe CLI for self-hosted CodePush Server releases.

Create or join your workspace in the admin UI first. The default CLI login opens the CodePush Server token page and saves the pasted access key locally.

pnpm add -g @vexor-push/code-push-cli
vexor-codepush login
vexor-codepush apps
vexor-codepush deployments --app CodexSmokeTest-iOS
vexor-codepush app add --name CodexSmokeTest-iOS --os ios
vexor-codepush deployment add --app CodexSmokeTest-iOS --name Staging

You can also run commands without global install:

pnpm dlx @vexor-push/code-push-cli login
pnpm dlx @vexor-push/code-push-cli apps

Release a prepared bundle directory:

vexor-codepush release \
  --app CodexSmokeTest-iOS \
  --deployment Staging \
  --target "*" \
  --contents build/ota-ios \
  --description "Smoke OTA release"

Bundle and release a React Native app:

vexor-codepush release-react \
  --app CodexSmokeTest-iOS \
  --platform ios \
  --deployment Staging \
  --target "*"

By default, release-react builds into build/ota-ios or build/ota-android, uploads the bundle, and then removes that generated folder after a successful release. If you pass --outputDir, the CLI keeps that custom directory.

If the server accepts the upload as a background job, the CLI waits for the job to finish and then prints the final result. That avoids long-running release requests getting cut off by Cloudflare-style proxy timeouts.

Auth options:

• vexor-codepush login opens the CodePush Server login/token page, then asks you to paste the generated access key.
• vexor-codepush login --token <access-key> saves an existing access key directly.
• For CI/CD, create an access key in Admin UI and use vexor-codepush login --token <access-key> or CODEPUSH_TOKEN=<access-key>.
• Account/password login is disabled by default. It remains available only for break-glass admin access with CODEPUSH_ALLOW_PASSWORD_LOGIN=1.
• Use the same account you registered in the admin UI / code-push-server.
• vexor-codepush status shows the saved session.
• vexor-codepush logout removes the saved session.
• CODEPUSH_TOKEN=<jwt-or-access-key> still works as a per-command override.
• --serverUrl https://app.vexor.one
• --workspaceId <workspace-id> scopes app/release/deployment commands to one workspace. You can also set CODEPUSH_WORKSPACE_ID.