@salesforce/cli 2.103.4 → 2.103.6

package/README.md

@@ -25,7 +25,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (--version|-v)
-@salesforce/cli/2.103.4 linux-x64 node-v22.18.0
+@salesforce/cli/2.103.6 linux-x64 node-v22.18.0
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND
@@ -126,7 +126,6 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 - [`sf org list sobject record-counts`](#sf-org-list-sobject-record-counts)
 - [`sf org list users`](#sf-org-list-users)
 - [`sf org login access-token`](#sf-org-login-access-token)
-- [`sf org login device`](#sf-org-login-device)
 - [`sf org login jwt`](#sf-org-login-jwt)
 - [`sf org login sfdx-url`](#sf-org-login-sfdx-url)
 - [`sf org login web`](#sf-org-login-web)
@@ -242,7 +241,7 @@ EXAMPLES
     $ sf agent activate --api-name Resort_Manager --target-org my-org
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/activate.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/activate.ts)_
 
 ## `sf agent create`
 
@@ -304,7 +303,7 @@ EXAMPLES
     $ sf agent create --name "Resort Manager" --spec specs/resortManagerAgent.yaml --preview
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/create.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/create.ts)_
 
 ## `sf agent deactivate`
 
@@ -344,7 +343,7 @@ EXAMPLES
     $ sf agent deactivate --api-name Resort_Manager --target-org my-org
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/deactivate.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/deactivate.ts)_
 
 ## `sf agent generate agent-spec`
 
@@ -449,7 +448,7 @@ EXAMPLES
     $ sf agent generate agent-spec --tone formal --agent-user resortmanager@myorg.com
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/generate/agent-spec.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/generate/agent-spec.ts)_
 
 ## `sf agent generate template`
 
@@ -497,7 +496,7 @@ EXAMPLES
       force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml --agent-version 1
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/generate/template.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/generate/template.ts)_
 
 ## `sf agent generate test-spec`
 
@@ -558,7 +557,7 @@ EXAMPLES
       force-app//main/default/aiEvaluationDefinitions/Resort_Manager_Tests.aiEvaluationDefinition-meta.xml
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/generate/test-spec.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/generate/test-spec.ts)_
 
 ## `sf agent preview`
 
@@ -622,7 +621,7 @@ EXAMPLES
       transcripts/my-preview
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/preview.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/preview.ts)_
 
 ## `sf agent test create`
 
@@ -677,7 +676,7 @@ EXAMPLES
     $ sf agent test create --spec specs/Resort_Manager-testSpec.yaml --api-name Resort_Manager_Test --preview
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/test/create.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/test/create.ts)_
 
 ## `sf agent test list`
 
@@ -712,7 +711,7 @@ EXAMPLES
     $ sf agent test list --target-org my-org
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/test/list.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/test/list.ts)_
 
 ## `sf agent test results`
 
@@ -721,7 +720,7 @@ Get the results of a completed agent test run.
 ```
 USAGE
   $ sf agent test results -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>] [--result-format
-    json|human|junit|tap] [-d <value>]
+    json|human|junit|tap] [-d <value>] [--verbose]
 
 FLAGS
   -d, --output-dir=<value>      Directory to write the agent test results into.
@@ -731,6 +730,7 @@ FLAGS
       --api-version=<value>     Override the api version used for api requests made by this command
       --result-format=<option>  [default: human] Format of the agent test run results.
                                 <options: json|human|junit|tap>
+      --verbose                 Show generated data in the test results output.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -766,9 +766,18 @@ FLAG DESCRIPTIONS
 
     If the agent test run completes, write the results to the specified directory. If the test is still running, the
     test results aren't written.
+
+  --verbose  Show generated data in the test results output.
+
+    When enabled, includes detailed generated data (such as invoked actions) in the human-readable test results output.
+    This is useful for debugging test failures and understanding what actions were actually invoked during the test run.
+
+    The generated data is in JSON format and includes the Apex classes or Flows that were invoked, the Salesforce
+    objects that were touched, and so on. Use the JSON structure of this information to build the test case JSONPath
+    expression when using custom evaluations.
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/test/results.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/test/results.ts)_
 
 ## `sf agent test resume`
 
@@ -777,7 +786,7 @@ Resume an agent test that you previously started in your org so you can view the
 ```
 USAGE
   $ sf agent test resume -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-i <value>] [-r] [-w
-    <value>] [--result-format json|human|junit|tap] [-d <value>]
+    <value>] [--result-format json|human|junit|tap] [-d <value>] [--verbose]
 
 FLAGS
   -d, --output-dir=<value>      Directory to write the agent test results into.
@@ -790,6 +799,7 @@ FLAGS
       --api-version=<value>     Override the api version used for api requests made by this command
       --result-format=<option>  [default: human] Format of the agent test run results.
                                 <options: json|human|junit|tap>
+      --verbose                 Show generated data in the test results output.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -829,9 +839,18 @@ FLAG DESCRIPTIONS
 
     If the agent test run completes, write the results to the specified directory. If the test is still running, the
     test results aren't written.
