CLIReleasing Updates
Expo Release
Release OTA updates for Expo apps using the Turbopush CLI — automatically bundles with Hermes support and deploys to your deployment.
Auto-bundles and releases Expo apps with Hermes support.
npx turbopush release-expo <appSlug> <platform> <targetBinaryVersion>yarn turbopush release-expo <appSlug> <platform> <targetBinaryVersion>pnpm turbopush release-expo <appSlug> <platform> <targetBinaryVersion>Example
npx turbopush release-expo myapp-ios ios "1.0.0"yarn turbopush release-expo myapp-ios ios "1.0.0"pnpm turbopush release-expo myapp-ios ios "1.0.0"Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
appSlug | Yes | - | The app slug from npx turbopush app add |
platform | Yes | - | android or ios |
targetBinaryVersion | Yes | - | Version found in app.json or app.config.js at build time. Supports semver ranges |
--deploymentName, -d | No | Staging | Target deployment |
--description, --des | No | - | "Change log" sent to the client, you can use it to describe the changes made to the app in this release and show it to the users if you want |
--disabled, -x | No | false | Prevent downloads; set to true to prevent clients from receiving the update until enabled |
--mandatory, -m | No | false | Mark as mandatory; set to true to require clients to install this update |
--noDuplicateReleaseError | No | false | If true, only warn (do not error) on duplicate content releases |
--rollout, -r | No | 100 | Percentage (1-100) of users who will receive this update |
--outputDir, -o | No | temp folder | Directory where the update bundle and metadata will be output |
--sourcemap, -s | No | false | If true, will generate sourcemaps |
--useHermes, -h | No | auto-detected | Force enable Hermes usage; auto-detected from config if omitted |
How is this guide?