@salesforce/cli 2.87.5 → 2.87.6

package/README.md

@@ -25,7 +25,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (--version|-v)
-@salesforce/cli/2.87.5 linux-x64 node-v22.14.0
+@salesforce/cli/2.87.6 linux-x64 node-v22.14.0
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND
@@ -76,7 +76,6 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 - [`sf data import resume`](#sf-data-import-resume)
 - [`sf data import tree`](#sf-data-import-tree)
 - [`sf data query`](#sf-data-query)
-- [`sf data query resume`](#sf-data-query-resume)
 - [`sf data resume`](#sf-data-resume)
 - [`sf data search`](#sf-data-search)
 - [`sf data update bulk`](#sf-data-update-bulk)
@@ -1337,7 +1336,7 @@ EXAMPLES
     $ sf data bulk results --job-id 7507i000fake341G --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/bulk/results.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/bulk/results.ts)_
 
 ## `sf data create file`
 
@@ -1386,7 +1385,7 @@ EXAMPLES
     $ sf data create file --file path/to/astro.png --parent-id a03fakeLoJWPIA3
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/create/file.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/create/file.ts)_
 
 ## `sf data create record`
 
@@ -1442,7 +1441,7 @@ EXAMPLES
       TracedEntityId=01p17000000R6bLAAS"
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/create/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/create/record.ts)_
 
 ## `sf data delete bulk`
 
@@ -1502,7 +1501,7 @@ FLAG DESCRIPTIONS
     and can be enabled only by a system administrator.
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/delete/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/delete/bulk.ts)_
 
 ## `sf data delete record`
 
@@ -1563,7 +1562,7 @@ EXAMPLES
     $ sf data delete record --use-tooling-api --sobject TraceFlag --record-id 7tf8c
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/delete/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/delete/record.ts)_
 
 ## `sf data delete resume`
 
@@ -1602,7 +1601,7 @@ EXAMPLES
     $ sf data delete resume --use-most-recent --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/delete/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/delete/resume.ts)_
 
 ## `sf data export bulk`
 
@@ -1676,7 +1675,7 @@ EXAMPLES
       --result-format json --async
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/export/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/export/bulk.ts)_
 
 ## `sf data export resume`
 
@@ -1712,7 +1711,7 @@ EXAMPLES
     $ sf data export resume --use-most-recent --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/export/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/export/resume.ts)_
 
 ## `sf data export tree`
 
@@ -1772,7 +1771,7 @@ EXAMPLES
       my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/export/tree.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/export/tree.ts)_
 
 ## `sf data get record`
 
@@ -1836,7 +1835,7 @@ EXAMPLES
     $ sf data get record --use-tooling-api --sobject TraceFlag --record-id 7tf8c
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/get/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/get/record.ts)_
 
 ## `sf data import bulk`
 
@@ -1894,7 +1893,7 @@ EXAMPLES
     $ sf data import bulk --file accounts.csv --sobject Account --async
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/import/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/import/bulk.ts)_
 
 ## `sf data import resume`
 
@@ -1930,7 +1929,7 @@ EXAMPLES
     $ sf data import resume --use-most-recent --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/import/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/import/resume.ts)_
 
 ## `sf data import tree`
 
@@ -1994,7 +1993,7 @@ FLAG DESCRIPTIONS
     - files(array) - Files: An array of files paths to load
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/import/tree.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/import/tree.ts)_
 
 ## `sf data query`
 