+
+  --verbose  Show generated data in the test results output.
+
+    When enabled, includes detailed generated data (such as invoked actions) in the human-readable test results output.
+    This is useful for debugging test failures and understanding what actions were actually invoked during the test run.
+
+    The generated data is in JSON format and includes the Apex classes or Flows that were invoked, the Salesforce
+    objects that were touched, and so on. Use the JSON structure of this information to build the test case JSONPath
+    expression when using custom evaluations.
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/test/resume.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/test/resume.ts)_
 
 ## `sf agent test run`
 
@@ -840,7 +859,7 @@ Start an agent test in your org.
 ```
 USAGE
   $ sf agent test run -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-n <value>] [-w <value>]
-    [--result-format json|human|junit|tap] [-d <value>]
+    [--result-format json|human|junit|tap] [-d <value>] [--verbose]
 
 FLAGS
   -d, --output-dir=<value>      Directory to write the agent test results into.
@@ -853,6 +872,7 @@ FLAGS
       --api-version=<value>     Override the api version used for api requests made by this command
       --result-format=<option>  [default: human] Format of the agent test run results.
                                 <options: json|human|junit|tap>
+      --verbose                 Show generated data in the test results output.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -893,9 +913,18 @@ FLAG DESCRIPTIONS
 
     If the agent test run completes, write the results to the specified directory. If the test is still running, the
     test results aren't written.
+
+  --verbose  Show generated data in the test results output.
+
+    When enabled, includes detailed generated data (such as invoked actions) in the human-readable test results output.
+    This is useful for debugging test failures and understanding what actions were actually invoked during the test run.
+
+    The generated data is in JSON format and includes the Apex classes or Flows that were invoked, the Salesforce
+    objects that were touched, and so on. Use the JSON structure of this information to build the test case JSONPath
+    expression when using custom evaluations.
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.3/src/commands/agent/test/run.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.24.4/src/commands/agent/test/run.ts)_
 
 ## `sf alias list`
 
@@ -2046,7 +2075,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.52/src/commands/data/bulk/results.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/bulk/results.ts)_
 
 ## `sf data create file`
 
@@ -2095,7 +2124,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.52/src/commands/data/create/file.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/create/file.ts)_
 
 ## `sf data create record`
 
@@ -2151,7 +2180,7 @@ EXAMPLES
       TracedEntityId=01p17000000R6bLAAS"
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/create/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/create/record.ts)_
 
 ## `sf data delete bulk`
 
@@ -2159,11 +2188,10 @@ Bulk delete records from an org using a CSV file. Uses Bulk API 2.0.
 
 ```
 USAGE
-  $ sf data delete bulk -o <value> -s <value> [--json] [--flags-dir <value>] [--api-version <value>] [-w <value> | -a]
+  $ sf data delete bulk -o <value> -s <value> [--json] [--flags-dir <value>] [--api-version <value>] [-w <value>]
     (--line-ending CRLF|LF -f <value>) [--hard-delete]
 
 FLAGS
-  -a, --async                 Run the command asynchronously.
   -f, --file=<value>          (required) CSV file that contains the IDs of the records to update or delete.
   -o, --target-org=<value>    (required) Username or alias of the target org. Not required if the `target-org`
                               configuration variable is already set.
@@ -2211,7 +2239,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.52/src/commands/data/delete/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/delete/bulk.ts)_
 
 ## `sf data delete record`
 
@@ -2272,7 +2300,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.52/src/commands/data/delete/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/delete/record.ts)_
 
 ## `sf data delete resume`
 
@@ -2311,7 +2339,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.52/src/commands/data/delete/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/delete/resume.ts)_
 
 ## `sf data export bulk`
 
