chore(release): 1.3.1 [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.
 
+### [1.3.1](https://github.com/salesforcecli/cli/compare/v1.3.0...v1.3.1) (2021-11-11)
+
+
+### Bug Fixes
+
+* bump versions ([7983bcc](https://github.com/salesforcecli/cli/commit/7983bcc2bc8ccfdc1123a6dce2548b70e1811d1f))
+
 ## [1.3.0](https://github.com/salesforcecli/cli/compare/v1.2.0...v1.3.0) (2021-11-04)
 
 

README.md

@@ -438,6 +438,10 @@ FLAGS
 DESCRIPTION
   Create a compute environment for use with Salesforce Functions.
 
+  Compute environments must be connected to a Salesforce org. By default the command uses your local environment's
+  connected org. Use the '--connected-org' flag to specify a specific org. Run 'sf env list' to see a list of
+  environments.
+
 EXAMPLES
   Create a compute environment to run Salesforce Functions:
 
@@ -467,6 +471,12 @@ FLAGS
 DESCRIPTION
   Delete an environment.
 
+  You must include the name of the environment to delete using '--target-compute'. Run 'sf env list' to see a list of
+  environments.
+
+  Running this command will prompt a confirmation. If you want to skip this confirmation, use the '--confirm' flag and
+  the environment alias to skip confirmation.
+
 EXAMPLES
   Delete a compute environment:
 
@@ -597,9 +607,6 @@ USAGE
 FLAGS
   -e, --target-compute=<value>  Compute environment name to retrieve logs.
 
-DESCRIPTION
-  Stream log output for an environment.
-
 EXAMPLES
   Stream log output:
 
@@ -621,6 +628,9 @@ FLAGS
 DESCRIPTION
   Add log drain to a specified environment.
 
+  Both '--target-compute' and '--url' are required flags. '--url' should be a HTTP or HTTPS URL that can receive the log
+  drain messages.
+
 EXAMPLES
   Add a log drain:
 
@@ -639,9 +649,6 @@ FLAGS
   -e, --target-compute=<value>  Environment name.
   -j, --json                    Output list in JSON format.
 
-DESCRIPTION
-  List log drains connected to a specified environment.
-
 EXAMPLES
   List log drains:
 
@@ -667,6 +674,8 @@ FLAGS
 DESCRIPTION
   Remove log drain from a specified environment.
 
+  Both '--target-compute' and '--drain-url' are required flags.
+
 EXAMPLES
   Remove a logdrain:
 
@@ -744,6 +753,8 @@ FLAGS
 DESCRIPTION
   Display a single config variable for an environment.
 
+  You must provide the '--target-compute' flag and the key to retrieve.
+
 EXAMPLES
   Get a config variable:
 
@@ -765,6 +776,8 @@ FLAGS
 DESCRIPTION
   List your environment's config vars in a table.
 
+  Use the '--json' flag to return config vars in JSON format.
+
 EXAMPLES
   List config vars:
 
@@ -786,9 +799,6 @@ USAGE
 FLAGS
   -e, --target-compute=<value>  Environment name.
 
-DESCRIPTION
-  Set a single config value for an environment.
-
 EXAMPLES
   Set a config value:
 
@@ -809,6 +819,8 @@ FLAGS
 DESCRIPTION
   Unset a single config value for an environment.
 
+  Run 'sf env var list' to see a list of config values that can be unset.
+
 EXAMPLES
   Unset a value:
 
@@ -830,6 +842,8 @@ FLAGS
 DESCRIPTION
   Create a Salesforce Function with basic scaffolding specific to a given language.
 
+  Both '--language' and '--name' are required flags. Function names must start with a capital letter.
+
 EXAMPLES
   Create a JavaScript function:
 
@@ -994,6 +1008,8 @@ USAGE
 DESCRIPTION
   Log in to Salesforce Functions.
 
+  This step is required to develop or deploy Salesforce Functions.
+
 EXAMPLES
   Log in to Salesforce Functions:
 
@@ -1021,6 +1037,8 @@ FLAGS
 DESCRIPTION
   Login using JWT instead of default web-based flow. This will authenticate you with both sf and Salesforce Functions.
 
+  Use this command when executing from a script.
+
 EXAMPLES
   Log in using JWT:
 
@@ -1253,9 +1271,6 @@ Log out of your Salesforce Functions account.
 USAGE
   $ sf logout functions
 
-DESCRIPTION
-  Log out of your Salesforce Functions account.
-
 EXAMPLES
   Log out:
 
@@ -1566,9 +1581,6 @@ FLAGS
   -p, --payload=<value>        Set the payload of the cloudevent as a JSON object or a path to a file via @file.json.
   -s, --structured             Set the cloudevent to be emitted as a structured JSON cloudevent.
 
-DESCRIPTION
-  Send a cloudevent to a function.
-
 EXAMPLES
   Run a function:
 
@@ -1600,6 +1612,8 @@ FLAGS
 DESCRIPTION
   Build and run a Salesforce Function locally.
 
+  Run this command from the directory of your Salesforce Functions project.
+
 EXAMPLES
   Build and run a function:
 
@@ -1628,6 +1642,8 @@ FLAGS
 DESCRIPTION
   Show information on your Salesforce Functions login.
 
+  Returns your email and ID. Use '--show-token' to show your Salesforce Functions token.
+
 EXAMPLES
   Get account information:
 

package.json

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