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,
140
140
it's time to instantly release them!
141
141
142
-
The easiest way to do this is to use the `release-nativescript` command in our CodePush CLI.
142
+
The easiest way to do this is to use the `release-nativescript` command in our CodePush CLI. Its (most relevant) options are:
143
+
144
+
|param|alias|default|description
145
+
|---|---|---|---
146
+
|deploymentName|d|Staging|Deploy to either "Staging" or "Production".
147
+
|description|des||Description of the changes made to the app with this release.
148
+
|targetBinaryVersion|t||Semver expression that specifies the binary app version(s) this release is targeting (e.g. 1.1.0, ~1.2.3).
149
+
|rollout|r|100%|Percentage of users this release should be available to. The `%` sign is optional.
143
150
144
151
### iOS
145
152
146
153
```shell
147
154
nativescript-code-push release-nativescript <codepush-ios-appname> ios # deploy to Staging
148
155
nativescript-code-push release-nativescript <codepush-ios-appname> ios --d Production # deploy to Production (default: Staging)
149
156
nativescript-code-push release-nativescript <codepush-ios-appname> ios --targetBinaryVersion ~1.0.0 # release to users running any 1.x version (default: the exact version in Info.plist)
150
-
nativescript-code-push release-nativescript <codepush-ios-appname> ios --rollout 25 # percentage of users this release should be immediately available to (default: 100)
157
+
nativescript-code-push release-nativescript <codepush-ios-appname> ios --rollout 25 --description "My awesome iOS version"# percentage of users this release should be immediately available to (default: 100)
151
158
```
152
159
153
160
### Android
154
161
155
162
```shell
156
-
nativescript-code-push release-nativescript <codepush-ios-appname> android # deploy to Staging
157
-
nativescript-code-push release-nativescript <codepush-ios-appname> android --d Production # deploy to Production (default: Staging)
158
-
nativescript-code-push release-nativescript <codepush-ios-appname> android --targetBinaryVersion ~1.0.0 # release to users running any 1.x version (default: the exact version in AndroidManifest.xml)
163
+
nativescript-code-push release-nativescript <codepush-android-appname> android # deploy to Staging
164
+
nativescript-code-push release-nativescript <codepush-android-appname> android --d Production # deploy to Production (default: Staging)
165
+
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)
159
166
```
160
167
161
168
### Tips
162
169
> 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 bundle and uglify your app, it's all transparent to this plugin.
163
170
164
171
> 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.
165
172
166
-
There are a few options you may want to pass in:
167
-
168
-
TODO version nr as an additional argument?
173
+
### Did folks install the update?
174
+
Using a command like this will tell you how many apps have the update installed:
169
175
170
176
```shell
171
-
# Release an update that targets users running any 1.*.* binary, as opposed to everyone ("*") or a specific version (1.0.0)
0 commit comments