@@ -2320,7 +2348,7 @@ Bulk export records from an org into a file using a SOQL query. Uses Bulk API 2.
 ```
 USAGE
   $ sf data export bulk -o <value> --output-file <value> -r csv|json [--json] [--flags-dir <value>] [--api-version
-    <value>] [-w <minutes> | --async] [-q <value> | --query-file <value>] [--all-rows] [--column-delimiter
+    <value>] [-w <minutes>] [-q <value> | --query-file <value>] [--all-rows] [--column-delimiter
     BACKQUOTE|CARET|COMMA|PIPE|SEMICOLON|TAB] [--line-ending LF|CRLF]
 
 FLAGS
@@ -2333,7 +2361,6 @@ FLAGS
       --all-rows                   Include records that have been soft-deleted due to a merge or delete. By default,
                                    deleted records are not returned.
       --api-version=<value>        Override the api version used for api requests made by this command
-      --async                      Don't wait for the job to complete.
       --column-delimiter=<option>  Column delimiter to be used when writing CSV output. Default is COMMA.
                                    <options: BACKQUOTE|CARET|COMMA|PIPE|SEMICOLON|TAB>
       --line-ending=<option>       Line ending to be used when writing CSV output. Default value on Windows is is
@@ -2357,8 +2384,8 @@ DESCRIPTION
   JSON format.
 
   Bulk exports can take a while, depending on how many records are returned by the SOQL query. If the command times out,
-  or you specified the --async flag, the command displays the job ID. To see the status and get the results of the job,
-  run "sf data export resume" and pass the job ID to the --job-id flag.
+  the command displays the job ID. To see the status and get the results of the job, run "sf data export resume" and
+  pass the job ID to the --job-id flag.
 
   IMPORTANT: This command uses Bulk API 2.0, which limits the type of SOQL queries you can run. For example, you can't
   use aggregate functions such as count(). For the complete list of limitations, see the "SOQL Considerations" section
@@ -2377,15 +2404,9 @@ EXAMPLES
 
     $ sf data export bulk --query "SELECT Id, Name, Account.Name FROM Contact" --output-file export-accounts.json \
       --result-format json --wait 10 --all-rows
-
-  Export asynchronously; the command immediately returns a job ID that you then pass to the "sf data export resume"
-  command:
-
-    $ sf data export bulk --query "SELECT Id, Name, Account.Name FROM Contact" --output-file export-accounts.json \
-      --result-format json --async
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/export/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/export/bulk.ts)_
 
 ## `sf data export resume`
 
@@ -2407,9 +2428,9 @@ GLOBAL FLAGS
 DESCRIPTION
   Resume a bulk export job that you previously started. Uses Bulk API 2.0.
 
-  When the original "data export bulk" command either times out or is run with the --async flag, it displays a job ID.
-  To see the status and get the results of the bulk export, run this command by either passing it the job ID or using
-  the --use-most-recent flag to specify the most recent bulk export job.
+  When the original "data export bulk" command times out, it displays a job ID. To see the status and get the results of
+  the bulk export, run this command by either passing it the job ID or using the --use-most-recent flag to specify the
+  most recent bulk export job.
 
   Using either `--job-id` or `--use-most-recent` will properly resolve to the correct org where the bulk job was started
   based on the cached data by "data export bulk".
@@ -2424,7 +2445,7 @@ EXAMPLES
     $ sf data export resume --use-most-recent
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/export/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/export/resume.ts)_
 
 ## `sf data export tree`
 
@@ -2484,7 +2505,7 @@ EXAMPLES
       my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/export/tree.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/export/tree.ts)_
 
 ## `sf data get record`
 
@@ -2548,7 +2569,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.52/src/commands/data/get/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/get/record.ts)_
 
 ## `sf data import bulk`
 
@@ -2556,11 +2577,10 @@ Bulk import records into a Salesforce object from a CSV file. Uses Bulk API 2.0.
 
 ```
 USAGE
-  $ sf data import bulk -s <value> -o <value> [--json] [--flags-dir <value>] [-a | -w <value>] [--api-version <value>]
+  $ sf data import bulk -s <value> -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-w <value>]
     (--line-ending CRLF|LF -f <value>) [--column-delimiter BACKQUOTE|CARET|COMMA|PIPE|SEMICOLON|TAB]
 
 FLAGS
-  -a, --async                      Don't wait for the command to complete.
   -f, --file=<value>               (required) CSV file that contains the Salesforce object records you want to import.
   -o, --target-org=<value>         (required) Username or alias of the target org. Not required if the `target-org`
                                    configuration variable is already set.
@@ -2586,9 +2606,9 @@ DESCRIPTION
 
   All the records in the CSV file must be for the same Salesforce object. Specify the object with the `--sobject` flag.
 
-  Bulk imports can take a while, depending on how many records are in the CSV file. If the command times out, or you
-  specified the --async flag, the command displays the job ID. To see the status and get the results of the job, run "sf
-  data import resume" and pass the job ID to the --job-id flag.
+  Bulk imports can take a while, depending on how many records are in the CSV file. If the command times out, the
+  command displays the job ID. To see the status and get the results of the job, run "sf data import resume" and pass
+  the job ID to the --job-id flag.
 
   For information and examples about how to prepare your CSV files, see "Prepare Data to Ingest" in the "Bulk API 2.0
   and Bulk API Developer Guide"
@@ -2599,14 +2619,9 @@ EXAMPLES
   in 10 minutes, the command ends and displays a job ID:
 
     $ sf data import bulk --file accounts.csv --sobject Account --wait 10 --target-org my-scratch
-
-  Import asynchronously and use the default org; the command immediately returns a job ID that you then pass to the
-  "sf data import resume" command:
-
-    $ sf data import bulk --file accounts.csv --sobject Account --async
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/import/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/import/bulk.ts)_
 
 ## `sf data import resume`
 
@@ -2628,9 +2643,9 @@ GLOBAL FLAGS
 DESCRIPTION
   Resume a bulk import job that you previously started. Uses Bulk API 2.0.
 
-  When the original "sf data import bulk" command either times out or is run with the --async flag, it displays a job
-  ID. To see the status and get the results of the bulk import, run this command by either passing it the job ID or
-  using the --use-most-recent flag to specify the most recent bulk import job.
+  When the original "sf data import bulk" command times out, it displays a job ID. To see the status and get the results
+  of the bulk import, run this command by either passing it the job ID or using the --use-most-recent flag to specify
+  the most recent bulk import job.
 
 EXAMPLES
   Resume a bulk import job to your default org using an ID:
@@ -2642,7 +2657,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.52/src/commands/data/import/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/import/resume.ts)_
 
 ## `sf data import tree`
 
