chore(release): 0.0.11 [ci skip]

salesforcecli · Jul 12, 2021 · 5383958 · 5383958
1 parent 1d4b10d
commit 5383958
Show file tree

Hide file tree

Showing 4 changed files with 106 additions and 48 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,6 +2,13 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+### [0.0.11](https://github.com/salesforcecli/cli/compare/v0.0.10...v0.0.11) (2021-07-12)
+
+
+### Bug Fixes
+
+* windows path issues ([#13](https://github.com/salesforcecli/cli/issues/13)) ([1d4b10d](https://github.com/salesforcecli/cli/commit/1d4b10d48100c25d1100f163276e1212ec7c5908))
+
 ### [0.0.10](https://github.com/salesforcecli/cli/compare/v0.0.9...v0.0.10) (2021-07-08)
 
 

diff --git a/README.md b/README.md
@@ -247,54 +247,58 @@ USAGE
   $ sf env open [--json] [-p <value>] [-r] [-e <value>] [--browser <value>]
 
 FLAGS
-  -e, --target-env=<value>
-      Specify the login user or alias that’s associated with the environment. For scratch orgs, the login user is
-      generated by the command that created the scratch org. You can also set an alias for the scratch org when you create
-      it.
+  -e, --target-env=<value>  Environment login user or alias to open.
+  -p, --path=<value>        Path to append to the end of the login URL.
+  -r, --url-only            Display the URL, but don’t launch it in a browser.
+  --browser=<value>         Browser in which to open the environment.
 
-      For Dev Hubs, sandboxes, and production orgs, specify the alias you set when you logged into the org with "sf
-      login".
-
-  -p, --path=<value>
-      Each of your environments is associated with an instance URL, such as https://<mydomian>.my.salesforce.com. To open
-      a specific web page at that URL, specify the portion of the URL after "<URL>/" with the --path flag, such as
-      /apex/YourPage to open a Visualforce page.
-
-  -r, --url-only
-
-  --browser=<value>
-      Specify a browser by its app name according to your operating system. For example, Chrome’s app name is "google
-      chrome" on macOS, "google-chrome" on Linux and "chrome" on Windows. So to open an environment in Chrome on macOS,
-      specify --browser "google chrome". If you don’t specify --browser, the environment opens in your default browser.
-
-      For convenience, "chrome", "firefox", and "edge" are mapped to the OS specific app name.
-
-  --json
-      format output as json
+GLOBAL FLAGS
+  --json  format output as json
 
 DESCRIPTION
+  Open an environment in your web browser.
+
   You can open the following types of environments in a web browser: scratch orgs, sandboxes, Dev Hubs, and production
   orgs.
 
-  If you run the command without flags, it attempts to open your default environment in your default web browser.
+  If you run the command without flags, it attempts to open your default environment in your default web browser. Run
+  "sf env list" to view your default environment.
+
+  Each of your environments is associated with an instance URL, such as https://login.salesforce.com. To open a specific
+  web page, specify the portion of the URL after "<URL>/" with the --path flag, such as /apex/YourPage to open a
+  Visualforce page.
 
 EXAMPLES
-  To open your default environment, run the command without flags:
+  Open your default environment:
 
     $ sf env open
 
-  This example opens the Visualforce page /apex/StartHere in a scratch org with alias "test-org":
+  Open the Visualforce page /apex/StartHere in a scratch org with alias test-org:
 
     $ sf env open --target-env test-org --path /apex/StartHere
 
-  If you want to view the URL for the preceding command, but not launch it in a browser:
+  View the URL but don't launch it in a browser:
 
     $ sf env open --target-env test-org --path /apex/StartHere --url-only
 
-  The preceding examples open the environment in your default web browser. To use a different browser, set the
-  --browser flag to its OS-specific name. For example, to use Chrome on macOS:
+  Open the environment in the Google Chrome browser:
+
+    $ sf env open --target-env test-org --path /apex/StartHere --browser chrome
+
+FLAG DESCRIPTIONS
+  -e, --target-env=<value>  Environment login user or alias to open.
+
+    Specify the login user or alias that’s associated with the environment. For scratch orgs, the login user is
+    generated by the command that created the scratch org. You can also set an alias for the scratch org when you create
+    it.
 
-    $ sf env open --target-env test-org --path /apex/StartHere --browser "google chrome"
+    For Dev Hubs, sandboxes, and production orgs, specify the alias you set when you logged into the org with "sf
+    login".
+
+  --browser=<value>  Browser in which to open the environment.
+
+    You can specify that the environment open in one of the following browsers: Firefox, Safari, Google Chrome, or
+    Windows Edge. If you don’t specify --browser, the environment opens in your default browser.
 ```
 
 ## `sf env var get KEY`
@@ -442,7 +446,7 @@ EXAMPLES
   $ sf login
 ```
 
-_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v0.0.4/src/commands/login.ts)_
+_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v0.0.5/src/commands/login.ts)_
 
 ## `sf login functions`
 