@@ -2003,10 +2002,9 @@ Execute a SOQL query.
 ```
 USAGE
   $ sf data query -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-q <value>] [-f <value>]
-    [-t | -b] [-w <value> ] [--async ] [--all-rows] [-r human|csv|json] [--output-file <value>]
+    [-t] [--all-rows] [-r human|csv|json] [--output-file <value>]
 
 FLAGS
-  -b, --bulk                    Use Bulk API 2.0 to run the query.
   -f, --file=<value>            File that contains the SOQL query.
   -o, --target-org=<value>      (required) Username or alias of the target org. Not required if the `target-org`
                                 configuration variable is already set.
@@ -2014,10 +2012,8 @@ FLAGS
   -r, --result-format=<option>  [default: human] Format to display the results; the --json flag overrides this flag.
                                 <options: human|csv|json>
   -t, --use-tooling-api         Use Tooling API so you can run queries on Tooling API objects.
-  -w, --wait=<value>            Time to wait for the command to finish, in minutes.
       --all-rows                Include deleted records. By default, deleted records are not returned.
       --api-version=<value>     Override the api version used for api requests made by this command
-      --async                   Use Bulk API 2.0, but don't wait for the job to complete.
       --output-file=<value>     File where records are written; only CSV and JSON output formats are supported.
 
 GLOBAL FLAGS
@@ -2029,14 +2025,8 @@ DESCRIPTION
 
   Specify the SOQL query at the command line with the --query flag or read the query from a file with the --file flag.
 
-  If your query returns more than 10,000 records, specify the --bulk flag. The command then runs the query using Bulk
-  API 2.0, which has higher limits than the default API used by the command.
-
-  When using --bulk, the command waits 3 minutes by default for the query to complete. Use the --wait parameter to
-  specify a different number of minutes to wait, or set --wait to 0 to immediately return control to the terminal. If
-  you set --wait to 0, or you use the --async flag, or the command simply times out, the command displays an ID. Pass
-  this ID to the the "data query resume" command using the --bulk-query-id flag to get the results; pass the ID to the
-  "data resume" command to get the job status.
+  If your query returns more than 10,000 records, prefer to use the `sf data export bulk` command instead. It runs the
+  query using Bulk API 2.0, which has higher limits than the default API used by the command.
 
 ALIASES
   $ sf force data soql query
@@ -2054,50 +2044,9 @@ EXAMPLES
   Use Tooling API to run a query on the ApexTrigger Tooling API object:
 
     $ sf data query --query "SELECT Name FROM ApexTrigger" --use-tooling-api
-
-  Use Bulk API 2.0 to run a query that returns many rows, and return control to the terminal immediately:
-
-    $ sf data query --query "SELECT Id FROM Contact" --bulk --wait 0
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/query.ts)_
-
-## `sf data query resume`
-
-View the status of a bulk query.
-
-```
-USAGE
-  $ sf data query resume [--json] [--flags-dir <value>] [-o <value>] [--api-version <value>] [-r human|csv|json] [-i
-    <value>] [--use-most-recent]
-
-FLAGS
-  -i, --bulk-query-id=<value>   Job ID of the bulk query.
-  -o, --target-org=<value>      Username or alias of the target org.
-  -r, --result-format=<option>  [default: human] Format to display the results; the --json flag overrides this flag.
-                                <options: human|csv|json>
-      --api-version=<value>     Override the api version used for api requests made by this command
-      --use-most-recent         Use the most recent bulk query ID from cache.
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  View the status of a bulk query.
-
-  Run this command using the job ID returned from the "sf data query --bulk" command.
-
-ALIASES
-  $ sf force data soql bulk report
-
-EXAMPLES
-  View the status of a bulk query with the specified ID:
-
-    $ sf data query resume --bulk-query-id 7500x000005BdFzXXX
-```
-
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/query/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/query.ts)_
 
 ## `sf data resume`
 
@@ -2134,7 +2083,7 @@ EXAMPLES
     $ sf data resume --job-id 750xx000000005sAAA --batch-id 751xx000000005nAAA
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/resume.ts)_
 
 ## `sf data search`
 
@@ -2184,7 +2133,7 @@ EXAMPLES
     $ sf data search --file query.txt --target-org my-scratch --result-format csv
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/search.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/search.ts)_
 
 ## `sf data update bulk`
 
@@ -2245,7 +2194,7 @@ EXAMPLES
     $ sf data update bulk --file accounts.csv --sobject Account --async
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/update/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/update/bulk.ts)_
 
 ## `sf data update record`
 
@@ -2307,7 +2256,7 @@ EXAMPLES
       "ExpirationDate=2017-12-01T00:58:04.000+0000"
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/update/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/update/record.ts)_
 
 ## `sf data update resume`
 
@@ -2343,7 +2292,7 @@ EXAMPLES
     $ sf data update resume --use-most-recent --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/update/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/update/resume.ts)_
 
 ## `sf data upsert bulk`
 
@@ -2400,7 +2349,7 @@ EXAMPLES
       my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/upsert/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/upsert/bulk.ts)_
 
 ## `sf data upsert resume`
 
@@ -2439,7 +2388,7 @@ EXAMPLES
     $ sf data upsert resume --use-most-recent --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/data/upsert/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/data/upsert/resume.ts)_
 
 ## `sf doctor`
 
@@ -2534,7 +2483,7 @@ EXAMPLES
     $ sf force data bulk delete --sobject MyObject__c --file files/delete.csv --wait 5 --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/force/data/bulk/delete.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/force/data/bulk/delete.ts)_
 
 ## `sf force data bulk status`
 
@@ -2571,7 +2520,7 @@ EXAMPLES
     $ sf force data bulk status --job-id 750xx000000005sAAA --batch-id 751xx000000005nAAA --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/force/data/bulk/status.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/force/data/bulk/status.ts)_
 
 ## `sf force data bulk upsert`
 
@@ -2629,7 +2578,7 @@ EXAMPLES
       --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.28/src/commands/force/data/bulk/upsert.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.29/src/commands/force/data/bulk/upsert.ts)_
 
 ## `sf help [COMMAND]`
 
@@ -6423,7 +6372,7 @@ FLAG DESCRIPTIONS
     If you specify this flag, don’t specify --metadata or --source-dir.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/convert/mdapi.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/convert/mdapi.ts)_
 
 ## `sf project convert source`
 
@@ -6496,7 +6445,7 @@ FLAG DESCRIPTIONS
     Override the api version used for api requests made by this command
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/convert/source.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/convert/source.ts)_
 
 ## `sf project convert source-behavior`
 
@@ -6555,7 +6504,7 @@ EXAMPLES
     $ sf project convert source-behavior --behavior decomposePermissionSetBeta --dry-run --preserve-temp-dir
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/convert/source-behavior.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/convert/source-behavior.ts)_
 
 ## `sf project delete source`
 
@@ -6695,7 +6644,7 @@ FLAG DESCRIPTIONS
     - Separate the test names with spaces: --tests Test1 Test2 "Test With Space"
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/delete/source.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/delete/source.ts)_
 
 ## `sf project delete tracking`
 
@@ -6732,7 +6681,7 @@ EXAMPLES
     $ sf project delete tracking --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/delete/tracking.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/delete/tracking.ts)_
 
 ## `sf project deploy cancel`
 
@@ -6804,7 +6753,7 @@ FLAG DESCRIPTIONS
     project deploy report".
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/deploy/cancel.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/deploy/cancel.ts)_
 
 ## `sf project deploy preview`
 
@@ -6887,7 +6836,7 @@ FLAG DESCRIPTIONS
     All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/deploy/preview.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/deploy/preview.ts)_
 
 ## `sf project deploy quick`
 
@@ -6980,7 +6929,7 @@ ERROR CODES
   Canceling (69)         The deploy is being canceled.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/deploy/quick.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/deploy/quick.ts)_
 
 ## `sf project deploy report`
 
@@ -7072,7 +7021,7 @@ FLAG DESCRIPTIONS
     --coverage-formatters lcov --coverage-formatters clover
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/deploy/report.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/deploy/report.ts)_
 
 ## `sf project deploy resume`
 
@@ -7169,7 +7118,7 @@ ERROR CODES
   Canceling (69)         The deploy is being canceled.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/deploy/resume.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/deploy/resume.ts)_
 
 ## `sf project deploy start`
 
@@ -7422,7 +7371,7 @@ ERROR CODES
   Canceling (69)         The deploy is being canceled.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/deploy/start.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/deploy/start.ts)_
 
 ## `sf project deploy validate`
 
@@ -7612,7 +7561,7 @@ ERROR CODES
   Canceling (69)         The deploy is being canceled.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/deploy/validate.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/deploy/validate.ts)_
 
 ## `sf project generate`
 
@@ -7813,7 +7762,7 @@ EXAMPLES
     $ sf project generate manifest --from-org test@myorg.com --excluded-metadata StandardValueSet
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/generate/manifest.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/generate/manifest.ts)_
 
 ## `sf project list ignored`
 
@@ -7855,7 +7804,7 @@ EXAMPLES
     $ sf project list ignored --source-dir package.xml
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/list/ignored.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/list/ignored.ts)_
 
 ## `sf project reset tracking`
 
@@ -7904,7 +7853,7 @@ EXAMPLES
     $ sf project reset tracking --revision 30
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/reset/tracking.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/reset/tracking.ts)_
 
 ## `sf project retrieve preview`
 
@@ -7958,7 +7907,7 @@ FLAG DESCRIPTIONS
     production orgs.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/retrieve/preview.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/retrieve/preview.ts)_
 
 ## `sf project retrieve start`
 
@@ -8054,6 +8003,10 @@ EXAMPLES
 
     $ sf project retrieve start --metadata 'CustomObject:SBQQ__*'
 
+  Retrieve all list views for the Case standard object:
+
+    $ sf project retrieve start --metadata 'ListView:Case*'
+
   Retrieve all custom objects and Apex classes found in all defined package directories (both examples are
   equivalent):
 
@@ -8135,7 +8088,7 @@ ENVIRONMENT VARIABLES
   SF_USE_PROGRESS_BAR  Set to false to disable the progress bar when running the metadata deploy command.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.4/src/commands/project/retrieve/start.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.22.5/src/commands/project/retrieve/start.ts)_
 
 ## `sf schema generate field`
 

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@salesforce/cli",
-  "version": "2.87.5",
+  "version": "2.87.6",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@salesforce/cli",
-      "version": "2.87.5",
+      "version": "2.87.6",
       "hasInstallScript": true,
       "license": "Apache-2.0",
       "dependencies": {
@@ -27,8 +27,8 @@
         "@salesforce/plugin-apex": "3.6.15",
         "@salesforce/plugin-api": "1.3.3",
         "@salesforce/plugin-auth": "3.6.115",
-        "@salesforce/plugin-data": "4.0.28",
-        "@salesforce/plugin-deploy-retrieve": "3.22.4",
+        "@salesforce/plugin-data": "4.0.29",
+        "@salesforce/plugin-deploy-retrieve": "3.22.5",
         "@salesforce/plugin-info": "3.4.56",
         "@salesforce/plugin-limits": "3.3.52",
         "@salesforce/plugin-marketplace": "1.3.8",
@@ -5064,9 +5064,9 @@
       }
     },
     "node_modules/@salesforce/plugin-data": {
-      "version": "4.0.28",
-      "resolved": "https://registry.npmjs.org/@salesforce/plugin-data/-/plugin-data-4.0.28.tgz",
-      "integrity": "sha512-gmLY9Mgp9TRMLerIChp+yzG1favp6MLpDna5dQFDRX5C7/ZA0JMpMTMqLh6En19VGSJHk4N3nB+Q8HedjR7CkA==",
+      "version": "4.0.29",
+      "resolved": "https://registry.npmjs.org/@salesforce/plugin-data/-/plugin-data-4.0.29.tgz",
+      "integrity": "sha512-+Fls7l6u4QIZskwYJCxesa9r8q0prqL08o/loGe3j1/aYDk8Hlq0Y3ccoO+3Zcgutkx/tadbohJw75aEq+G24w==",
       "license": "Apache-2.0",
       "dependencies": {
         "@jsforce/jsforce-node": "^3.6.6",
@@ -5087,10 +5087,10 @@
       }
     },
     "node_modules/@salesforce/plugin-deploy-retrieve": {
-      "version": "3.22.4",
-      "resolved": "https://registry.npmjs.org/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-3.22.4.tgz",
-      "integrity": "sha512-gpbJfIAUQTfFL6rtxQuREaz/CrrqrIzR7oNhzMeOZFN6Dky03LnKuQDMTFCEGzTJpiSStJ7RGb36I0rtTv7WZA==",
-      "license": "BSD-3-Clause",
+      "version": "3.22.5",
+      "resolved": "https://registry.npmjs.org/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-3.22.5.tgz",
+      "integrity": "sha512-dhq7kagY5R8+n2DXnQidLv9bJMW/T198WrcT5VDSgyzvVIesVYJX7xbN2r6ISxt6PU1V/7IwYEOendfdI93rvQ==",
+      "license": "Apache-2.0",
       "dependencies": {
         "@inquirer/prompts": "^7.4.1",
         "@oclif/core": "^4.2.10",

package/oclif.lock

@@ -2105,10 +2105,10 @@
     debug "^4.4.0"
     handlebars "^4.7.8"
 
-"@salesforce/plugin-data@4.0.28":
-  version "4.0.28"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-data/-/plugin-data-4.0.28.tgz"
-  integrity sha512-gmLY9Mgp9TRMLerIChp+yzG1favp6MLpDna5dQFDRX5C7/ZA0JMpMTMqLh6En19VGSJHk4N3nB+Q8HedjR7CkA==
+"@salesforce/plugin-data@4.0.29":
+  version "4.0.29"
+  resolved "https://registry.npmjs.org/@salesforce/plugin-data/-/plugin-data-4.0.29.tgz"
+  integrity sha512-+Fls7l6u4QIZskwYJCxesa9r8q0prqL08o/loGe3j1/aYDk8Hlq0Y3ccoO+3Zcgutkx/tadbohJw75aEq+G24w==
   dependencies:
     "@jsforce/jsforce-node" "^3.6.6"
     "@oclif/multi-stage-output" "^0.8.12"
@@ -2123,10 +2123,10 @@
     form-data "^4.0.2"
     terminal-link "^3.0.0"
 
-"@salesforce/plugin-deploy-retrieve@3.22.4":
-  version "3.22.4"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-3.22.4.tgz"
-  integrity sha512-gpbJfIAUQTfFL6rtxQuREaz/CrrqrIzR7oNhzMeOZFN6Dky03LnKuQDMTFCEGzTJpiSStJ7RGb36I0rtTv7WZA==
+"@salesforce/plugin-deploy-retrieve@3.22.5":
+  version "3.22.5"
+  resolved "https://registry.npmjs.org/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-3.22.5.tgz"
+  integrity sha512-dhq7kagY5R8+n2DXnQidLv9bJMW/T198WrcT5VDSgyzvVIesVYJX7xbN2r6ISxt6PU1V/7IwYEOendfdI93rvQ==
   dependencies:
     "@inquirer/prompts" "^7.4.1"
     "@oclif/core" "^4.2.10"

package/oclif.manifest.json

@@ -3,22 +3,32 @@
     "code-analyzer:config": {
       "aliases": [],
       "args": {},
-      "description": "Code Analyzer gives you the ability to configure settings that modify Code Analyzer's behavior, to override the tags and severity levels of rules, and to configure the engine specific settings.  Use this command to see the current state of this configuration. You can also save this state to a YAML-formatted file that you can modify for your needs.\n\nTo apply a custom configuration with Code Analyzer, either keep your custom configuration settings in a `code-analyzer.yml` file located in the current folder from which you are executing commands, or specify the location of your custom configuration file to the Code Analyzer commands with the --config-file flag.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.",
+      "description": "Code Analyzer gives you the ability to configure settings that modify Code Analyzer's behavior, to override the tags and severity levels of rules, and to configure the engine specific settings. Use this command to see the current state of this configuration. You can also save this state to a YAML-formatted file that you can modify for your needs.\n\nTo apply a custom configuration with Code Analyzer, either keep your custom configuration settings in a `code-analyzer.yml` file located in the current folder from which you are executing commands, or specify the location of your custom configuration file to the Code Analyzer commands with the --config-file flag.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at https://sfdc.co/CodeAnalyzerFeedback.",
       "examples": [
         "Display the current state of the Code Analyzer configuration using the default behavior: display top level configuration, display the engine and rule override settings associated with all the rules; and automatically apply any existing custom configuration settings found in a `code-analyzer.yml` or `code-analyzer.yaml` file in the current folder:\n<%= config.bin %> <%= command.id %>",
         "This example is identical to the previous one, assuming that `./code-analyzer.yml` exists in your current folder.\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer.yml --rule-selector all",
         "Write the current state of configuration to the file `code-analyzer.yml`, including any configuration from an existing `code-analyzer.yml` file. The command preserves all values from the original config, but overwrites any comments:\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer.yml --output-file code-analyzer.yml",
         "Display the configuration state for just the recommended rules, instead of all the rules:\n<%= config.bin %> <%= command.id %> --rule-selector Recommended",
-        "Display the configuration state associated with all the rules that are applicable to your workspace folder, `./src`:\n<%= config.bin %> <%= command.id %> --workspace ./src",
+        "Display the configuration state associated with all the rules that are applicable to the files targeted within the folder `./src`:\n<%= config.bin %> <%= command.id %> --target ./src",
         "Display any relevant configuration settings associated with the rule name 'no-undef' from the 'eslint' engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:no-undef",
         "Load an existing configuration file called `existing-config.yml`, and then write the configuration to a new file called `new-config.yml`, the configuration state that is applicable to all rules that are relevant to the workspace located in the current folder:\n<%= config.bin %> <%= command.id %> --config-file ./existing-config.yml --workspace . --output-file ./subfolder-config.yml"
       ],
       "flags": {
         "workspace": {
           "char": "w",
-          "description": "Use the --workspace flag to display only the configuration associated with the rules that apply to the files that make up your workspace. Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders.\n\nThis command uses the type of file in the workspace, such as JavaScript or Typescript, to determine the rules to include in the configuration state. For example, if your workspace contains only JavaScript files, the command doesn't include TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nSome engines may be configured to add additional rules based on what it finds in your workspace.  For example, if you set the \"engines.eslint.auto_discover_eslint_config\" value of your `code-analyzer.yml` file to true, then supplying your workspace allows the \"eslint\" engine to examine your files in order to find ESLint configuration files that could potentially add in additional rules.",
+          "description": "Use the `--workspace` flag to display only the configuration associated with the rules that apply to the files that make up your workspace. Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders.\n\nThis command uses the types of files in the workspace, such as JavaScript or Typescript, to determine the applicable configuration state. For example, if your workspace contains only JavaScript files, then the command doesn't display configuration state associated with TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nSome engines can be configured to add additional rules based on what it finds in your workspace. For example, if you set the engines.eslint.auto_discover_eslint_config value of your `code-analyzer.yml` file to true, then supplying your workspace allows the \"eslint\" engine to examine your files in order to find ESLint configuration files that could potentially add in additional rules.\n\nIf you specify `--target` but not `--workspace`, then the current folder '.' is used as your workspace.",
           "name": "workspace",
-          "summary": "Set of files you want to include in the code analysis.",
+          "summary": "Set of files that make up your workspace.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "target": {
+          "char": "t",
+          "description": "Use the `--target` flag to display the configuration state associated with the rules that apply to only a subset of targeted files within your workspace. You can specify a target as a file, a folder, or a glob pattern. If you specify this flag multiple times, then the full list of targeted files is the sum of the files and folders.\n\nThe command uses the type of the targeted files, such as JavaScript or Typescript, to determine which configuration state is applicable. For example, if you target only JavaScript files, then the command doesn't display the configuration state associated with TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nEach targeted file must live within the workspace specified by the `–-workspace` flag.\n\nIf you specify `--workspace` but not `--target`, then all the files within your workspace are targeted.",
+          "name": "target",
+          "summary": "Subset of files within your workspace that you want to target for analysis.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -26,7 +36,7 @@
         },
         "rule-selector": {
           "char": "r",
-          "description": "Use the --rule-selector flag to display only the configuration associated with the rules based on specific criteria. You can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names.\n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection.  For example, \"--rule-selector eslint:Security\" reduces the output to only contain the configuration state associated with the rules from the \"eslint\" engine that have the \"Security\" tag. To add multiple rule selectors together (a union), specify the --rule-selector flag multiple times, such as \"--rule-selector eslint:Recommended --rule-selector retire-js:3\".\n\nIf you don't specify this flag, then the command uses the \"all\" rule selector.\n\nRun `<%= config.bin %> <%= command.id %>  --rule-selector Recommended` to display the configuration state associated with just the 'Recommended' rules, instead of all the rules.",
+          "description": "Use the `--rule-selector` flag to display only the configuration associated with the rules based on specific criteria. You can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names.\n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection. For example, `--rule-selector eslint:Security` reduces the output to only contain the configuration state associated with the rules from the \"eslint\" engine that have the \"Security\" tag. To add multiple rule selectors together (a union), specify the `--rule-selector` flag multiple times, such as `--rule-selector eslint:Recommended --rule-selector retire-js:3`.\n\nIf you don't specify this flag, then the command uses the \"all\" rule selector.\n\nRun `<%= config.bin %> <%= command.id %> --rule-selector Recommended` to display the configuration state associated with just the 'Recommended' rules, instead of all the rules.",
           "name": "rule-selector",
           "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
           "default": [
@@ -48,7 +58,7 @@
         },
         "output-file": {
           "char": "f",
-          "description": "Use this flag to write the final config to a file, in addition to the terminal.",
+          "description": "If you specify a file within folder, such as `--output-file ./config/code-analyzer.yml`, the folder must already exist, or you get an error. If the file already exists, a prompt asks if you want to overwrite it.\n\nIf you don't specify this flag, the command outputs the configuration state to the terminal.",
           "name": "output-file",
           "summary": "Output file to write the configuration state to. The file is written in YAML format.",
           "hasDynamicHelp": false,
@@ -62,7 +72,6 @@
       "pluginAlias": "@salesforce/plugin-code-analyzer",
       "pluginName": "@salesforce/plugin-code-analyzer",
       "pluginType": "jit",
-      "state": "Beta",
       "strict": true,
       "summary": "Display the current state of configuration for Code Analyzer.",
       "enableJsonFlag": false,
@@ -83,27 +92,37 @@
     "code-analyzer:rules": {
       "aliases": [],
       "args": {},
-      "description": "You can also view details about the rules, such as the engine it's associated with, tags, and description.\n\nUse this command to determine the exact set of rules to analyze your code. The `code-analyzer run` command has similar flags as this command, so once you've determined the flag values for this command that list the rules you want to run, you specify the same values to the `code-analyzer run` command.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.",
+      "description": "You can also view details about the rules, such as the engine it's associated with, tags, and description.\n\nUse this command to determine the exact set of rules to analyze your code. The `code-analyzer run` command has similar flags as this command, so once you've determined the flag values for this command that list the rules you want to run, you specify the same values to the `code-analyzer run` command.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at https://sfdc.co/CodeAnalyzerFeedback.",
       "examples": [
-        "List rules using the default behavior: include rules from all engines that have a \"Recommended\" tag; display the rules using concise table format; and automatically apply rule or engine overrides if a \"code-analyzer.yml\" or \"code-analyzer.yaml\" file exists in the current folder:\n<%= config.bin %> <%= command.id %>",
+        "List rules using the default behavior: include rules from all engines that have a \"Recommended\" tag; display the rules using concise table format; and automatically apply rule or engine overrides if a `code-analyzer.yml` or `code-analyzer.yaml` file exists in the current folder:\n<%= config.bin %> <%= command.id %>",
         "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %> --rule-selector Recommended --view table --config-file ./code-analyzer.yml",
-        "List the recommended rules for the \"eslint\" engine:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint:Recommended",
-        "List all the rules for the \"eslint\" engine:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint",
-        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint:all",
-        "List the details about all rules for all engines; also write the rules in JSON format to a file called \"rules.json\" in the \"out\" folder, which must already exist:\n<%= config.bin %> <%= command.id %>  --rule-selector all --output-file ./out/rules.json --view detail",
-        "Get a more accurate list of the rules that apply specifically to your workspace (all the files in the current folder):\n<%= config.bin %> <%= command.id %>  --rule-selector all --workspace .",
-        "List the recommended rules associated with a workspace that includes all the files in the folder \"./other-source\" and only the Apex class files (extension .cls) under the folder \"./force-app\":\n<%= config.bin %> <%= command.id %>  --rule-selector Recommended --workspace ./other-source --workspace ./force-app/**/*.cls",
+        "List the recommended rules for the \"eslint\" engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:Recommended",
+        "List all the rules for the \"eslint\" engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint",
+        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:all",
+        "List the details about all rules for all engines; also write the rules in JSON format to a file called \"rules.json\" in the \"out\" folder, which must already exist:\n<%= config.bin %> <%= command.id %> --rule-selector all --output-file ./out/rules.json --view detail",
+        "Get a more accurate list of the rules that apply specifically to your workspace (all the files in the current folder):\n<%= config.bin %> <%= command.id %> --rule-selector all --workspace .",
+        "List the recommended rules associated with a workspace that targets all the files in the folder \"./other-source\" and only the Apex class files (extension .cls) under the folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector Recommended --workspace . --target ./other-source --target ./force-app/**/*.cls",
         "List all the \"eslint\" engine rules that have a moderate severity (3) and the recommended \"retire-js\" engine rules with any severity:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended",
-        "Similar to the previous example, but apply the rule overrides and engine settings from the configuration file called \"code-analyzer2.yml\" in the current folder. If, for example, you changed the severity of an \"eslint\" rule from moderate (3) to high (2) in the configuration file, then that rule won't be listed:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended --config-file ./code-analyzer2.yml",
+        "Similar to the previous example, but apply the rule overrides and engine settings from the configuration file called `code-analyzer2.yml` in the current folder. If, for example, you changed the severity of an \"eslint\" rule from moderate (3) to high (2) in the configuration file, then that rule isn't listed:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended --config-file ./code-analyzer2.yml",
         "List the details of the \"getter-return\" rule of the \"eslint\" engine and the rules named \"no-inner-declarations\" in any engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:getter-return --rule-selector no-inner-declarations --view detail",
-        "List the details of the recommended \"eslint\" engine rules that have the tag \"problem\" and high severity level (2) that apply to your workspace folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector eslint:Recommended:problem:2 --view detail --workspace ./force-app"
+        "List the details of the recommended \"eslint\" engine rules that have the tag \"problem\" and high severity level (2) that apply when targeting the files within the folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector eslint:Recommended:problem:2 --view detail --target ./force-app"
       ],
       "flags": {
         "workspace": {
           "char": "w",
-          "description": "If you specify this flag, the command returns a more accurate list of the rules that apply to the files that make up your workspace. Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders. \n\nThis command uses the type of file in the workspace, such as JavaScript or Typescript, to determine the rules to list. For example, if your workspace contains only JavaScript files, the command doesn't list TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nSome engines may be configured to add additional rules based on what it finds in your workspace.  For example, if you set the engines.eslint.auto_discover_eslint_config value of your code-analyzer.yml file to true, then supplying your workspace allows the \"eslint\" engine to examine your files in order to find ESLint configuration files that could potentially add in additional rules.",
+          "description": "Use the `--workspace` flag to return a more accurate list of the rules that apply to the files that make up your workspace. Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders. \n\nThe command uses the types of files in the workspace, such as JavaScript or Typescript, to determine which rules to list. For example, if your workspace contains only JavaScript files, the command doesn't list TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nSome engines may be configured to add additional rules based on what it finds in your workspace. For example, if you set the engines.eslint.auto_discover_eslint_config value of your `code-analyzer.yml` file to true, then supplying your workspace allows the \"eslint\" engine to examine your files in order to find ESLint configuration files that could potentially add in additional rules.\n\nIf you specify `--target` but not `--workspace`, then the current folder '.' is used as your workspace.",
           "name": "workspace",
-          "summary": "Set of files you want to include in the code analysis.",
+          "summary": "Set of files that make up your workspace.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "target": {
+          "char": "t",
+          "description": "Use the `--target` flag to return a more accurate list of the rules that apply to only a subset of targeted files within your workspace. You can specify a target as a file, a folder, or a glob pattern. If you specify this flag multiple times, then the full list of targeted files is the sum of the files and folders.\n\nThe command uses the type of the targeted files, such as JavaScript or Typescript, to determine which rules to list. For example, if you target only JavaScript files, the command doesn't list TypeScript rules. The command uses a file's extension to determine what kind of file it is, such as \".ts\" for TypeScript.\n\nEach targeted file must live within the workspace specified by the –-workspace flag.\n\nIf you specify `--workspace` but not `--target`, then all the files within your workspace are targeted.",
+          "name": "target",
+          "summary": "Subset of files within your workspace that you want to target for analysis.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -111,7 +130,7 @@
         },
         "rule-selector": {
           "char": "r",
-          "description": "Use the --rule-selector flag to select the list of rules based on specific criteria.  For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\". \n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection.  For example, \"--rule-selector eslint:Security\" lists rules associated only with the \"eslint\" engine that have the Security tag.  The flag \"--rule-selector eslint:Security:3\" flag lists the \"eslint\" rules that have the Security tag and moderate severity (3). To add multiple rule selectors together (a union), specify the --rule-selector flag multiple times, such as \"--rule-selector eslint:Recommended --rule-selector retire-js:3\".\n\nRun `<%= config.bin %> <%= command.id %>  --rule-selector all` to list see the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
+          "description": "Use the `--rule-selector` flag to select the list of rules based on specific criteria. For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\". \n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection. For example, `--rule-selector eslint:Security` lists rules associated only with the \"eslint\" engine that have the Security tag. The flag `--rule-selector eslint:Security:3` flag lists the \"eslint\" rules that have the Security tag and moderate severity (3). To add multiple rule selectors together (a union), specify the `--rule-selector` flag multiple times, such as `--rule-selector eslint:Recommended --rule-selector retire-js:3`.\n\nRun `<%= config.bin %> <%= command.id %> --rule-selector all` to list the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
           "name": "rule-selector",
           "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
           "default": [
@@ -124,7 +143,7 @@
         },
         "config-file": {
           "char": "c",
-          "description": "Code Analyzer has an internal default configuration for its rule and engine properties. If you want to override these defaults, you can create a Code Analyzer configuration file.\n\nWe recommend that you name your Code Analyzer configuration file \"code-analyzer.yml\" or \"code-analyzer.yaml\" and put it at the root of your workspace. You then don't need to use this flag when you run the `<%= command.id %>` command from the root of your workspace, because it automatically looks for either file in the current folder, and if found, applies its rule overrides and engine settings. If you want to name the file something else, or put it in an alternative folder, then you must specify this flag.\n\nTo help you get started, use the `code-analyzer config` command to create your first Code Analyzer configuration file. With it, you can change the severity of an existing rule, change a rule's tags, and so on. Then use this flag to specify the file so that the command takes your customizations into account.",
+          "description": "Code Analyzer has an internal default configuration for its rule and engine properties. If you want to override these defaults, you can create a Code Analyzer configuration file.\n\nWe recommend that you name your Code Analyzer configuration file `code-analyzer.yml` or `code-analyzer.yaml` and put it at the root of your workspace. You then don't need to use this flag when you run the `<%= command.id %>` command from the root of your workspace, because it automatically looks for either file in the current folder, and if found, applies its rule overrides and engine settings. If you want to name the file something else, or put it in an alternative folder, then you must specify this flag.\n\nTo help you get started, use the `code-analyzer config` command to create your first Code Analyzer configuration file. With it, you can change the severity of an existing rule, change a rule's tags, and so on. Then use this flag to specify the file so that the command takes your customizations into account.",
           "name": "config-file",
           "summary": "Path to the configuration file used to customize the engines and rules.",
           "hasDynamicHelp": false,
@@ -133,7 +152,7 @@
         },
         "output-file": {
           "char": "f",
-          "description": "If you specify a folder, such as \"--output-file ./out/rules.json\", the folder must already exist or you get an error. If the file already exists, it's overwritten without prompting.\n\nIf you don't specify this flag, the command outputs the rules to only the terminal.",
+          "description": "If you specify a file within folder, such as `--output-file ./out/rules.json`, the folder must already exist, or you get an error. If the file already exists, it's overwritten without prompting.\n\nIf you don't specify this flag, the command outputs the rules to only the terminal.",
           "name": "output-file",
           "summary": "Name of the file where the selected rules are written. The file format depends on the extension you specify; currently, only .json is supported for JSON-formatted output.",
           "hasDynamicHelp": false,
@@ -142,7 +161,7 @@
         },
         "view": {
           "char": "v",
-          "description": "The format `table` is concise and shows minimal output, the format `detail` shows all available information. \n\nIf you specify neither --view nor --output-file, then the default table view is shown. If you specify --output-file but not --view, only summary information is shown in the terminal.",
+          "description": "The format `table` is concise and shows minimal output, the format `detail` shows all available information. \n\nIf you specify neither `--view` nor `--output-file`, then the default table view is shown. If you specify `--output-file` but not `--view`, only summary information is shown in the terminal.",
           "name": "view",
           "summary": "Format to display the rules in the terminal.",
           "hasDynamicHelp": false,
@@ -160,7 +179,6 @@
       "pluginAlias": "@salesforce/plugin-code-analyzer",
       "pluginName": "@salesforce/plugin-code-analyzer",
       "pluginType": "jit",
-      "state": "Beta",
       "strict": true,
       "summary": "List the rules that are available to analyze your code.",
       "enableJsonFlag": false,
@@ -181,15 +199,15 @@
     "code-analyzer:run": {
       "aliases": [],
       "args": {},
-      "description": "You can scan your codebase with the recommended rules. Or use flags to filter the rules based on engines (such as \"retire-js\" or \"eslint\"), rule names, tags, and more. \n\nIf you want to preview the list of rules before you actually run them, use the `code-analyzer rules` command, which also has the \"--rules-selector\", \"--workspace\", and \"--config-file\" flags that together define the list of rules to be run.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.",
+      "description": "You can scan your codebase with the recommended rules. Or use flags to filter the rules based on engines (such as \"retire-js\" or \"eslint\"), rule names, tags, and more. \n\nIf you want to preview the list of rules before you actually run them, use the `code-analyzer rules` command, which also has the `--config-file`, `--rule-selector`, `--target`, and `--workspace` flags that together define the list of rules to be run.\n\nWe're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at https://sfdc.co/CodeAnalyzerFeedback.",
       "examples": [
-        "Analyze code using the default behavior: analyze the files in the current folder (default workspace) using the Recommended rules; display the output in the terminal with the concise table view; and automatically apply rule or engine overrides if a \"code-analyzer.yml\" or \"code-analyzer.yaml\" file exists in the current folder:\n<%= config.bin %> <%= command.id %>",
-        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %> --rule-selector Recommended --workspace . --view table --config-file ./code-analyzer.yml",
+        "Analyze code using the default behavior: analyze all the files in the current folder (default workspace) using the Recommended rules; display the output in the terminal with the concise table view; and automatically apply rule or engine overrides if a `code-analyzer.yml` or `code-analyzer.yaml` file exists in the current folder:\n<%= config.bin %> <%= command.id %>",
+        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %> --rule-selector Recommended --workspace . --target . --view table --config-file ./code-analyzer.yml",
         "Analyze the files using the recommended \"eslint\" rules and show details of the violations:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:Recommended --view detail",
         "Analyze the files using all the \"eslint\" rules:\n<%= config.bin %> <%= command.id %> --rule-selector eslint",
-        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %>  --rule-selector eslint:all",
+        "The previous example is equivalent to this example:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:all",
         "Analyze the files using all rules for all engines:\n<%= config.bin %> <%= command.id %> --rule-selector all",
-        "Analyze files using the recommended \"retire-js\" rules analyze in a workspace that consists of all files in the folder \"./other-source\" and only the Apex class files (extension .cls) in the folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector retire-js:Recommended --workspace ./other-source --workspace ./force-app/**/*.cls",
+        "Analyze files using the recommended \"retire-js\" rules; target all the files in the folder \"./other-source\" and only the Apex class files (extension .cls) in the folder \"./force-app\":\n<%= config.bin %> <%= command.id %> --rule-selector retire-js:Recommended --target ./other-source --target ./force-app/**/*.cls",
         "Specify a custom configuration file and output the results to the \"results.csv\" file in CSV format; the commands fails if it finds a violation that exceeds the moderate severity level (3):\n<%= config.bin %> <%= command.id %> --config-file ./code-analyzer2.yml --output-file results.csv --severity-threshold 3",
         "Analyze the files using all the \"eslint\" engine rules that have a moderate severity (3) and the recommended \"retire-js\" engine rules with any severity:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:3 --rule-selector retire-js:Recommended",
         "Analyze the files using only the \"getter-return\" rule of the \"eslint\" engine and any rule named \"no-inner-declarations\" from any engine:\n<%= config.bin %> <%= command.id %> --rule-selector eslint:getter-return --rule-selector no-inner-declarations"
@@ -197,9 +215,9 @@
       "flags": {
         "workspace": {
           "char": "w",
-          "description": "Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders.",
+          "description": "Typically, a workspace is a single project folder that contains all your files. But it can also consist of one or more folders, one or more files, and use glob patterns (wildcards). If you specify this flag multiple times, then your workspace is the sum of the files and folders.\n\nSome engines often need your entire code base to perform an analysis, even if you want to target only a subset of the files within your workspace , such as with the `--target` flag. For example, the Salesforce Graph Engine might need to compile your entire project in order to properly build a graph so it can perform a data flow analysis on the paths that start in your targeted files.\n\nIf you don't specify the `--workspace` flag, then the current folder '.' is used as your workspace.",
           "name": "workspace",
-          "summary": "Set of files you want to include in the code analysis.",
+          "summary": "Set of files that make up your workspace.",
           "default": [
             "."
           ],
@@ -208,12 +226,11 @@
           "multiple": true,
           "type": "option"
         },
-        "path-start": {
-          "char": "s",
-          "description": "If you don't specify this flag, then any path-based analysis rules automatically discover and use all starting points found in your workspace. Use this flag to restrict the starting points to only those you want in your code analysis. \n\nThis flag only applies to path-based analysis rules, which are of type DataFlow and Flow. These types of rules are only available from some engines, like the Salesforce Graph Engine, \"sfge\" for example.\n\nIf you specify a file or a folder as your starting point, then the analysis uses only the methods that have public or global accessibility. \n\nTo specify individual methods as a starting point, use the syntax \"<file>#methodName\" to select a single method or \"<file>#methodName1;methodName2\" to select multiple methods. For example, \"SomeClass.cls#method1\" (single method) or \"SomeClass.cls#method1;method2\" (multiple methods).\n\nYou can use glob patterns (wildcards) only when specifying files and folders; you can't use glob patterns when specifying individual methods.",
-          "hidden": true,
-          "name": "path-start",
-          "summary": "Starting points within your workspace to restrict any path-based analysis rules to.",
+        "target": {
+          "char": "t",
+          "description": "You can specify a target as a file, a folder, or a glob pattern.\n\nIf you specify this flag multiple times, then the full list of targeted files is the sum of the files and folders.\n\nEach targeted file must live within the workspace that you specified with the `–-workspace` flag.\n\nIf you don't specify the `--target` flag, then all the files within your workspace (specified by the `--workspace` flag) are targeted for analysis.",
+          "name": "target",
+          "summary": "Subset of files within your workspace to be targeted for analysis.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -221,7 +238,7 @@
         },
         "rule-selector": {
           "char": "r",
-          "description": "Use the --rule-selector flag to select the list of rules to run based on specific criteria.  For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\".\n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection.  For example, \"--rule-selector eslint:Security\" runs rules associated only with the \"eslint\" engine that have the Security tag.  The flag \"--rule-selector eslint:Security:3\" flag runs the \"eslint\" rules that have the Security tag and moderate severity (3). To add multiple rule selectors together (a union), specify the --rule-selector flag multiple times, such as \"--rule-selector eslint:Recommended --rule-selector retire-js:3\".\n\nRun `<%= config.bin %> code-analyzer rules --rule-selector all` to see the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
+          "description": "Use the `--rule-selector` flag to select the list of rules to run based on specific criteria. For example, you can select by engine, such as the rules associated with the \"retire-js\" or \"eslint\" engine. Or select by the severity of the rules, such as high or moderate. You can also select rules using tag values or rule names. Every rule has a name, which is unique within the scope of an engine. Most rules have tags, although it's not required. An example of a tag is \"Recommended\".\n\nYou can combine different criteria using colons to further filter the list; the colon works as an intersection. For example, `--rule-selector eslint:Security` runs rules associated only with the \"eslint\" engine that have the Security tag. The flag `--rule-selector eslint:Security:3` flag runs the \"eslint\" rules that have the Security tag and moderate severity (3). To add multiple rule selectors together (a union), specify the `--rule-selector` flag multiple times, such as `--rule-selector eslint:Recommended --rule-selector retire-js:3`.\n\nRun `<%= config.bin %> code-analyzer rules --rule-selector all` to see the possible values for engine name, rule name, tags, and severity levels that you can use with this flag.",
           "name": "rule-selector",
           "summary": "Selection of rules, based on engine name, severity level, rule name, tag, or a combination of criteria separated by colons.",
           "default": [
@@ -233,7 +250,7 @@
           "type": "option"
         },
         "severity-threshold": {
-          "char": "t",
+          "char": "s",
           "description": "You can specify either a number (2) or its equivalent string (\"High\").",
           "name": "severity-threshold",
           "summary": "Severity level of a found violation that must be met or exceeded to cause this command to fail with a non-zero exit code.",
@@ -243,7 +260,7 @@
         },
         "view": {
           "char": "v",
-          "description": "The format `table` is concise and shows minimal output, the format `detail` shows all available information.\n\nIf you specify neither --view nor --output-file, then the default table view is shown. If you specify --output-file but not --view, only summary information is shown.",
+          "description": "The format `table` is concise and shows minimal output, the format `detail` shows all available information.\n\nIf you specify neither `--view` nor `--output-file`, then the default table view is shown. If you specify `--output-file` but not `--view`, only summary information is shown.",
           "name": "view",
           "summary": "Format to display the command results in the terminal.",
           "hasDynamicHelp": false,
@@ -256,7 +273,7 @@
         },
         "output-file": {
           "char": "f",
-          "description": "If you don't specify this flag, the command outputs the results to only the terminal. Use this flag to print the results to a file; the format of the results depends on the extension you provide. For example, \"--output-file results.csv\" creates a comma-separated values file. You can specify one of these extensions:\n\n- .csv\n- .html or .htm\n- .json\n- .sarif or .sarif.json\n- .xml\n\nTo output the results to multiple files, specify this flag multiple times.  For example: \"--output-file results.json --output-file report.html\" creates both a JSON results file and an HTML file.\n\nIf you specify a folder, such as \"--output-file ./out/results.json\", the folder must already exist or you get an error. If the file already exists, it's overwritten without prompting.",
+          "description": "If you don't specify this flag, the command outputs the results to only the terminal. Use this flag to print the results to a file; the format of the results depends on the extension you provide. For example, `--output-file results.csv` creates a comma-separated values file. You can specify one of these extensions:\n\n- .csv\n- .html or .htm\n- .json\n- .sarif or .sarif.json\n- .xml\n\nTo output the results to multiple files, specify this flag multiple times. For example: `--output-file results.json --output-file report.html` creates both a JSON results file and an HTML file.\n\nIf you specify a file within a folder, such as `--output-file ./out/results.json`, the folder must already exist, or you get an error. If the file already exists, it's overwritten without prompting.",
           "name": "output-file",
           "summary": "Name of the file where the analysis results are written. The file format depends on the extension you specify, such as .csv, .html, .xml, and so on.",
           "delimiter": ",",
@@ -266,7 +283,7 @@
         },
         "config-file": {
           "char": "c",
-          "description": "Code Analyzer has an internal default configuration for its rule and engine properties. If you want to override these defaults, you can create a Code Analyzer configuration file.\n\nWe recommend that you name your Code Analyzer configuration file \"code-analyzer.yml\" or \"code-analyzer.yaml\" and put it at the root of your workspace. You then don't need to use this flag when you run the `<%= command.id %>` command from the root of your workspace, because it automatically looks for either file in the current folder, and if found, applies its rule overrides and engine settings. If you want to name the file something else, or put it in an alternative folder, then you must specify this flag.\n\nTo help you get started, use the `code-analyzer config` command to create your first Code Analyzer configuration file. With it, you can change the severity of an existing rule, change a rule's tags, and so on. Then use this flag to specify the file so that the command takes your customizations into account.",
+          "description": "Code Analyzer has an internal default configuration for its rule and engine properties. If you want to override these defaults, you can create a Code Analyzer configuration file.\n\nWe recommend that you name your Code Analyzer configuration file `code-analyzer.yml` or `code-analyzer.yaml` and put it at the root of your workspace. You then don't need to use this flag when you run the `<%= command.id %>` command from the root of your workspace, because it automatically looks for either file in the current folder, and if found, applies its rule overrides and engine settings. If you want to name the file something else, or put it in an alternative folder, then you must specify this flag.\n\nTo help you get started, use the `code-analyzer config` command to create your first Code Analyzer configuration file. With it, you can change the severity of an existing rule, change a rule's tags, and so on. Then use this flag to specify the file so that the command takes your customizations into account.",
           "name": "config-file",
           "summary": "Path to the configuration file used to customize the engines and rules.",
           "hasDynamicHelp": false,
@@ -280,7 +297,6 @@
       "pluginAlias": "@salesforce/plugin-code-analyzer",
       "pluginName": "@salesforce/plugin-code-analyzer",
       "pluginType": "jit",
-      "state": "Beta",
       "strict": true,
       "summary": "Analyze your code with a selection of rules to ensure good coding practices.",
       "enableJsonFlag": false,
@@ -5918,5 +5934,5 @@
       ]
     }
   },
-  "version": "2.87.5"
+  "version": "2.87.6"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "2.87.5",
+  "version": "2.87.6",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run.js",
@@ -75,7 +75,7 @@
       "@salesforce/plugin-user"
     ],
     "jitPlugins": {
-      "@salesforce/plugin-code-analyzer": "5.0.0-beta.3",
+      "@salesforce/plugin-code-analyzer": "5.0.0",
       "@salesforce/plugin-community": "3.3.21",
       "@salesforce/plugin-custom-metadata": "3.3.51",
       "@salesforce/plugin-dev": "2.5.1",
@@ -83,7 +83,7 @@
       "@salesforce/plugin-flow": "1.0.2",
       "@salesforce/plugin-signups": "2.6.23",
       "@salesforce/sfdx-plugin-lwc-test": "1.2.1",
-      "@salesforce/sfdx-scanner": "4.11.0",
+      "@salesforce/sfdx-scanner": "4.12.0",
       "@salesforce/plugin-agent": "1.20.12"
     },
     "devPlugins": [
@@ -161,8 +161,8 @@
     "@salesforce/plugin-apex": "3.6.15",
     "@salesforce/plugin-api": "1.3.3",
     "@salesforce/plugin-auth": "3.6.115",
-    "@salesforce/plugin-data": "4.0.28",
-    "@salesforce/plugin-deploy-retrieve": "3.22.4",
+    "@salesforce/plugin-data": "4.0.29",
+    "@salesforce/plugin-deploy-retrieve": "3.22.5",
     "@salesforce/plugin-info": "3.4.56",
     "@salesforce/plugin-limits": "3.3.52",
     "@salesforce/plugin-marketplace": "1.3.8",