@@ -2706,7 +2721,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.52/src/commands/data/import/tree.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/import/tree.ts)_
 
 ## `sf data query`
 
@@ -2759,7 +2774,7 @@ EXAMPLES
     $ sf data query --query "SELECT Name FROM ApexTrigger" --use-tooling-api
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/query.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/query.ts)_
 
 ## `sf data resume`
 
@@ -2796,7 +2811,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.52/src/commands/data/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/resume.ts)_
 
 ## `sf data search`
 
@@ -2846,7 +2861,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.52/src/commands/data/search.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/search.ts)_
 
 ## `sf data update bulk`
 
@@ -2854,11 +2869,10 @@ Bulk update records to an org from a CSV file. Uses Bulk API 2.0.
 
 ```
 USAGE
-  $ sf data update bulk -s <value> -o <value> [--json] [--flags-dir <value>] [-a] [-w <value>] [--api-version <value>]
+  $ sf data update bulk -s <value> -o <value> [--json] [--flags-dir <value>] [-w <value>] [--api-version <value>]
     (--line-ending CRLF|LF -f <value>) [--column-delimiter BACKQUOTE|CARET|COMMA|PIPE|SEMICOLON|TAB]
 
 FLAGS
-  -a, --async                      Don't wait for the command to complete.
   -f, --file=<value>               (required) CSV file that contains the Salesforce object records you want to update.
   -o, --target-org=<value>         (required) Username or alias of the target org. Not required if the `target-org`
                                    configuration variable is already set.
@@ -2887,9 +2901,9 @@ DESCRIPTION
   contain only existing records; if a record in the file doesn't currently exist in the Salesforce object, the command
   fails. Consider using "sf data upsert bulk" if you also want to insert new records.
 
-  Bulk updates can take a while, depending on how many records are in the CSV file. If the command times out, or you
-  specified the --async flag, the command displays the job ID. To see the status and get the results of the job, run "sf
-  data update resume" and pass the job ID to the --job-id flag.
+  Bulk updates can take a while, depending on how many records are in the CSV file. If the command times out, the
+  command displays the job ID. To see the status and get the results of the job, run "sf data update resume" and pass
+  the job ID to the --job-id flag.
 
   For information and examples about how to prepare your CSV files, see "Prepare Data to Ingest" in the "Bulk API 2.0
   and Bulk API Developer Guide"
@@ -2900,14 +2914,9 @@ EXAMPLES
   in 10 minutes, the command ends and displays a job ID:
 
     $ sf data update bulk --file accounts.csv --sobject Account --wait 10 --target-org my-scratch
-
-  Update asynchronously and use the default org; the command immediately returns a job ID that you then pass to the
-  "sf data update resume" command:
-
-    $ sf data update bulk --file accounts.csv --sobject Account --async
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/update/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/update/bulk.ts)_
 
 ## `sf data update record`
 
@@ -2969,7 +2978,7 @@ EXAMPLES
       "ExpirationDate=2017-12-01T00:58:04.000+0000"
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/update/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/update/record.ts)_
 
 ## `sf data update resume`
 
@@ -2991,9 +3000,9 @@ GLOBAL FLAGS
 DESCRIPTION
   Resume a bulk update job that you previously started. Uses Bulk API 2.0.
 
-  When the original "sf data update bulk" command either times out or is run with the --async flag, it displays a job
-  ID. To see the status and get the results of the bulk update, run this command by either passing it the job ID or
-  using the --use-most-recent flag to specify the most recent bulk update job.
+  When the original "sf data update bulk" command times out, it displays a job ID. To see the status and get the results
+  of the bulk update, run this command by either passing it the job ID or using the --use-most-recent flag to specify
+  the most recent bulk update job.
 
   Using either `--job-id` or `--use-most-recent` will properly resolve to the correct org where the bulk job was started
   based on the cached data by "data update bulk".
@@ -3008,7 +3017,7 @@ EXAMPLES
     $ sf data update resume --use-most-recent
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/update/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/update/resume.ts)_
 
 ## `sf data upsert bulk`
 
@@ -3017,10 +3026,9 @@ Bulk upsert records to an org from a CSV file. Uses Bulk API 2.0.
 ```
 USAGE
   $ sf data upsert bulk -o <value> -s <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>] [-w
-    <value> | -a] (--line-ending CRLF|LF -f <value>) [--column-delimiter BACKQUOTE|CARET|COMMA|PIPE|SEMICOLON|TAB]
+    <value>] (--line-ending CRLF|LF -f <value>) [--column-delimiter BACKQUOTE|CARET|COMMA|PIPE|SEMICOLON|TAB]
 
 FLAGS
-  -a, --async                      Run the command asynchronously.
   -f, --file=<value>               (required) CSV file that contains the IDs of the records to update or delete.
   -i, --external-id=<value>        (required) Name of the external ID field, or the Id field.
   -o, --target-org=<value>         (required) Username or alias of the target org. Not required if the `target-org`
@@ -3065,7 +3073,7 @@ EXAMPLES
       my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/data/upsert/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/upsert/bulk.ts)_
 
 ## `sf data upsert resume`
 