@@ -465,7 +469,7 @@ Allows you to login to a Salesforce org using either the default https://login.s
 
 ```
 USAGE
-  $ sf login org [-a <value>] [-b <value>] [-i <value>] [-l <value>] [-d]
+  $ sf login org [--json] [-a <value>] [-b <value>] [-i <value>] [-l <value>] [-d]
 
 FLAGS
   -a, --alias=<value>         Set an alias for the account or environment
@@ -474,7 +478,12 @@ FLAGS
   -i, --clientid=<value>      OAuth client ID (sometimes called the consumer key)
   -l, --instance-url=<value>  [default: https://login.salesforce.com] The login url
 
+GLOBAL FLAGS
+  --json  format output as json
+
 DESCRIPTION
+  Login to your Salesforce orgs.
+
   Allows you to login to a Salesforce org using either the default https://login.salesforce.com portal or a specific
   instance URL as defined with a flag.
 
@@ -494,7 +503,7 @@ Log in to your Salesforce orgs using a JSON web token
 
 ```
 USAGE
-  $ sf login org jwt [-a <value>] [-i <value>] [-l <value>] [-f <value>] [-d] [-u <value>]
+  $ sf login org jwt [--json] [-a <value>] [-l <value>] [-f <value> -u <value> -i <value>] [-d]
 
 FLAGS
   -a, --alias=<value>         Set an alias for the account or environment
@@ -504,6 +513,9 @@ FLAGS
   -l, --instance-url=<value>  [default: https://login.salesforce.com] The login url
   -u, --username=<value>      Authentication username
 
+GLOBAL FLAGS
+  --json  format output as json
+
 DESCRIPTION
   Log in to your Salesforce orgs using a JSON web token
 
@@ -517,7 +529,10 @@ Log out of all Salesforce orgs and environments.
 
 ```
 USAGE
-  $ sf logout
+  $ sf logout [--json]
+
+GLOBAL FLAGS
+  --json  format output as json
 
 DESCRIPTION
   Log out of all Salesforce orgs and environments.
@@ -526,7 +541,7 @@ EXAMPLES
   $ sf logout
 ```
 
-_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v0.0.4/src/commands/logout.ts)_
+_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v0.0.5/src/commands/logout.ts)_
 
 ## `sf plugins`
 
@@ -683,9 +698,11 @@ USAGE
   $ sf project deploy [--interactive]
 
 FLAGS
-  --interactive
+  --interactive  Force the CLI to prompt for all deployment inputs.
 
 DESCRIPTION
+  Deploy a project interactively to any Salesforce environment.
+
   The command first analyzes your project, active or logged-into environments, and local defaults to determine what to
   deploy and where. The command then prompts you for information about this particular deployment and provides
   intelligent choices based on its analysis.
