From b43d52bc732f325e4f85db1b8b6dafce445f67b3 Mon Sep 17 00:00:00 2001 From: Ruben Rios Date: Tue, 17 May 2016 16:12:15 -0700 Subject: [PATCH 1/4] Bumping version Bumping the minor version to release PhoneGap support via the release-cordova command as well as some bug fixes. --- cli/package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cli/package.json b/cli/package.json index 4b95dad6..a43f2dc4 100644 --- a/cli/package.json +++ b/cli/package.json @@ -1,6 +1,6 @@ { "name": "code-push-cli", - "version": "1.10.0-beta", + "version": "1.10.1-beta", "description": "Management CLI for the CodePush service", "main": "script/cli.js", "scripts": { From 7df0480a9a27c8e2e28d142262faa0da74bda0a7 Mon Sep 17 00:00:00 2001 From: rub8n Date: Wed, 18 May 2016 10:52:42 -0700 Subject: [PATCH 2/4] Bumping to 1.11.0-beta and code-push dependency to 1.9.0 --- cli/package.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cli/package.json b/cli/package.json index a43f2dc4..11b3a6c8 100644 --- a/cli/package.json +++ b/cli/package.json @@ -1,6 +1,6 @@ { "name": "code-push-cli", - "version": "1.10.1-beta", + "version": "1.11.0-beta", "description": "Management CLI for the CodePush service", "main": "script/cli.js", "scripts": { @@ -28,7 +28,7 @@ "base-64": "^0.1.0", "chalk": "^1.1.0", "cli-table": "^0.3.1", - "code-push": "1.8.0-beta", + "code-push": "1.9.0-beta", "email-validator": "^1.0.3", "gradle-to-js": "0.1.0", "moment": "^2.10.6", From 02a51a1040675626592d4a14194b6a6b742dbd0c Mon Sep 17 00:00:00 2001 From: rub8n Date: Wed, 18 May 2016 11:54:26 -0700 Subject: [PATCH 3/4] Updates the CLI's readme to call out phonegap and proxy support --- cli/README.md | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/cli/README.md b/cli/README.md index 7d3c2ab0..c7fd5250 100644 --- a/cli/README.md +++ b/cli/README.md @@ -64,7 +64,22 @@ code-push login This will launch a browser, asking you to authenticate with either your GitHub or Microsoft account. This will generate an access key that you need to copy/paste into the CLI (it will prompt you for it). You are now successfully authenticated and can safely close your browser window. -If at anytime you want to determine if you're already logged in, you can run the following command to display the e-mail address associated with your current authentication session, and which identity providers your account is linked to (e.g. GitHub): +By default, the login command supports proxies and will look for system environment variables (`HTTPS_PROXY` or `HTTP_PROXY` for HTTPS or HTTP traffic respectively) to establish proxy connections. + +CodePush specific proxy settings are also supported and can be set using the `--proxy` flag: + +``` +code-push login --proxy proxyUrl +``` + + +Alternatively, proxy functionality can be disabled (system environment variables are suppressed and CodePush ignores proxy settings) by passing the `--noproxy` flag: + +``` +code-push login --noproxy +``` + +If at any time you want to determine if you're already logged in, you can run the following command to display the e-mail address associated with your current authentication session, which identity providers your account is linked to (e.g. GitHub) and any previously set proxy: ```shell code-push whoami @@ -245,7 +260,7 @@ Once your app has been configured to query for updates against the CodePush serv 2. [React Native](#releasing-updates-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 `code-push release`. -3. [Cordova](#releasing-updates-cordova) - Performs the same functionality as the general release command, but also handles the task of preparing the app update for you, instead of requiring you to run both `cordova prepare` and then `code-push release`. +3. [Cordova](#releasing-updates-cordova) - Performs the same functionality as the general release command, but also handles the task of preparing the app update for you, instead of requiring you to run both `cordova prepare` (or `phonegap build` for PhoneGap instances) and then `code-push release`. 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. @@ -483,7 +498,7 @@ code-push release-cordova The `release-cordova` command is a Cordova-specific version of the "vanilla" [`release`](#releasing-app-updates) command, which supports all of the same parameters (e.g. `--mandatory`, `--description`), yet simplifies the process of releasing updates by performing the following additional behavior: -1. Running the `cordova prepare` command in order to generate the [update contents](#update-contents-parameter) (`www` folder) that will be released to the CodePush server. +1. Running the `cordova prepare` (or `phonegap build` for PhoneGap instances) command in order to generate the [update contents](#update-contents-parameter) (`www` folder) that will be released to the CodePush server. 2. Inferring the [`targetBinaryVersion`](#target-binary-version-parameter) of this release by using the version name that is specified in your project's `config.xml` file. From 87a5a0b891e47b10fce2d5d182448b5918094262 Mon Sep 17 00:00:00 2001 From: Ruben Rios Date: Wed, 18 May 2016 15:21:49 -0700 Subject: [PATCH 4/4] Tweaks PhoneGap support comment --- cli/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cli/README.md b/cli/README.md index c7fd5250..501c3947 100644 --- a/cli/README.md +++ b/cli/README.md @@ -260,7 +260,7 @@ Once your app has been configured to query for updates against the CodePush serv 2. [React Native](#releasing-updates-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 `code-push release`. -3. [Cordova](#releasing-updates-cordova) - Performs the same functionality as the general release command, but also handles the task of preparing the app update for you, instead of requiring you to run both `cordova prepare` (or `phonegap build` for PhoneGap instances) and then `code-push release`. +3. [Cordova](#releasing-updates-cordova) - Performs the same functionality as the general release command, but also handles the task of preparing the app update for you, instead of requiring you to run both `cordova prepare` (or `phonegap prepare`) and then `code-push release`. 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. @@ -498,7 +498,7 @@ code-push release-cordova The `release-cordova` command is a Cordova-specific version of the "vanilla" [`release`](#releasing-app-updates) command, which supports all of the same parameters (e.g. `--mandatory`, `--description`), yet simplifies the process of releasing updates by performing the following additional behavior: -1. Running the `cordova prepare` (or `phonegap build` for PhoneGap instances) command in order to generate the [update contents](#update-contents-parameter) (`www` folder) that will be released to the CodePush server. +1. Running the `cordova prepare` (or `phonegap prepare`) command in order to generate the [update contents](#update-contents-parameter) (`www` folder) that will be released to the CodePush server. 2. Inferring the [`targetBinaryVersion`](#target-binary-version-parameter) of this release by using the version name that is specified in your project's `config.xml` file.