@@ -3104,7 +3112,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.52/src/commands/data/upsert/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/data/upsert/resume.ts)_
 
 ## `sf doctor`
 
@@ -3199,7 +3207,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.52/src/commands/force/data/bulk/delete.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/force/data/bulk/delete.ts)_
 
 ## `sf force data bulk status`
 
@@ -3236,7 +3244,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.52/src/commands/force/data/bulk/status.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/force/data/bulk/status.ts)_
 
 ## `sf force data bulk upsert`
 
@@ -3294,7 +3302,7 @@ EXAMPLES
       --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.52/src/commands/force/data/bulk/upsert.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.53/src/commands/force/data/bulk/upsert.ts)_
 
 ## `sf help [COMMAND]`
 
@@ -4553,7 +4561,7 @@ EXAMPLES
     $ sf org list auth
 ```
 
-_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.7.19/src/commands/org/list/auth.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.8.1/src/commands/org/list/auth.ts)_
 
 ## `sf org list limits`
 
@@ -4853,67 +4861,7 @@ FLAG DESCRIPTIONS
     To specify a sandbox, set --instance-url to "https://<MyDomainName>--<SandboxName>.sandbox.my.salesforce.com".
 ```
 
-_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.7.19/src/commands/org/login/access-token.ts)_
-
-## `sf org login device`
-
-Authorize an org using a device code.
-
-```
-USAGE
-  $ sf org login device [--json] [--flags-dir <value>] [-i <value>] [-r <value>] [-d] [-s] [-a <value>]
-
-FLAGS
-  -a, --alias=<value>         Alias for the org.
-  -d, --set-default-dev-hub   Set the authenticated org as the default Dev Hub.
-  -i, --client-id=<value>     OAuth client ID (also called consumer key) of your custom connected app.
-  -r, --instance-url=<value>  URL of the instance that the org lives on.
-  -s, --set-default           Set the authenticated org as the default that all org-related commands run against.
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Authorize an org using a device code.
-
-  Use this command to allow a device to connect to an org.
-
-  When you run this command, it first displays an 8-digit device code and the URL for verifying the code on your org.
-  The default instance URL is https://login.salesforce.com, so if the org you're authorizing is on a different instance,
-  use the --instance-url. The command waits while you complete the verification. Open a browser and navigate to the
-  displayed verification URL, enter the code, then click Connect. If you aren't already logged into your org, log in,
-  and then you're prompted to allow the device to connect to the org. After you successfully authorize the org, you can
-  close the browser window.
-
-ALIASES
-  $ sf force auth device login
-  $ sf auth device login
-
-EXAMPLES
-  Authorize an org using a device code, give the org the alias TestOrg1, and set it as your default Dev Hub org:
-
-    $ sf org login device --set-default-dev-hub --alias TestOrg1
-
-  Authorize an org in which you've created a custom connected app with the specified client ID (consumer key):
-
-    $ sf org login device --client-id <OAuth client id>
-
-  Authorize a sandbox org with the specified instance URL:
-
-    $ sf org login device --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com
-
-FLAG DESCRIPTIONS
-  -r, --instance-url=<value>  URL of the instance that the org lives on.
-
-    If you specify an --instance-url value, this value overrides the sfdcLoginUrl value in your sfdx-project.json file.
-
-    To specify a My Domain URL, use the format "https://<MyDomainName>.my.salesforce.com".
-
-    To specify a sandbox, set --instance-url to "https://<MyDomainName>--<SandboxName>.sandbox.my.salesforce.com".
-```
-
-_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.7.19/src/commands/org/login/device.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.8.1/src/commands/org/login/access-token.ts)_
 
 ## `sf org login jwt`
 
@@ -5004,7 +4952,7 @@ FLAG DESCRIPTIONS
     To specify a sandbox, set --instance-url to "https://<MyDomainName>--<SandboxName>.sandbox.my.salesforce.com".
 ```
 
-_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.7.19/src/commands/org/login/jwt.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.8.1/src/commands/org/login/jwt.ts)_
 
 ## `sf org login sfdx-url`
 
@@ -5074,7 +5022,7 @@ EXAMPLES
   $ echo url | sf org login sfdx-url --sfdx-url-stdin
 ```
 
-_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.7.19/src/commands/org/login/sfdx-url.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.8.1/src/commands/org/login/sfdx-url.ts)_
 
 ## `sf org login web`
 
@@ -5179,7 +5127,7 @@ FLAG DESCRIPTIONS
     To specify a sandbox, set --instance-url to "https://<MyDomainName>--<SandboxName>.sandbox.my.salesforce.com".
 ```
 
-_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.7.19/src/commands/org/login/web.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.8.1/src/commands/org/login/web.ts)_
 
 ## `sf org logout`
 
@@ -5245,7 +5193,7 @@ FLAG DESCRIPTIONS
     All orgs includes Dev Hubs, sandboxes, DE orgs, and expired, deleted, and unknown-status scratch orgs.
 ```
 
