chore(release): 0.0.30 [ci skip]

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.30](https://github.com/salesforcecli/cli/compare/v0.0.29...v0.0.30) (2021-08-03)
+
+
+### Bug Fixes
+
+* mark commands as beta ([#28](https://github.com/salesforcecli/cli/issues/28)) ([cd44237](https://github.com/salesforcecli/cli/commit/cd44237e82eefb6f191e919f29b380f8daa41c69))
+
 ### [0.0.29](https://github.com/salesforcecli/cli/compare/v0.0.28...v0.0.29) (2021-07-28)
 
 ### [0.0.28](https://github.com/salesforcecli/cli/compare/v0.0.27...v0.0.28) (2021-07-27)

README.md

@@ -21,7 +21,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (-v|--version|version)
-@salesforce/cli/0.0.29 linux-x64 node-v14.17.3
+@salesforce/cli/0.0.29 linux-x64 node-v14.17.4
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND
@@ -213,8 +213,8 @@ DESCRIPTION
   if you want to deploy that Salesforce app to an org. The command lists your connected orgs and asks which one you want
   to deploy to. If the command finds Apex tests, it asks if you want to run them and at which level.
 
-  The command stores your responses in a local file and uses them as defaults when you rerun the command. Specify
-  --interactive to force the command to reprompt.
+  The command stores your responses in the "deploy-options.json" file in your local project directory and uses them as
+  defaults when you rerun the command. Specify --interactive to force the command to reprompt.
 
   Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific
   commands, such as "sf deploy metadata", that provide additional flags.
@@ -229,16 +229,16 @@ EXAMPLES
     $ sf deploy --interactive
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/v0.0.12/src/commands/deploy.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/v0.0.14/src/commands/deploy.ts)_
 
 ## `sf deploy metadata`
 
 You must run this command from within a project.
 
 ```
 USAGE
-  $ sf deploy metadata [--json] [-m <value>] [-x <value>] [-d <value>] [--target-org <value>] [-l
-    NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg] [--wait <value>]
+  $ sf deploy metadata [--json] [-m <value>] [-x <value>] [-d <value>] [-t <value>] [-l
+    NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg] [-w <value>]
 
 FLAGS
   -d, --deploy-dir=<value>...  Path to the local source files to deploy.
@@ -248,11 +248,11 @@ FLAGS
 
   -m, --metadata=<value>...    Metadata component names to deploy.
 
-  -x, --manifest=<value>       Full file path for manifest (package.xml) of components to deploy.
+  -t, --target-org=<value>     Login username or alias for the target org.
 
-  --target-org=<value>         Login username or alias for the target org.
+  -w, --wait=<value>           [default: 33] Number of minutes to wait for command to complete and display results.
 
-  --wait=<value>               [default: 33] Number of minutes to wait for command to complete and display results.
+  -x, --manifest=<value>       Full file path for manifest (package.xml) of components to deploy.
 
 GLOBAL FLAGS
   --json  format output as json
@@ -333,17 +333,17 @@ FLAG DESCRIPTIONS
     If you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more
     information, see “Running Tests in a Deployment” in the Metadata API Developer Guide.
 
-  -x, --manifest=<value>  Full file path for manifest (package.xml) of components to deploy.
-
-    All child components are included. If you specify this flag, don’t specify --metadata or --deploy-dir.
-
-  --target-org=<value>  Login username or alias for the target org.
+  -t, --target-org=<value>  Login username or alias for the target org.
 
     Overrides your default org.
 
-  --wait=<value>  Number of minutes to wait for command to complete and display results.
+  -w, --wait=<value>  Number of minutes to wait for command to complete and display results.
 
     If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
+
+  -x, --manifest=<value>  Full file path for manifest (package.xml) of components to deploy.
+
+    All child components are included. If you specify this flag, don’t specify --metadata or --deploy-dir.
 ```
 
 ## `sf env display`
@@ -390,11 +390,10 @@ The command displays only active environments. For orgs, active means unexpired
 
 ```
 USAGE
-  $ sf env list [--json] [-x] [--columns <value>] [--csv] [--filter <value>] [--no-header] [--no-truncate]
+  $ sf env list [--json] [--columns <value>] [--csv] [--filter <value>] [--no-header] [--no-truncate]
     [--output csv|json|yaml] [--sort <value>]
 
 FLAGS
-  -x, --extended        Show extra columns.
   --columns=<value>...  List of columns to display.
   --csv                 Output in csv format [alias: --output=csv]
   --filter=<value>      Filter property by partial string matching.
@@ -562,7 +561,7 @@ EXAMPLES
     $ sf login
 ```
 
-_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v0.0.11/src/commands/login.ts)_
+_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v0.0.12/src/commands/login.ts)_
 
 ## `sf login org`
 
