code-push 1.5.0-beta

v1.5.0-beta

on Node.js NPM

This release introduces the new installation metrics feature to the CLI, which let's you identify the total number of installations that every update has received, as well as how many active installations it currently has (i.e. this is the version that an end-user would see when running your app). Note that this feature depends on the 1.5.0+ release of the Cordova plugin and the 1.6.0+ release of the React Native plugin, since those include the necessary telemetry. So if you want to begin viewing installation metrics, you'll need to upgrade your respective plugin and submit a new app store update (sorry!). This update is now available on NPM and can be installed immediately via npm i -g code-push-cli@latest.

New Features

1. The deployment ls and deployment history commands now display basic metrics for each CodePush release, which help you understand: how many total (and pending) installations each release has, how many of those installations are active, and whether or not any client-side rollbacks have occurred (i.e. because you released an update that crashed). Hopefully no one release an update via CodePush that is broken, but if you do, the plugin will make sure that your end-users are seamlessly rolled back, and the CLI will let you know about the failure so that you can respond accordingly! (e.g. by doing a server-side rollback to prevent other users from getting it).

Bug Fixes

1. The release command wasn't properly rejecting *.ipa and *.apk files, which made it possible for devs to mistakenly attempt to release a binary file, only to have it fail to install, since neither the Cordova or React Native plugin expects that.
2. We heard a lot of feedback about confusion around the "package" and "appStoreVersion" parameters of the release command. Because of this, we have renamed them to "updateContentsPath" and "targetBinaryVersion", respectively. These parameters are positional so their names wouldn't break existing behavior, but we hope that the description and examples displayed within the CLI are now a little more intuitive.

Breaking Changes

1. The Deployment Key column within the deployment ls command is now hidden by default, since it took up a lot of space, and wasn't regularly needed. To display this value, simply pass the new -k (or --displayKeys) flag when calling deployment ls.