-_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.7.19/src/commands/org/logout.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/3.8.1/src/commands/org/logout.ts)_
 
 ## `sf org open`
 

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@salesforce/cli",
-  "version": "2.103.4",
+  "version": "2.103.6",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@salesforce/cli",
-      "version": "2.103.4",
+      "version": "2.103.6",
       "hasInstallScript": true,
       "license": "Apache-2.0",
       "dependencies": {
@@ -24,11 +24,11 @@
         "@oclif/plugin-which": "3.2.39",
         "@salesforce/core": "^8.9.1",
         "@salesforce/kit": "^3.1.6",
-        "@salesforce/plugin-agent": "1.24.3",
+        "@salesforce/plugin-agent": "1.24.4",
         "@salesforce/plugin-apex": "3.6.19",
         "@salesforce/plugin-api": "1.3.3",
-        "@salesforce/plugin-auth": "3.7.19",
-        "@salesforce/plugin-data": "4.0.52",
+        "@salesforce/plugin-auth": "3.8.1",
+        "@salesforce/plugin-data": "4.0.53",
         "@salesforce/plugin-deploy-retrieve": "3.22.41",
         "@salesforce/plugin-info": "3.4.81",
         "@salesforce/plugin-limits": "3.3.64",
@@ -38,7 +38,7 @@
         "@salesforce/plugin-schema": "3.3.78",
         "@salesforce/plugin-settings": "2.4.42",
         "@salesforce/plugin-sobject": "1.4.68",
-        "@salesforce/plugin-telemetry": "3.6.54",
+        "@salesforce/plugin-telemetry": "3.6.55",
         "@salesforce/plugin-templates": "56.3.60",
         "@salesforce/plugin-trust": "3.7.113",
         "@salesforce/plugin-user": "3.6.34",
@@ -4741,9 +4741,9 @@
       }
     },
     "node_modules/@salesforce/core": {
-      "version": "8.19.1",
-      "resolved": "https://registry.npmjs.org/@salesforce/core/-/core-8.19.1.tgz",
-      "integrity": "sha512-HPJxus0W4S1aoT4Qn6mG2s9Ik/mZ59rXNUFc2c+BgEAs28khbZOLR2uiZYexNpXIIZnCrSbb+v1t8IW/idIyCA==",
+      "version": "8.20.0",
+      "resolved": "https://registry.npmjs.org/@salesforce/core/-/core-8.20.0.tgz",
+      "integrity": "sha512-WZoab9aHDbYXUh4nO+91PNLHpiPfK408qjn3l6Sbgck2d0bzYkW5wOmuv5D5yWrEybs9kGosrW/e9liKPGmgng==",
       "license": "BSD-3-Clause",
       "dependencies": {
         "@jsforce/jsforce-node": "^3.10.1",
@@ -4986,9 +4986,9 @@
       }
     },
     "node_modules/@salesforce/plugin-agent": {
-      "version": "1.24.3",
-      "resolved": "https://registry.npmjs.org/@salesforce/plugin-agent/-/plugin-agent-1.24.3.tgz",
-      "integrity": "sha512-ck2cOVvnaUuuukajUkBvxgAHy53lYbzCxMXr6m1L99ZRYO9l44tosvUfJMkBb4xKBgDrOWtLZtZd7ddwutDPfw==",
+      "version": "1.24.4",
+      "resolved": "https://registry.npmjs.org/@salesforce/plugin-agent/-/plugin-agent-1.24.4.tgz",
+      "integrity": "sha512-DrZ3bBUyOOlrrHqN8YBJlVfBW0JVDPOt5N7Zzjux5z84K8EfoO0rVAoFCfPXlNtAQwI2WaXZWEVMDTigcv0h3g==",
       "license": "BSD-3-Clause",
       "dependencies": {
         "@inquirer/core": "^10.1.6",
@@ -5050,15 +5050,15 @@
       }
     },
     "node_modules/@salesforce/plugin-auth": {
-      "version": "3.7.19",
-      "resolved": "https://registry.npmjs.org/@salesforce/plugin-auth/-/plugin-auth-3.7.19.tgz",
-      "integrity": "sha512-dqXyi8SyygnAHGaHtucx8D0rNlC3IMMtLai98qh6E0XQFPCvZEiYjpYAQlO206CvVgjQ6HGtymWsT4a52eoyVA==",
+      "version": "3.8.1",
+      "resolved": "https://registry.npmjs.org/@salesforce/plugin-auth/-/plugin-auth-3.8.1.tgz",
+      "integrity": "sha512-ltovvzozwA8cw3f+2HgahZTRyy1K++ijfv1ekiKugkaRvwFvcUtbhDhtKmeew0m74npUKcahoRsafPNeNu81XQ==",
       "license": "Apache-2.0",
       "dependencies": {
         "@inquirer/checkbox": "^2.5.0",
         "@inquirer/select": "^2.5.0",
         "@oclif/core": "^4",
-        "@salesforce/core": "^8.18.7",
+        "@salesforce/core": "^8.20.0",
         "@salesforce/kit": "^3.2.3",
         "@salesforce/plugin-info": "^3.4.80",
         "@salesforce/sf-plugins-core": "^12.2.4",
@@ -5181,9 +5181,9 @@
       }
     },
     "node_modules/@salesforce/plugin-data": {
-      "version": "4.0.52",
-      "resolved": "https://registry.npmjs.org/@salesforce/plugin-data/-/plugin-data-4.0.52.tgz",
-      "integrity": "sha512-ClcTYXITqksDhqHXuLrNa4uAPM5tV9KF2MDHyNaRvz9VaxFk+JZnUXhfsb1D2akzRMgWaKEv4rCSqNMKQOmT+Q==",
+      "version": "4.0.53",
+      "resolved": "https://registry.npmjs.org/@salesforce/plugin-data/-/plugin-data-4.0.53.tgz",
+      "integrity": "sha512-fIOazIGnz5eh7kR/641ilPn/IFWGp6FyuQMq+p2CsTlU1OR2E+eXG23L53R/SOrdJvNvYKq0wr85hXivBpLhzg==",
       "license": "Apache-2.0",
       "dependencies": {
         "@jsforce/jsforce-node": "^3.9.4",
@@ -5578,9 +5578,9 @@
       }
     },
     "node_modules/@salesforce/plugin-telemetry": {
-      "version": "3.6.54",
-      "resolved": "https://registry.npmjs.org/@salesforce/plugin-telemetry/-/plugin-telemetry-3.6.54.tgz",
-      "integrity": "sha512-YNSshwHXpln2impiDLd7sfjBSl1NnADSYXiafJiPjr67Zb5lbl9Pc3uFSQCCWPcwA0Fk9X8tc4kpKsJc3wbPXA==",
+      "version": "3.6.55",
+      "resolved": "https://registry.npmjs.org/@salesforce/plugin-telemetry/-/plugin-telemetry-3.6.55.tgz",
+      "integrity": "sha512-n5mpUxtS8ti8AXsX8LNxYc4gPl5ljn9KVS72Hd8ZUAMk9W9Atw/foZu6D2hAICGBzC2qdEXlmPWPbMPzGyIO7Q==",
       "license": "Apache-2.0",
       "dependencies": {
         "@oclif/core": "^4.5.2",

package/oclif.lock

@@ -2068,10 +2068,10 @@
     strip-ansi "6.0.1"
     ts-retry-promise "^0.8.1"
 
-"@salesforce/core@^8.10.1", "@salesforce/core@^8.12.0", "@salesforce/core@^8.15.0", "@salesforce/core@^8.18.1", "@salesforce/core@^8.18.5", "@salesforce/core@^8.18.7", "@salesforce/core@^8.19.1", "@salesforce/core@^8.5.1", "@salesforce/core@^8.8.0", "@salesforce/core@^8.8.1", "@salesforce/core@^8.8.5", "@salesforce/core@^8.9.1":
-  version "8.19.1"
-  resolved "https://registry.npmjs.org/@salesforce/core/-/core-8.19.1.tgz"
-  integrity sha512-HPJxus0W4S1aoT4Qn6mG2s9Ik/mZ59rXNUFc2c+BgEAs28khbZOLR2uiZYexNpXIIZnCrSbb+v1t8IW/idIyCA==
+"@salesforce/core@^8.10.1", "@salesforce/core@^8.12.0", "@salesforce/core@^8.15.0", "@salesforce/core@^8.18.1", "@salesforce/core@^8.18.5", "@salesforce/core@^8.18.7", "@salesforce/core@^8.19.1", "@salesforce/core@^8.20.0", "@salesforce/core@^8.5.1", "@salesforce/core@^8.8.0", "@salesforce/core@^8.8.1", "@salesforce/core@^8.8.5", "@salesforce/core@^8.9.1":
+  version "8.20.0"
+  resolved "https://registry.npmjs.org/@salesforce/core/-/core-8.20.0.tgz"
+  integrity sha512-WZoab9aHDbYXUh4nO+91PNLHpiPfK408qjn3l6Sbgck2d0bzYkW5wOmuv5D5yWrEybs9kGosrW/e9liKPGmgng==
   dependencies:
     "@jsforce/jsforce-node" "^3.10.1"
     "@salesforce/kit" "^3.2.2"
@@ -2165,10 +2165,10 @@
     jszip "^3.10.1"
     object-treeify "^2"
 
-"@salesforce/plugin-agent@1.24.3":
-  version "1.24.3"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-agent/-/plugin-agent-1.24.3.tgz"
-  integrity sha512-ck2cOVvnaUuuukajUkBvxgAHy53lYbzCxMXr6m1L99ZRYO9l44tosvUfJMkBb4xKBgDrOWtLZtZd7ddwutDPfw==
+"@salesforce/plugin-agent@1.24.4":
+  version "1.24.4"
+  resolved "https://registry.npmjs.org/@salesforce/plugin-agent/-/plugin-agent-1.24.4.tgz"
+  integrity sha512-DrZ3bBUyOOlrrHqN8YBJlVfBW0JVDPOt5N7Zzjux5z84K8EfoO0rVAoFCfPXlNtAQwI2WaXZWEVMDTigcv0h3g==
   dependencies:
     "@inquirer/core" "^10.1.6"
     "@inquirer/prompts" "^7.2.0"
@@ -2214,15 +2214,15 @@
     got "^13.0.0"
     proxy-agent "^6.4.0"
 
-"@salesforce/plugin-auth@3.7.19":
-  version "3.7.19"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-auth/-/plugin-auth-3.7.19.tgz"
-  integrity sha512-dqXyi8SyygnAHGaHtucx8D0rNlC3IMMtLai98qh6E0XQFPCvZEiYjpYAQlO206CvVgjQ6HGtymWsT4a52eoyVA==
+"@salesforce/plugin-auth@3.8.1":
+  version "3.8.1"
+  resolved "https://registry.npmjs.org/@salesforce/plugin-auth/-/plugin-auth-3.8.1.tgz"
+  integrity sha512-ltovvzozwA8cw3f+2HgahZTRyy1K++ijfv1ekiKugkaRvwFvcUtbhDhtKmeew0m74npUKcahoRsafPNeNu81XQ==
   dependencies:
     "@inquirer/checkbox" "^2.5.0"
     "@inquirer/select" "^2.5.0"
     "@oclif/core" "^4"
-    "@salesforce/core" "^8.18.7"
+    "@salesforce/core" "^8.20.0"
     "@salesforce/kit" "^3.2.3"
     "@salesforce/plugin-info" "^3.4.80"
     "@salesforce/sf-plugins-core" "^12.2.4"
@@ -2243,10 +2243,10 @@
     debug "^4.4.0"
     handlebars "^4.7.8"
 
-"@salesforce/plugin-data@4.0.52":
-  version "4.0.52"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-data/-/plugin-data-4.0.52.tgz"
-  integrity sha512-ClcTYXITqksDhqHXuLrNa4uAPM5tV9KF2MDHyNaRvz9VaxFk+JZnUXhfsb1D2akzRMgWaKEv4rCSqNMKQOmT+Q==
+"@salesforce/plugin-data@4.0.53":
+  version "4.0.53"
+  resolved "https://registry.npmjs.org/@salesforce/plugin-data/-/plugin-data-4.0.53.tgz"
+  integrity sha512-fIOazIGnz5eh7kR/641ilPn/IFWGp6FyuQMq+p2CsTlU1OR2E+eXG23L53R/SOrdJvNvYKq0wr85hXivBpLhzg==
   dependencies:
     "@jsforce/jsforce-node" "^3.9.4"
     "@oclif/multi-stage-output" "^0.8.20"
@@ -2410,10 +2410,10 @@
     fast-xml-parser "^4.5.3"
     js2xmlparser "^4.0.2"
 
-"@salesforce/plugin-telemetry@3.6.54":
-  version "3.6.54"
-  resolved "https://registry.npmjs.org/@salesforce/plugin-telemetry/-/plugin-telemetry-3.6.54.tgz"
-  integrity sha512-YNSshwHXpln2impiDLd7sfjBSl1NnADSYXiafJiPjr67Zb5lbl9Pc3uFSQCCWPcwA0Fk9X8tc4kpKsJc3wbPXA==
+"@salesforce/plugin-telemetry@3.6.55":
+  version "3.6.55"
+  resolved "https://registry.npmjs.org/@salesforce/plugin-telemetry/-/plugin-telemetry-3.6.55.tgz"
+  integrity sha512-n5mpUxtS8ti8AXsX8LNxYc4gPl5ljn9KVS72Hd8ZUAMk9W9Atw/foZu6D2hAICGBzC2qdEXlmPWPbMPzGyIO7Q==
   dependencies:
     "@oclif/core" "^4.5.2"
     "@salesforce/core" "^8.15.0"

package/oclif.manifest.json

@@ -4158,5 +4158,5 @@
       "requiresProject": true
     }
   },