@@ -686,6 +685,9 @@ DESCRIPTION
   cliend id) that’s generated for you. Be sure the username of the user logging in is approved to use the connected app.
   When you run this command, you set the --clientid flag to the consumer key.
 
+  See https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_jwt_flow.htm for more
+  information.
+
   We recommend that you set an alias when you log into an org. Aliases make it easy to later reference this org when
   running commands that require it. If you don’t set an alias, you use the username that you specified when you logged
   in to the org. If you run multiple commands that reference the same org, consider setting the org as your default. Use
@@ -754,7 +756,7 @@ EXAMPLES
     $ sf logout --noprompt
 ```
 
-_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v0.0.11/src/commands/logout.ts)_
+_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v0.0.12/src/commands/logout.ts)_
 
 ## `sf plugins`
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "0.0.29",
+  "version": "0.0.30",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run"

yarn.lock

@@ -917,6 +917,27 @@
     sfdx-faye "^1.0.9"
     ts-retry-promise "^0.6.0"
 
+"@salesforce/core@3.3.7":
+  version "3.3.7"
+  resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-3.3.7.tgz#063877eadca4a9add78cf088932cae138c5b4c69"
+  integrity sha512-/roLuNSHQ8pvBDE0ARVazsYh4+GXs8bBw+MAyRbdIta76jw5E5GiSioQ45o0vz1DR/aXBhsoEPCfPpxZW+/Adw==
+  dependencies:
+    "@salesforce/bunyan" "^2.0.0"
+    "@salesforce/kit" "^1.5.8"
+    "@salesforce/schemas" "^1.0.1"
+    "@salesforce/ts-types" "^1.5.13"
+    "@types/graceful-fs" "^4.1.5"
+    "@types/jsforce" "^1.9.29"
+    "@types/mkdirp" "^1.0.1"
+    debug "^3.1.0"
+    graceful-fs "^4.2.4"
+    jsen "0.6.6"
+    jsforce "^1.10.1"
+    jsonwebtoken "8.5.0"
+    mkdirp "1.0.4"
+    sfdx-faye "^1.0.9"
+    ts-retry-promise "^0.6.0"
+
 "@salesforce/core@^2.15.2", "@salesforce/core@^2.23.4", "@salesforce/core@^2.24.0":
   version "2.26.1"
   resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-2.26.1.tgz#00ecf0d989308786dcee648da231c528e6346c09"
@@ -1086,44 +1107,44 @@
     cli-ux "^5.6.3"
     tslib "^2"
 
-"@sf/deploy-retrieve@npm:@salesforce/plugin-deploy-retrieve@0.0.12":
-  version "0.0.12"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-0.0.12.tgz#f063277399b0d3770cdfb02e37c4b56789ef8625"
-  integrity sha512-29xrnMjbS11dF3Ud/jFfqxlFdh9Q2NCQIzl2NZdkx7bPnQv0l4aNiA4k63OKLk+a8PQYaxy9TOeViecFwkkb7w==
+"@sf/deploy-retrieve@npm:@salesforce/plugin-deploy-retrieve@0.0.14":
+  version "0.0.14"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-0.0.14.tgz#7978922391761e3602b29b81271eb878bda710cc"
+  integrity sha512-ugsYgLVqgowxNOt5h4AxCnUPS2KCSnk+cQ7noSZfwoWnjZXdZ0K+Oo6DdyYxq6LTqwb4dfvcJK+B9Xd7SYqGIA==
   dependencies:
     "@oclif/core" "^0.5.24"
     "@salesforce/core" "3.3.5"
     "@salesforce/plugin-deploy-retrieve-utils" "^0.0.9"
     tslib "^2"
 
-"@sf/dr-metadata@npm:@salesforce/plugin-deploy-retrieve-metadata@0.0.12":
-  version "0.0.12"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-deploy-retrieve-metadata/-/plugin-deploy-retrieve-metadata-0.0.12.tgz#8d6cd0605f16862874ce4ab99718d8628340c92d"
-  integrity sha512-eoR8HdbjvrlaOmVkvuwV44SANzA60MwlDgfneS0QmSSLPvYTDnPY2MZR8eYYG2wy9a/bs1dzcxWnkCbNFPsDaA==
+"@sf/dr-metadata@npm:@salesforce/plugin-deploy-retrieve-metadata@0.0.14":
+  version "0.0.14"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-deploy-retrieve-metadata/-/plugin-deploy-retrieve-metadata-0.0.14.tgz#fdbf823ef8cfb4c1d5ff2b55fbcd46d1c99aebb0"
+  integrity sha512-nFmssROAyCPd8g5C50jH4eTzoQJrwY2QQ1RGspkLiFADLkQqoktIM0QHcjubw7GvidF/xsYAGaghrU06Yx3YTQ==
   dependencies:
     "@oclif/core" "^0.5.26"
-    "@salesforce/core" "3.3.5"
+    "@salesforce/core" "3.3.7"
     "@salesforce/plugin-deploy-retrieve-utils" "^0.0.9"
     "@salesforce/source-deploy-retrieve" "^3.1.1"
     chalk "^4.1.1"
     cli-ux "^5.5.1"
     tslib "^2"
 
-"@sf/env@npm:@salesforce/plugin-env@0.0.16":
-  version "0.0.16"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-env/-/plugin-env-0.0.16.tgz#83ff136e45f7fc269f739e6278f05556548b1502"
-  integrity sha512-LL7hnOpjv1UxqPHCTsZnLSrEXNYg1+4CINGj9wob3IEFeui9RzM2+e9cjnenRJto2wgI6tVL8zTuuiXZhgCu0w==
+"@sf/env@npm:@salesforce/plugin-env@0.0.18":
+  version "0.0.18"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-env/-/plugin-env-0.0.18.tgz#75ca6ec2c06a84101e8839c838e8ba509a572f66"
+  integrity sha512-u1fhLE0E6TSfZill1ISEZWnv2tAwSz0Ufqg+bdfp81ApT8VM9/zo9s07IgNnkGkEXxg3HRCDWQQSdrk40X3Usg==
   dependencies:
     "@oclif/core" "^0.5.26"
     "@salesforce/core" "3.3.5"
     cli-ux "^5.6.3"
     open "^8.2.0"
     tslib "^2"
 
-"@sf/login@npm:@salesforce/plugin-login@0.0.11":
-  version "0.0.11"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-login/-/plugin-login-0.0.11.tgz#7607517cde685752098a61d73b10353b10621b4f"
-  integrity sha512-W+hzwUWiX4hzsXEcCaUNInSYkevtMT4k5vTFcHbNhWv2tyz3nwsfSk0fDOc+OQqdqydwc2quxfD2je+Ow9DUqg==
+"@sf/login@npm:@salesforce/plugin-login@0.0.12":
+  version "0.0.12"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-login/-/plugin-login-0.0.12.tgz#cd5e0f3d8ef74cbe5f1dcfb61573b2c2efb6c125"
+  integrity sha512-z01i/o58k5bsTQQxP5EeRmLRidrXzisyP03vofglQ+QoTFKe0XaIsl5Rj3K9jOEpuVUjmGfPUO5mhCyGmlCCHA==
   dependencies:
     "@oclif/core" "^0.5.21"
     "@salesforce/core" "3.3.6"