@@ -735,16 +752,29 @@ You must run this command from wihin a project.
 
 ```
 USAGE
-  $ sf project deploy org [--json] [-m <value>] [-x <value>] [-d <value>] [-t <value>]
+  $ sf project deploy org [--json] [-m <value>] [-x <value>] [-d <value>] [--target-org <value>] [-l
+    NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg] [--wait <value>]
 
 FLAGS
-  -d, --deploy-dir=<value>  Root of local directory tree of files to deploy.
-  -m, --metadata=<value>    Space-separated list of metadata component names to deploy.
-  -t, --target-org=<value>  Username or alias of the org you want to deploy to
-  -x, --manifest=<value>    Full file path for manifest (package.xml) of components to deploy.
-  --json                    format output as json
+  -d, --deploy-dir=<value>...  Root of local directory tree of files to deploy.
+
+  -l, --test-level=<option>    [default: NoTestRun] Deployment Apex testing level.
+                               <options: NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg>
+
+  -m, --metadata=<value>...    List of metadata component names to deploy.
+
+  -x, --manifest=<value>       Full file path for manifest (package.xml) of components to deploy.
+
+  --target-org=<value>         Username or alias of the org you want to deploy to
+
+  --wait=<value>               [default: 33] Number of minutes to wait for command to complete.
+
+GLOBAL FLAGS
+  --json  format output as json
 
 DESCRIPTION
+  Deploy source to an org.
+
   You must run this command from wihin a project.
 
   The source you deploy overwrites the corresponding metadata in your org. This command doesn’t attempt to merge your
@@ -786,6 +816,27 @@ EXAMPLES
   Deploy all components listed in a manifest:
 
     $ sf project deploy org --manifest path/to/package.xml
+
+FLAG DESCRIPTIONS
+  -d, --deploy-dir=<value>...  Root of local directory tree of files to deploy.
+
+    Root of local directory tree of files to deploy.
+
+  -l, --test-level=NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg  Deployment Apex testing level.
+
+    Deployment Apex testing level.
+
+  -m, --metadata=<value>...  List of metadata component names to deploy.
+
+    List of metadata component names to deploy.
+
+  -x, --manifest=<value>  Full file path for manifest (package.xml) of components to deploy.
+
+    Full file path for manifest (package.xml) of components to deploy.
+
+  --wait=<value>  Number of minutes to wait for command to complete.
+
+    Default is 33 minutes.
 ```
 
 ## `sf run function`

diff --git a/package.json b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "0.0.10",
+  "version": "0.0.11",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run"
@@ -64,7 +64,7 @@
     "@oclif/plugin-help": "^3.2.2",
     "@oclif/plugin-not-found": "^2.1.1",
     "@oclif/plugin-plugins": "^1.10.1",
-    "@sf/env": "npm:@salesforce/[email protected].8",
+    "@sf/env": "npm:@salesforce/[email protected].9",
     "@sf/func": "npm:@salesforce/[email protected]",
     "@sf/login": "npm:@salesforce/[email protected]",
     "@sf/project": "npm:@salesforce/[email protected]",

diff --git a/yarn.lock b/yarn.lock
@@ -1172,10 +1172,10 @@
   dependencies:
     tslib "^2.2.0"
 
-"@sf/env@npm:@salesforce/[email protected].8":
-  version "0.0.8"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-env/-/plugin-env-0.0.8.tgz#f47b6edd20456a302a981338d7e7df31e0a9f321"
-  integrity sha512-kMBPmshTbSFFCyptqJ+dOQztONq5qZurcJBRXMOT82u4t5sva9cKzTSOr8Fq2oRaUIXYtB3OxLVmcFW1CViAgA==
+"@sf/env@npm:@salesforce/[email protected].9":
+  version "0.0.9"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-env/-/plugin-env-0.0.9.tgz#4d6dab8441bfab31238b1691351754aa5d630005"
+  integrity sha512-kPIwlAxObtRCcx3/C80wK4yKPxVyk5FwnVxh3yNwHyZZScO2eWsEXOuMQQNpRYUYx4Pv5hLdeEJHDkkrNAlGwQ==
   dependencies:
     "@oclif/core" "^0.5.21"
     "@salesforce/core" "^3.1.1-v3.2"