Overview

Once your app has been configured to query for updates against the Turbopush server, you can begin releasing updates to it. In order to provide both simplicity and flexibility, the Turbopush CLI includes three different commands for releasing updates:

1. General - Releases an update to the Turbopush server that was generated by an external tool or build script (e.g. a Gulp task, the react-native bundle command). This provides the most flexibility in terms of fitting into existing workflows, since it strictly deals with Turbopush-specific step, and leaves the app-specific compilation process to you.

2. React Native - Performs the same functionality as the general release command, but also handles the task of generating the updated app contents for you (JS bundle and assets), instead of requiring you to run both react-native bundle and then turbopush release.

3. Expo - Performs the same functionality as the general release command, but specifically optimized for Expo applications with automatic detection of project configuration and support for Expo-specific features like Hermes.

Which of these commands you should use is mostly a matter of requirements and/or preference. However, we generally recommend using the relevant platform-specific command to start (since it greatly simplifies the experience), and then leverage the general-purpose release command if/when greater control is needed.

NOTE: Only the 50 most recent releases in a deployment can be discovered and downloaded by the clients.