You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once your app has been configured and distributed to your users, and you've made some code and/or asset changes,
161
-
it's time to instantly release them!
161
+
it's time to instantly unleash those changes onto your users!
162
+
163
+
> ⚠️ Make sure to create a *release build* first, so use the same command that you'd use for app store distribution, just don't send it to the AppStore. You can even Webpack and Uglify your app, it's all transparent to this plugin.
164
+
165
+
> 💁♂️ When releasing updates to CodePush, you do not need to bump your app's version since you aren't modifying the app store version at all. CodePush will automatically generate a "label" for each release you make (e.g. `v3`) in order to help identify it within your release history.
162
166
163
167
The easiest way to do this is to use the `release-nativescript` command in our CodePush CLI. Its (most relevant) options are:
164
168
165
169
|param|alias|default|description
166
170
|---|---|---|---
167
171
|deploymentName|d|"Staging"|Deploy to either "Staging" or "Production".
168
-
|description|des||Description of the changes made to the app with this release.
169
-
|targetBinaryVersion|t||Semver expression that specifies the binary app version(s) this release is targeting (e.g. 1.1.0, ~1.2.3).
172
+
|description|des|not set|Description of the changes made to the app with this release.
173
+
|targetBinaryVersion|t|`App_Resources`|Semver expression that specifies the binary app version(s) this release is targeting (e.g. 1.1.0, ~1.2.3). The default is the exact version in `App_Resources/iOS/Info.plist` or `App_Resources/Android/AndroidManifest.xml`.
170
174
|mandatory|m|not set|This specifies whether the update should be considered mandatory or not (e.g. it includes a critical security fix). This attribute is simply round tripped to the client, who can then decide if and how they would like to enforce it. This is flag, so its absence indicates an optional release.
nativescript-code-push release-nativescript <codepush-android-appname> android --targetBinaryVersion ~1.0.0 # release to users running any 1.x version (default: the exact version in AndroidManifest.xml)
189
193
```
190
194
191
-
> ⚠️ Make sure to create a *release build* first, so use the same command that you'd use for app store distribution, just don't send it to the AppStore. You can even Webpack and Uglify your app, it's all transparent to this plugin.
192
-
193
-
> 💁♂️ When releasing updates to CodePush, you do not need to bump your app's version since you aren't modifying the app store version at all. CodePush will automatically generate a "label" for each release you make (e.g. `v3`) in order to help identify it within your release history.
194
-
195
195
## CodePush CLI tricks
196
196
Here are a few commands you may find useful:
197
197
198
198
### Which releases did I create and what are the install metrics?
199
199
Using a command like this will tell you how many apps have the update installed:
0 commit comments