-  "version": "2.103.4"
+  "version": "2.103.6"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "2.103.4",
+  "version": "2.103.6",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run.js",
@@ -157,11 +157,11 @@
     "@oclif/plugin-which": "3.2.39",
     "@salesforce/core": "^8.9.1",
     "@salesforce/kit": "^3.1.6",
-    "@salesforce/plugin-agent": "1.24.3",
+    "@salesforce/plugin-agent": "1.24.4",
     "@salesforce/plugin-apex": "3.6.19",
     "@salesforce/plugin-api": "1.3.3",
-    "@salesforce/plugin-auth": "3.7.19",
-    "@salesforce/plugin-data": "4.0.52",
+    "@salesforce/plugin-auth": "3.8.1",
+    "@salesforce/plugin-data": "4.0.53",
     "@salesforce/plugin-deploy-retrieve": "3.22.41",
     "@salesforce/plugin-info": "3.4.81",
     "@salesforce/plugin-limits": "3.3.64",
@@ -171,7 +171,7 @@
     "@salesforce/plugin-schema": "3.3.78",
     "@salesforce/plugin-settings": "2.4.42",
     "@salesforce/plugin-sobject": "1.4.68",
-    "@salesforce/plugin-telemetry": "3.6.54",
+    "@salesforce/plugin-telemetry": "3.6.55",
     "@salesforce/plugin-templates": "56.3.60",
     "@salesforce/plugin-trust": "3.7.113",
     "@salesforce/plugin-user": "3.6.34",