From ecaf523820fff49f6ea46c70edb38f7a3392a573 Mon Sep 17 00:00:00 2001
From: svc-cli-bot <Svc_cli_bot@salesforce.com>
Date: Wed, 11 Feb 2026 03:11:50 +0000
Subject: [PATCH 1/2] chore(release): bump to 2.123.1

---
 README.md    | 2177 ++++++++++++++++++++++++++++----------------------
 package.json |   40 +-
 yarn.lock    |  323 ++++----
 3 files changed, 1419 insertions(+), 1121 deletions(-)

diff --git a/README.md b/README.md
index 45f50fbd..b8f211ec 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (--version|-v)
-@salesforce/cli/2.123.0 linux-x64 node-v22.22.0
+@salesforce/cli/2.123.1 linux-x64 node-v22.22.0
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND
@@ -50,6 +50,10 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 - [`sf agent generate template`](#sf-agent-generate-template)
 - [`sf agent generate test-spec`](#sf-agent-generate-test-spec)
 - [`sf agent preview`](#sf-agent-preview)
+- [`sf agent preview end`](#sf-agent-preview-end)
+- [`sf agent preview send`](#sf-agent-preview-send)
+- [`sf agent preview sessions`](#sf-agent-preview-sessions)
+- [`sf agent preview start`](#sf-agent-preview-start)
 - [`sf agent publish authoring-bundle`](#sf-agent-publish-authoring-bundle)
 - [`sf agent test create`](#sf-agent-test-create)
 - [`sf agent test list`](#sf-agent-test-list)
@@ -60,9 +64,6 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 - [`sf alias list`](#sf-alias-list)
 - [`sf alias set`](#sf-alias-set)
 - [`sf alias unset`](#sf-alias-unset)
-- [`sf analytics generate template`](#sf-analytics-generate-template)
-- [`sf apex generate class`](#sf-apex-generate-class)
-- [`sf apex generate trigger`](#sf-apex-generate-trigger)
 - [`sf apex get log`](#sf-apex-get-log)
 - [`sf apex get test`](#sf-apex-get-test)
 - [`sf apex list log`](#sf-apex-list-log)
@@ -104,11 +105,6 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 - [`sf force data bulk upsert`](#sf-force-data-bulk-upsert)
 - [`sf help [COMMAND]`](#sf-help-command)
 - [`sf info releasenotes display`](#sf-info-releasenotes-display)
-- [`sf lightning generate app`](#sf-lightning-generate-app)
-- [`sf lightning generate component`](#sf-lightning-generate-component)
-- [`sf lightning generate event`](#sf-lightning-generate-event)
-- [`sf lightning generate interface`](#sf-lightning-generate-interface)
-- [`sf lightning generate test`](#sf-lightning-generate-test)
 - [`sf logic get test`](#sf-logic-get-test)
 - [`sf logic run test`](#sf-logic-run-test)
 - [`sf org assign permset`](#sf-org-assign-permset)
@@ -191,7 +187,6 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 - [`sf project deploy resume`](#sf-project-deploy-resume)
 - [`sf project deploy start`](#sf-project-deploy-start)
 - [`sf project deploy validate`](#sf-project-deploy-validate)
-- [`sf project generate`](#sf-project-generate)
 - [`sf project generate manifest`](#sf-project-generate-manifest)
 - [`sf project list ignored`](#sf-project-list-ignored)
 - [`sf project reset tracking`](#sf-project-reset-tracking)
@@ -204,11 +199,21 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 - [`sf search`](#sf-search)
 - [`sf sobject describe`](#sf-sobject-describe)
 - [`sf sobject list`](#sf-sobject-list)
-- [`sf static-resource generate`](#sf-static-resource-generate)
+- [`sf template generate analytics template`](#sf-template-generate-analytics-template)
+- [`sf template generate apex class`](#sf-template-generate-apex-class)
+- [`sf template generate apex trigger`](#sf-template-generate-apex-trigger)
+- [`sf template generate digital-experience site`](#sf-template-generate-digital-experience-site)
+- [`sf template generate lightning app`](#sf-template-generate-lightning-app)
+- [`sf template generate lightning component`](#sf-template-generate-lightning-component)
+- [`sf template generate lightning event`](#sf-template-generate-lightning-event)
+- [`sf template generate lightning interface`](#sf-template-generate-lightning-interface)
+- [`sf template generate lightning test`](#sf-template-generate-lightning-test)
+- [`sf template generate project`](#sf-template-generate-project)
+- [`sf template generate static-resource`](#sf-template-generate-static-resource)
+- [`sf template generate visualforce component`](#sf-template-generate-visualforce-component)
+- [`sf template generate visualforce page`](#sf-template-generate-visualforce-page)
 - [`sf update [CHANNEL]`](#sf-update-channel)
 - [`sf version`](#sf-version)
-- [`sf visualforce generate component`](#sf-visualforce-generate-component)
-- [`sf visualforce generate page`](#sf-visualforce-generate-page)
 - [`sf which`](#sf-which)
 
 ## `sf agent activate`
@@ -248,7 +253,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.27.5/src/commands/agent/activate.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/activate.ts)_
 
 ## `sf agent create`
 
@@ -315,7 +320,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.27.5/src/commands/agent/create.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/create.ts)_
 
 ## `sf agent deactivate`
 
@@ -355,7 +360,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.27.5/src/commands/agent/deactivate.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/deactivate.ts)_
 
 ## `sf agent generate agent-spec`
 
@@ -462,7 +467,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.27.5/src/commands/agent/generate/agent-spec.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/generate/agent-spec.ts)_
 
 ## `sf agent generate authoring-bundle`
 
@@ -537,7 +542,7 @@ EXAMPLES
       other-package-dir/main/default --target-org my-dev-org
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.27.5/src/commands/agent/generate/authoring-bundle.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/generate/authoring-bundle.ts)_
 
 ## `sf agent generate template`
 
@@ -585,7 +590,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.27.5/src/commands/agent/generate/template.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/generate/template.ts)_
 
 ## `sf agent generate test-spec`
 
@@ -646,7 +651,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.27.5/src/commands/agent/generate/test-spec.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/generate/test-spec.ts)_
 
 ## `sf agent preview`
 
@@ -659,7 +664,7 @@ USAGE
 
 FLAGS
   -d, --output-dir=<value>        Directory where conversation transcripts are saved.
-  -n, --api-name=<value>          API name of the published and active agent you want to interact with.
+  -n, --api-name=<value>          API name of the activated published agent you want to interact with.
   -o, --target-org=<value>        (required) Username or alias of the target org. Not required if the `target-org`
                                   configuration variable is already set.
   -x, --apex-debug                Enable Apex debug logging during the agent preview conversation.
@@ -719,7 +724,210 @@ EXAMPLES
     $ sf agent preview --use-live-actions --apex-debug --output-dir transcripts/my-preview
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.27.5/src/commands/agent/preview.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/preview.ts)_
+
+## `sf agent preview end`
+
+End an existing programmatic agent preview session and get trace location.
+
+```
+USAGE
+  $ sf agent preview end -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [--session-id <value>] [-n
+    <value>] [--authoring-bundle <value>]
+
+FLAGS
+  -n, --api-name=<value>          API name of the activated published agent you want to preview.
+  -o, --target-org=<value>        (required) Username or alias of the target org. Not required if the `target-org`
+                                  configuration variable is already set.
+      --api-version=<value>       Override the api version used for api requests made by this command
+      --authoring-bundle=<value>  API name of the authoring bundle metadata component that contains the agent's Agent
+                                  Script file.
+      --session-id=<value>        Session ID outputted by "agent preview start". Not required when the agent has exactly
+                                  one active session. Run "agent preview sessions" to see the list of all sessions.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  End an existing programmatic agent preview session and get trace location.
+
+  You must have previously started a programmatic agent preview session with the "agent preview start" command to then
+  use this command to end it. This command also displays the local directory where the session trace files are stored.
+
+  The original "agent preview start" command outputs a session ID which you then use with the --session-id flag of this
+  command to end the session.  You don't have to specify the --session-id flag if an agent has only one active preview
+  session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring
+  bundle or the published agent, respecitvely.  To find either API name, navigate to your package directory in your DX
+  project. The API name of an authoring bundle is the same as its directory name under the "aiAuthoringBundles" metadata
+  directory.  Similarly, the published agent's API name is the same as its directory name under the "Bots" metadata
+  directory.
+
+EXAMPLES
+  End a preview session of a published agent by specifying its session ID and API name ; use the default org:
+
+    $ sf agent preview end --session-id <SESSION_ID> --api-name My_Published_Agent
+
+  Similar to previous example, but don't specify a session ID; you get an error if the published agent has more than
+  one active session. Use the org with alias "my-dev-org":
+
+    $ sf agent preview end --api-name My_Published_Agent --target-org my-dev-org
+
+  End a preview session of an agent using its authoring bundle API name; you get an error if the agent has more than
+  one active session.
+
+    $ sf agent preview end --authoring-bundle My_Local_Agent
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/preview/end.ts)_
+
+## `sf agent preview send`
+
+Send a message to an existing agent preview session.
+
+```
+USAGE
+  $ sf agent preview send -o <value> -u <value> [--json] [--flags-dir <value>] [--api-version <value>] [--session-id
+    <value>] [-n <value>] [--authoring-bundle <value>]
+
+FLAGS
+  -n, --api-name=<value>          API name of the activated published agent you want to preview.
+  -o, --target-org=<value>        (required) Username or alias of the target org. Not required if the `target-org`
+                                  configuration variable is already set.
+  -u, --utterance=<value>         (required) Utterance to send to the agent, enclosed in double quotes.
+      --api-version=<value>       Override the api version used for api requests made by this command
+      --authoring-bundle=<value>  API name of the authoring bundle metadata component that contains the agent's Agent
+                                  Script file.
+      --session-id=<value>        Session ID outputted by "agent preview start". Not required when the agent has exactly
+                                  one active session. Run "agent preview sessions" to see list of all sessions.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Send a message to an existing agent preview session.
+
+  You must have previously started a programmatic agent preview session with the "agent preview start" command to then
+  use this command to send the agent a message (utterance). This command then displays the agent's response.
+
+  The original "agent preview start" command outputs a session ID which you then use with the --session-id flag of this
+  command to send a message.  You don't have to specify the --session-id flag if an agent has only one active preview
+  session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring
+  bundle or the published agent, respecitvely.  To find either API name, navigate to your package directory in your DX
+  project. The API name of an authoring bundle is the same as its directory name under the "aiAuthoringBundles" metadata
+  directory.  Similarly, the published agent's API name is the same as its directory name under the "Bots" metadata
+  directory.
+
+EXAMPLES
+  Send a message to an activated published agent using its API name and session ID; use the default org:
+
+    $ sf agent preview send --utterance "What can you help me with?" --api-name My_Published_Agent --session-id \
+      <SESSION_ID>
+
+  Similar to previous example, but don't specify a session ID; you get an error if the agent has more than one active
+  session. Use the org with alias "my-dev-org":
+
+    $ sf agent preview send --utterance "What can you help me with?" --api-name My_Published_Agent --target-org \
+      my-dev-org
+
+  Send a message to an agent using its authoring bundle API name; you get an error if the agent has more than one
+  active session:
+
+    $ sf agent preview send --utterance "what can you help me with?" --authoring-bundle My_Local_Agent
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/preview/send.ts)_
+
+## `sf agent preview sessions`
+
+List all known programmatic agent preview sessions.
+
+```
+USAGE
+  $ sf agent preview sessions [--json] [--flags-dir <value>]
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  List all known programmatic agent preview sessions.
+
+  This command lists the agent preview sessions that were started with the "agent preview start" command and are still
+  in the local cache. Use this command to discover specific session IDs that you can pass to the "agent preview send" or
+  "agent preview end" commands with the --session-id flag.
+
+  Programmatic agent preview sessions can be started for both published activated agents and by using an agent's local
+  authoring bundle, which contains its Agent Script file.  In this command's output table, the Agent column contains
+  either the API name of the authoring bundle or the published agent, whichever was used when starting the session. In
+  the table, if the same API name has multiple rows with different session IDs, then it means that you previously
+  started multiple preview sessions with the associated agent.
+
+EXAMPLES
+  List all cached agent preview sessions:
+
+    $ sf agent preview sessions
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/preview/sessions.ts)_
+
+## `sf agent preview start`
+
+Start a programmatic agent preview session.
+
+```
+USAGE
+  $ sf agent preview start -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-n <value>]
+    [--authoring-bundle <value>] [--use-live-actions]
+
+FLAGS
+  -n, --api-name=<value>          API name of the activated published agent you want to preview.
+  -o, --target-org=<value>        (required) Username or alias of the target org. Not required if the `target-org`
+                                  configuration variable is already set.
+      --api-version=<value>       Override the api version used for api requests made by this command
+      --authoring-bundle=<value>  API name of the authoring bundle metadata component that contains the agent's Agent
+                                  Script file.
+      --use-live-actions          Use real actions in the org; if not specified, preview uses AI to simulate (mock)
+                                  actions.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Start a programmatic agent preview session.
+
+  This command outputs a session ID that you then use with the "agent preview send" command to send an utterance to the
+  agent.  Use the "agent preview sessions" command to list all active sessions and the "agent preview end" command to
+  end a specific session.
+
+  Identify the agent you want to start previewing with either the --authoring-bundle flag to specify a local authoring
+  bundle's API name or --api-name to specify an activated published agent's API name.  To find either API name, navigate
+  to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name
+  under the "aiAuthoringBundles" metadata directory.  Similarly, the published agent's API name is the same as its
+  directory name under the "Bots" metadata directory.
+
+  When starting a preview session using the authoring bundle, which contains the agent's Agent Script file, the preview
+  uses mocked actions by default.  Specify --use-live-actions for live mode, which uses the real Apex classes, flows,
+  etc, in the org for the actions.
+
+EXAMPLES
+  Start a programmatic agent preview session by specifying an authoring bundle; uses mocked actions by default. Use
+  the org with alias "my-dev-org":
+
+    $ sf agent preview start --authoring-bundle My_Agent_Bundle --target-org my-dev-org
+
+  Similar to previous example but use live actions and the default org:
+
+    $ sf agent preview start --authoring-bundle My_Agent_Bundle --use-live-actions
+
+  Start a preview session with an activated published agent:
+
+    $ sf agent preview start --api-name My_Published_Agent
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/preview/start.ts)_
 
 ## `sf agent publish authoring-bundle`
 
@@ -768,7 +976,7 @@ EXAMPLES
     $ sf agent publish authoring-bundle --api-name MyAuthoringbundle --target-org my-dev-org
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.27.5/src/commands/agent/publish/authoring-bundle.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/publish/authoring-bundle.ts)_
 
 ## `sf agent test create`
 
@@ -823,7 +1031,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.27.5/src/commands/agent/test/create.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/test/create.ts)_
 
 ## `sf agent test list`
 
@@ -858,7 +1066,7 @@ EXAMPLES
     $ sf agent test list --target-org my-org
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.27.5/src/commands/agent/test/list.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/test/list.ts)_
 
 ## `sf agent test results`
 
@@ -924,7 +1132,7 @@ FLAG DESCRIPTIONS
     expression when using custom evaluations.
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.27.5/src/commands/agent/test/results.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/test/results.ts)_
 
 ## `sf agent test resume`
 
@@ -997,7 +1205,7 @@ FLAG DESCRIPTIONS
     expression when using custom evaluations.
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.27.5/src/commands/agent/test/resume.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/test/resume.ts)_
 
 ## `sf agent test run`
 
@@ -1071,7 +1279,7 @@ FLAG DESCRIPTIONS
     expression when using custom evaluations.
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.27.5/src/commands/agent/test/run.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/test/run.ts)_
 
 ## `sf agent validate authoring-bundle`
 
@@ -1118,7 +1326,7 @@ EXAMPLES
     $ sf agent validate authoring-bundle --api-name MyAuthoringBundle --target-org my-dev-org
 ```
 
-_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.27.5/src/commands/agent/validate/authoring-bundle.ts)_
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.29.0/src/commands/agent/validate/authoring-bundle.ts)_
 
 ## `sf alias list`
 
@@ -1146,7 +1354,7 @@ EXAMPLES
     $ sf alias list
 ```
 
-_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.54/src/commands/alias/list.ts)_
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.55/src/commands/alias/list.ts)_
 
 ## `sf alias set`
 
@@ -1195,7 +1403,7 @@ EXAMPLES
     $ sf alias set my-scratch-org test-ss0xut7txzxf@example.com
 ```
 
-_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.54/src/commands/alias/set.ts)_
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.55/src/commands/alias/set.ts)_
 
 ## `sf alias unset`
 
@@ -1235,19 +1443,23 @@ EXAMPLES
     $ sf alias unset --all [--no-prompt]
 ```
 
-_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.54/src/commands/alias/unset.ts)_
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.55/src/commands/alias/unset.ts)_
 
-## `sf analytics generate template`
+## `sf apex get log`
 
-Generate a simple Analytics template.
+Fetch the specified log or given number of most recent logs from the org.
 
 ```
 USAGE
-  $ sf analytics generate template -n <value> [--json] [--flags-dir <value>] [-d <value>] [--api-version <value>]
+  $ sf apex get log -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-i <value>] [-n <value>]
+    [-d <value>]
 
 FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -n, --name=<value>         (required) Name of the Analytics template.
+  -d, --output-dir=<value>   Directory for saving the log files.
+  -i, --log-id=<value>       ID of the specific log to display.
+  -n, --number=<value>       Number of the most recent logs to display.
+  -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
+                             configuration variable is already set.
       --api-version=<value>  Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
@@ -1255,108 +1467,111 @@ GLOBAL FLAGS
   --json               Format output as json.
 
 DESCRIPTION
-  Generate a simple Analytics template.
+  Fetch the specified log or given number of most recent logs from the org.
 
-  The metadata files associated with the Analytics template must be contained in a parent directory called
-  "waveTemplates" in your package directory. Either run this command from an existing directory of this name, or use the
-  --output-dir flag to generate one or point to an existing one.
+  To get the IDs for your debug logs, run "sf apex log list". Executing this command without flags returns the most
+  recent log.
 
 ALIASES
-  $ sf force analytics template create
+  $ sf force apex log get
 
 EXAMPLES
-  Generate the metadata files for a simple Analytics template file called myTemplate in the
-  force-app/main/default/waveTemplates directory:
+  Fetch the log in your default org using an ID:
+
+    $ sf apex get log --log-id <log id>
+
+  Fetch the log in the org with the specified username using an ID:
+
+    $ sf apex get log --log-id <log id> --target-org me@my.org
+
+  Fetch the two most recent logs in your default org:
+
+    $ sf apex get log --number 2
 
-    $ sf analytics generate template --name myTemplate --output-dir force-app/main/default/waveTemplates
+  Similar to previous example, but save the two log files in the specified directory:
+
+    $ sf apex get log --output-dir /Users/sfdxUser/logs --number 2
 
 FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
+  -d, --output-dir=<value>  Directory for saving the log files.
 
     The location can be an absolute path or relative to the current working directory. The default is the current
     directory.
 ```
 
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/analytics/generate/template.ts)_
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.6/src/commands/apex/get/log.ts)_
 
-## `sf apex generate class`
+## `sf apex get test`
 
-Generate an Apex class.
+Display test results for a specific asynchronous test run.
 
 ```
 USAGE
-  $ sf apex generate class -n <value> [--json] [--flags-dir <value>] [-t
-    ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService] [-d <value>] [--api-version <value>]
+  $ sf apex get test -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>]
+    [--detailed-coverage -c] [-d <value>] [-r human|tap|junit|json] [--concise]
 
 FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -n, --name=<value>         (required) Name of the generated Apex class.
-  -t, --template=<option>    [default: DefaultApexClass] Template to use for file creation.
-                             <options: ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService>
-      --api-version=<value>  Override the api version used for api requests made by this command
+  -c, --code-coverage           Retrieve code coverage results.
+  -d, --output-dir=<value>      Directory in which to store test result files.
+  -i, --test-run-id=<value>     (required) ID of the test run.
+  -o, --target-org=<value>      (required) Username or alias of the target org. Not required if the `target-org`
+                                configuration variable is already set.
+  -r, --result-format=<option>  [default: human] Format of the test results.
+                                <options: human|tap|junit|json>
+      --api-version=<value>     Override the api version used for api requests made by this command
+      --concise                 Display only failed test results; works with human-readable output only.
+      --detailed-coverage       Display detailed code coverage per test.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
   --json               Format output as json.
 
 DESCRIPTION
-  Generate an Apex class.
+  Display test results for a specific asynchronous test run.
 
-  Generates the Apex *.cls file and associated metadata file. These files must be contained in a parent directory called
-  "classes" in your package directory. Either run this command from an existing directory of this name, or use the
-  --output-dir flag to generate one or point to an existing one.
+  Provide a test run ID to display test results for an enqueued or completed asynchronous test run. The test run ID is
+  displayed after running the "sf apex test run" command.
+
+  To see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level
+  summary of the test run and the code coverage values for classes in your org. If you specify human-readable result
+  format, use the --detailed-coverage flag to see detailed coverage results for each test method run.
 
 ALIASES
-  $ sf force apex class create
+  $ sf force apex test report
 
 EXAMPLES
-  Generate two metadata files associated with the MyClass Apex class (MyClass.cls and MyClass.cls-meta.xml) in the
-  current directory:
-
-    $ sf apex generate class --name MyClass
-
-  Similar to previous example, but generates the files in the "force-app/main/default/classes" directory:
-
-    $ sf apex generate class --name MyClass --output-dir force-app/main/default/classes
+  Display test results for your default org using a test run ID:
 
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
+    $ sf apex get test --test-run-id <test run id>
 
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
+  Similar to previous example, but output the result in JUnit format:
 
-  -n, --name=<value>  Name of the generated Apex class.
+    $ sf apex get test --test-run-id <test run id> --result-format junit
 
-    The name can be up to 40 characters and must start with a letter.
+  Also retrieve code coverage results and output in JSON format:
 
-  -t, --template=ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService
+    $ sf apex get test --test-run-id <test run id> --code-coverage --json
 
-    Template to use for file creation.
+  Specify a directory in which to save the test results from the org with the specified username (rather than your
+  default org):
 
-    Supplied parameter values or default values are filled into a copy of the template.
+    $ sf apex get test --test-run-id <test run id> --code-coverage --output-dir <path to outputdir> --target-org \
+      me@myorg'
 ```
 
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/apex/generate/class.ts)_
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.6/src/commands/apex/get/test.ts)_
 
-## `sf apex generate trigger`
+## `sf apex list log`
 
-Generate an Apex trigger.
+Display a list of IDs and general information about debug logs.
 
 ```
 USAGE
-  $ sf apex generate trigger -n <value> [--json] [--flags-dir <value>] [-t ApexTrigger] [-d <value>] [--api-version
-    <value>] [-s <value>] [-e before insert|before update|before delete|after insert|after update|after delete|after
-    undelete...]
+  $ sf apex list log -o <value> [--json] [--flags-dir <value>] [--api-version <value>]
 
 FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -e, --event=<option>...    [default: before insert] Events that fire the trigger.
-                             <options: before insert|before update|before delete|after insert|after update|after
-                             delete|after undelete>
-  -n, --name=<value>         (required) Name of the generated Apex trigger
-  -s, --sobject=<value>      [default: SOBJECT] Salesforce object to generate a trigger on.
-  -t, --template=<option>    [default: ApexTrigger] Template to use for file creation.
-                             <options: ApexTrigger>
+  -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
+                             configuration variable is already set.
       --api-version=<value>  Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
@@ -1364,212 +1579,35 @@ GLOBAL FLAGS
   --json               Format output as json.
 
 DESCRIPTION
-  Generate an Apex trigger.
+  Display a list of IDs and general information about debug logs.
 
-  Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent
-  directory called "triggers" in your package directory. Either run this command from an existing directory of this
-  name, or use the --output-dir flag to generate one or point to an existing one.
+  Run this command in a project to list the IDs and general information for all debug logs in your default org.
 
-  If you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with
-  the Salesforce object you want to generate a trigger for. If you don't specify --event, "before insert" is used.
+  To fetch a specific log from your org, obtain the ID from this command's output, then run the “sf apex log get”
+  command.
 
 ALIASES
-  $ sf force apex trigger create
+  $ sf force apex log list
 
 EXAMPLES
-  Generate two files associated with the MyTrigger Apex trigger (MyTrigger.trigger and MyTrigger.trigger-meta.xml) in
-  the current directory:
-
-    $ sf apex generate trigger --name MyTrigger
+  List the IDs and information about the debug logs in your default org:
 
-  Similar to the previous example, but generate the files in the "force-app/main/default/triggers" directory:
+    $ sf apex list log
 
-    $ sf apex generate trigger --name MyTrigger --output-dir force-app/main/default/triggers
+  Similar to previous example, but use the org with the specified username:
 
-  Generate files for a trigger that fires on the Account object before and after an insert:
+    $ sf apex list log --target-org me@my.org
+```
 
-    $ sf apex generate trigger --name MyTrigger --sobject Account --event "before insert,after insert"
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.6/src/commands/apex/list/log.ts)_
 
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
+## `sf apex run`
 
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
+Execute anonymous Apex code entered on the command line or from a local file.
 
-  -n, --name=<value>  Name of the generated Apex trigger
-
-    The name can be up to 40 characters and must start with a letter.
-
-  -t, --template=ApexTrigger  Template to use for file creation.
-
-    Supplied parameter values or default values are filled into a copy of the template.
-```
-
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/apex/generate/trigger.ts)_
-
-## `sf apex get log`
-
-Fetch the specified log or given number of most recent logs from the org.
-
-```
-USAGE
-  $ sf apex get log -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-i <value>] [-n <value>]
-    [-d <value>]
-
-FLAGS
-  -d, --output-dir=<value>   Directory for saving the log files.
-  -i, --log-id=<value>       ID of the specific log to display.
-  -n, --number=<value>       Number of the most recent logs to display.
-  -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
-                             configuration variable is already set.
-      --api-version=<value>  Override the api version used for api requests made by this command
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Fetch the specified log or given number of most recent logs from the org.
-
-  To get the IDs for your debug logs, run "sf apex log list". Executing this command without flags returns the most
-  recent log.
-
-ALIASES
-  $ sf force apex log get
-
-EXAMPLES
-  Fetch the log in your default org using an ID:
-
-    $ sf apex get log --log-id <log id>
-
-  Fetch the log in the org with the specified username using an ID:
-
-    $ sf apex get log --log-id <log id> --target-org me@my.org
-
-  Fetch the two most recent logs in your default org:
-
-    $ sf apex get log --number 2
-
-  Similar to previous example, but save the two log files in the specified directory:
-
-    $ sf apex get log --output-dir /Users/sfdxUser/logs --number 2
-
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the log files.
-
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
-```
-
-_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.5/src/commands/apex/get/log.ts)_
-
-## `sf apex get test`
-
-Display test results for a specific asynchronous test run.
-
-```
-USAGE
-  $ sf apex get test -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>]
-    [--detailed-coverage -c] [-d <value>] [-r human|tap|junit|json] [--concise]
-
-FLAGS
-  -c, --code-coverage           Retrieve code coverage results.
-  -d, --output-dir=<value>      Directory in which to store test result files.
-  -i, --test-run-id=<value>     (required) ID of the test run.
-  -o, --target-org=<value>      (required) Username or alias of the target org. Not required if the `target-org`
-                                configuration variable is already set.
-  -r, --result-format=<option>  [default: human] Format of the test results.
-                                <options: human|tap|junit|json>
-      --api-version=<value>     Override the api version used for api requests made by this command
-      --concise                 Display only failed test results; works with human-readable output only.
-      --detailed-coverage       Display detailed code coverage per test.
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Display test results for a specific asynchronous test run.
-
-  Provide a test run ID to display test results for an enqueued or completed asynchronous test run. The test run ID is
-  displayed after running the "sf apex test run" command.
-
-  To see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level
-  summary of the test run and the code coverage values for classes in your org. If you specify human-readable result
-  format, use the --detailed-coverage flag to see detailed coverage results for each test method run.
-
-ALIASES
-  $ sf force apex test report
-
-EXAMPLES
-  Display test results for your default org using a test run ID:
-
-    $ sf apex get test --test-run-id <test run id>
-
-  Similar to previous example, but output the result in JUnit format:
-
-    $ sf apex get test --test-run-id <test run id> --result-format junit
-
-  Also retrieve code coverage results and output in JSON format:
-
-    $ sf apex get test --test-run-id <test run id> --code-coverage --json
-
-  Specify a directory in which to save the test results from the org with the specified username (rather than your
-  default org):
-
-    $ sf apex get test --test-run-id <test run id> --code-coverage --output-dir <path to outputdir> --target-org \
-      me@myorg'
-```
-
-_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.5/src/commands/apex/get/test.ts)_
-
-## `sf apex list log`
-
-Display a list of IDs and general information about debug logs.
-
-```
-USAGE
-  $ sf apex list log -o <value> [--json] [--flags-dir <value>] [--api-version <value>]
-
-FLAGS
-  -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
-                             configuration variable is already set.
-      --api-version=<value>  Override the api version used for api requests made by this command
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Display a list of IDs and general information about debug logs.
-
-  Run this command in a project to list the IDs and general information for all debug logs in your default org.
-
-  To fetch a specific log from your org, obtain the ID from this command's output, then run the “sf apex log get”
-  command.
-
-ALIASES
-  $ sf force apex log list
-
-EXAMPLES
-  List the IDs and information about the debug logs in your default org:
-
-    $ sf apex list log
-
-  Similar to previous example, but use the org with the specified username:
-
-    $ sf apex list log --target-org me@my.org
-```
-
-_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.5/src/commands/apex/list/log.ts)_
-
-## `sf apex run`
-
-Execute anonymous Apex code entered on the command line or from a local file.
-
-```
-USAGE
-  $ sf apex run -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-f <value>]
+```
+USAGE
+  $ sf apex run -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-f <value>]
 
 FLAGS
   -f, --file=<value>         Path to a local file that contains Apex code.
@@ -1608,7 +1646,7 @@ EXAMPLES
     $ sf apex run
 ```
 
-_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.5/src/commands/apex/run.ts)_
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.6/src/commands/apex/run.ts)_
 
 ## `sf apex run test`
 
@@ -1755,7 +1793,7 @@ FLAG DESCRIPTIONS
     --tests Test1 --tests Test2
 ```
 
-_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.5/src/commands/apex/run/test.ts)_
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.6/src/commands/apex/run/test.ts)_
 
 ## `sf apex tail log`
 
@@ -1798,7 +1836,7 @@ EXAMPLES
     $ sf apex tail log --color --skip-trace-flag
 ```
 
-_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.5/src/commands/apex/tail/log.ts)_
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.6/src/commands/apex/tail/log.ts)_
 
 ## `sf api request graphql`
 
@@ -1851,7 +1889,7 @@ EXAMPLES
     $ sf api request graphql --body example.txt --stream-to-file output.txt --include
 ```
 
-_See code: [@salesforce/plugin-api](https://github.com/salesforcecli/plugin-api/blob/1.3.8/src/commands/api/request/graphql.ts)_
+_See code: [@salesforce/plugin-api](https://github.com/salesforcecli/plugin-api/blob/1.3.9/src/commands/api/request/graphql.ts)_
 
 ## `sf api request rest [URL]`
 
@@ -1960,7 +1998,7 @@ FLAG DESCRIPTIONS
     https://github.com/salesforcecli/plugin-api/tree/main/test/test-files/data-project.
 ```
 
-_See code: [@salesforce/plugin-api](https://github.com/salesforcecli/plugin-api/blob/1.3.8/src/commands/api/request/rest.ts)_
+_See code: [@salesforce/plugin-api](https://github.com/salesforcecli/plugin-api/blob/1.3.9/src/commands/api/request/rest.ts)_
 
 ## `sf autocomplete [SHELL]`
 
@@ -2069,7 +2107,7 @@ CONFIGURATION VARIABLES
   org-capitalize-record-types    Whether record types are capitalized on scratch org creation.
 ```
 
-_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.54/src/commands/config/get.ts)_
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.55/src/commands/config/get.ts)_
 
 ## `sf config list`
 
@@ -2109,7 +2147,7 @@ EXAMPLES
     $ sf config list
 ```
 
-_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.54/src/commands/config/list.ts)_
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.55/src/commands/config/list.ts)_
 
 ## `sf config set`
 
@@ -2178,7 +2216,7 @@ CONFIGURATION VARIABLES
   org-capitalize-record-types    Whether record types are capitalized on scratch org creation.
 ```
 
-_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.54/src/commands/config/set.ts)_
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.55/src/commands/config/set.ts)_
 
 ## `sf config unset`
 
@@ -2228,7 +2266,7 @@ CONFIGURATION VARIABLES
   org-capitalize-record-types    Whether record types are capitalized on scratch org creation.
 ```
 
-_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.54/src/commands/config/unset.ts)_
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/2.4.55/src/commands/config/unset.ts)_
 
 ## `sf data bulk results`
 
@@ -2273,7 +2311,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.67/src/commands/data/bulk/results.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/bulk/results.ts)_
 
 ## `sf data create file`
 
@@ -2322,7 +2360,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.67/src/commands/data/create/file.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/create/file.ts)_
 
 ## `sf data create record`
 
@@ -2378,7 +2416,7 @@ EXAMPLES
       TracedEntityId=01p17000000R6bLAAS"
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/data/create/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/create/record.ts)_
 
 ## `sf data delete bulk`
 
@@ -2437,7 +2475,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.67/src/commands/data/delete/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/delete/bulk.ts)_
 
 ## `sf data delete record`
 
@@ -2498,7 +2536,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.67/src/commands/data/delete/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/delete/record.ts)_
 
 ## `sf data delete resume`
 
@@ -2537,7 +2575,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.67/src/commands/data/delete/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/delete/resume.ts)_
 
 ## `sf data export bulk`
 
@@ -2604,7 +2642,7 @@ EXAMPLES
       --result-format json --wait 10 --all-rows
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/data/export/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/export/bulk.ts)_
 
 ## `sf data export resume`
 
@@ -2643,7 +2681,7 @@ EXAMPLES
     $ sf data export resume --use-most-recent
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/data/export/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/export/resume.ts)_
 
 ## `sf data export tree`
 
@@ -2703,7 +2741,7 @@ EXAMPLES
       my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/data/export/tree.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/export/tree.ts)_
 
 ## `sf data get record`
 
@@ -2767,7 +2805,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.67/src/commands/data/get/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/get/record.ts)_
 
 ## `sf data import bulk`
 
@@ -2819,7 +2857,7 @@ EXAMPLES
     $ sf data import bulk --file accounts.csv --sobject Account --wait 10 --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/data/import/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/import/bulk.ts)_
 
 ## `sf data import resume`
 
@@ -2855,7 +2893,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.67/src/commands/data/import/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/import/resume.ts)_
 
 ## `sf data import tree`
 
@@ -2919,7 +2957,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.67/src/commands/data/import/tree.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/import/tree.ts)_
 
 ## `sf data query`
 
@@ -2972,7 +3010,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.67/src/commands/data/query.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/query.ts)_
 
 ## `sf data resume`
 
@@ -3009,7 +3047,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.67/src/commands/data/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/resume.ts)_
 
 ## `sf data search`
 
@@ -3059,7 +3097,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.67/src/commands/data/search.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/search.ts)_
 
 ## `sf data update bulk`
 
@@ -3114,7 +3152,7 @@ EXAMPLES
     $ sf data update bulk --file accounts.csv --sobject Account --wait 10 --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/data/update/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/update/bulk.ts)_
 
 ## `sf data update record`
 
@@ -3176,7 +3214,7 @@ EXAMPLES
       "ExpirationDate=2017-12-01T00:58:04.000+0000"
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/data/update/record.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/update/record.ts)_
 
 ## `sf data update resume`
 
@@ -3215,7 +3253,7 @@ EXAMPLES
     $ sf data update resume --use-most-recent
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/data/update/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/update/resume.ts)_
 
 ## `sf data upsert bulk`
 
@@ -3271,7 +3309,7 @@ EXAMPLES
       my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/data/upsert/bulk.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/upsert/bulk.ts)_
 
 ## `sf data upsert resume`
 
@@ -3310,7 +3348,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.67/src/commands/data/upsert/resume.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/data/upsert/resume.ts)_
 
 ## `sf doctor`
 
@@ -3358,7 +3396,7 @@ EXAMPLES
     $ sf doctor --plugin @salesforce/plugin-source
 ```
 
-_See code: [@salesforce/plugin-info](https://github.com/salesforcecli/plugin-info/blob/3.4.100/src/commands/doctor.ts)_
+_See code: [@salesforce/plugin-info](https://github.com/salesforcecli/plugin-info/blob/3.4.101/src/commands/doctor.ts)_
 
 ## `sf force data bulk delete`
 
@@ -3405,7 +3443,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.67/src/commands/force/data/bulk/delete.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/force/data/bulk/delete.ts)_
 
 ## `sf force data bulk status`
 
@@ -3442,7 +3480,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.67/src/commands/force/data/bulk/status.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/force/data/bulk/status.ts)_
 
 ## `sf force data bulk upsert`
 
@@ -3500,7 +3538,7 @@ EXAMPLES
       --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.67/src/commands/force/data/bulk/upsert.ts)_
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/4.0.68/src/commands/force/data/bulk/upsert.ts)_
 
 ## `sf help [COMMAND]`
 
@@ -3560,354 +3598,65 @@ EXAMPLES
     $ sf info releasenotes display --version latest
 ```
 
-_See code: [@salesforce/plugin-info](https://github.com/salesforcecli/plugin-info/blob/3.4.100/src/commands/info/releasenotes/display.ts)_
+_See code: [@salesforce/plugin-info](https://github.com/salesforcecli/plugin-info/blob/3.4.101/src/commands/info/releasenotes/display.ts)_
 
-## `sf lightning generate app`
+## `sf logic get test`
 
-Generate a Lightning App.
+Get the results of a test run.
 
 ```
 USAGE
-  $ sf lightning generate app -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningApp] [-d <value>] [--api-version
-    <value>]
+  $ sf logic get test -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>]
+    [--detailed-coverage -c] [-d <value>] [-r human|tap|junit|json] [--concise]
 
 FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -n, --name=<value>         (required) Name of the generated Lightning App.
-  -t, --template=<option>    [default: DefaultLightningApp] Template to use for file creation.
-                             <options: DefaultLightningApp>
-      --api-version=<value>  Override the api version used for api requests made by this command
+  -c, --code-coverage           Retrieve code coverage results.
+  -d, --output-dir=<value>      Directory in which to store test result files.
+  -i, --test-run-id=<value>     (required) ID of the test run.
+  -o, --target-org=<value>      (required) Username or alias of the target org. Not required if the `target-org`
+                                configuration variable is already set.
+  -r, --result-format=<option>  [default: human] Format of the test results.
+                                <options: human|tap|junit|json>
+      --api-version=<value>     Override the api version used for api requests made by this command
+      --concise                 Display only failed test results; works with human-readable output only.
+      --detailed-coverage       Display detailed code coverage per test.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
   --json               Format output as json.
 
 DESCRIPTION
-  Generate a Lightning App.
+  Get the results of a test run.
 
-  Generates a Lightning App bundle in the specified directory or the current working directory. The bundle consists of
-  multiple files in a folder with the designated name.
+  When you run 'sf logic run test' to test Apex classes and Flows asynchronously, it returns a test run ID. Use that ID
+  with this command to see the results.
 
-ALIASES
-  $ sf force lightning app create
+  To see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level
+  summary of the test run and the code coverage values for classes in your org. If you specify human-readable result
+  format, use the --detailed-coverage flag to see detailed coverage results for each test method run.
 
 EXAMPLES
-  Generate the metadata files for a Lightning app bundle called "myapp" in the current directory:
-
-    $ sf lightning generate app --name myapp
-
-  Similar to the previous example, but generate the files in the "force-app/main/default/aura" directory:
-
-    $ sf lightning generate app --name myapp --output-dir force-app/main/default/aura
-
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
-
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
-
-  -n, --name=<value>  Name of the generated Lightning App.
+  Get the results for a specific test run ID in the default human-readable format; uses your default org:
 
-    The name can be up to 40 characters and must start with a letter.
+    $ sf logic get test --test-run-id <test run id>
 
-  -t, --template=DefaultLightningApp  Template to use for file creation.
+  Get the results for a specific test run ID, format them as JUnit, and save them to the "test-results/junit"
+  directory; uses the org with alias "my-scratch":
 
-    Supplied parameter values or default values are filled into a copy of the template.
+    $ sf logic get test --test-run-id <test run id> --result-format junit --target-org my-scratch
 ```
 
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/lightning/generate/app.ts)_
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.6/src/commands/logic/get/test.ts)_
 
-## `sf lightning generate component`
+## `sf logic run test`
 
-Generate a bundle for an Aura component or a Lightning web component.
+Invoke tests for Apex and Flows in an org.
 
 ```
 USAGE
-  $ sf lightning generate component -n <value> [--json] [--flags-dir <value>] [-t
-    default|analyticsDashboard|analyticsDashboardWithStep] [-d <value>] [--api-version <value>] [--type aura|lwc]
-
-FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -n, --name=<value>         (required) Name of the generated Lightning Component.
-  -t, --template=<option>    [default: default] Template to use for file creation.
-                             <options: default|analyticsDashboard|analyticsDashboardWithStep>
-      --api-version=<value>  Override the api version used for api requests made by this command
-      --type=<option>        [default: aura] Type of the component bundle.
-                             <options: aura|lwc>
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Generate a bundle for an Aura component or a Lightning web component.
-
-  Generates the bundle in the specified directory or the current working directory. The bundle consists of multiple
-  files in a directory with the designated name. Lightning web components are contained in the directory with name
-  "lwc", Aura components in "aura".
-
-  To generate a Lightning web component, pass "--type lwc" to the command. If you don’t specify --type, Salesforce CLI
-  generates an Aura component by default.
-
-ALIASES
-  $ sf force lightning component create
-
-EXAMPLES
-  Generate the metadata files for an Aura component bundle in the current directory:
-
-    $ sf lightning generate component --name mycomponent
-
-  Generate a Lightning web component bundle in the current directory:
-
-    $ sf lightning generate component --name mycomponent --type lwc
-
-  Generate an Aura component bundle in the "force-app/main/default/aura" directory:
-
-    $ sf lightning generate component --name mycomponent --output-dir force-app/main/default/aura
-
-  Generate a Lightning web component bundle in the "force-app/main/default/lwc" directory:
-
-    $ sf lightning generate component --name mycomponent --type lwc --output-dir force-app/main/default/lwc
-
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
-
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
-
-  -n, --name=<value>  Name of the generated Lightning Component.
-
-    The name can be up to 40 characters and must start with a letter.
-
-  -t, --template=default|analyticsDashboard|analyticsDashboardWithStep  Template to use for file creation.
-
-    Supplied parameter values or default values are filled into a copy of the template.
-```
-
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/lightning/generate/component.ts)_
-
-## `sf lightning generate event`
-
-Generate a Lightning Event.
-
-```
-USAGE
-  $ sf lightning generate event -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningEvt] [-d <value>] [--api-version
-    <value>]
-
-FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -n, --name=<value>         (required) Name of the generated Lightning Event.
-  -t, --template=<option>    [default: DefaultLightningEvt] Template to use for file creation.
-                             <options: DefaultLightningEvt>
-      --api-version=<value>  Override the api version used for api requests made by this command
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Generate a Lightning Event.
-
-  Generates a Lightning Event bundle in the specified directory or the current working directory. The bundle consists of
-  multiple files in a folder with the designated name.
-
-ALIASES
-  $ sf force lightning event create
-
-EXAMPLES
-  Generate the metadata files for a Lightning event bundle called "myevent" in the current directory:
-
-    $ sf lightning generate event --name myevent
-
-  Similar to previous example, but generate the files in the "force-app/main/default/aura" directory:
-
-    $ sf lightning generate event --name myevent --output-dir force-app/main/default/aura
-
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
-
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
-
-  -n, --name=<value>  Name of the generated Lightning Event.
-
-    The name can be up to 40 characters and must start with a letter.
-
-  -t, --template=DefaultLightningEvt  Template to use for file creation.
-
-    Supplied parameter values or default values are filled into a copy of the template.
-```
-
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/lightning/generate/event.ts)_
-
-## `sf lightning generate interface`
-
-Generate a Lightning Interface.
-
-```
-USAGE
-  $ sf lightning generate interface -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningIntf] [-d <value>]
-    [--api-version <value>]
-
-FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -n, --name=<value>         (required) Name of the generated Lightning Interface.
-  -t, --template=<option>    [default: DefaultLightningIntf] Template to use for file creation.
-                             <options: DefaultLightningIntf>
-      --api-version=<value>  Override the api version used for api requests made by this command
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Generate a Lightning Interface.
-
-  Generates a Lightning Interface bundle in the specified directory or the current working directory. The bundle
-  consists of multiple files in a folder with the designated name.
-
-ALIASES
-  $ sf force lightning interface create
-
-EXAMPLES
-  Generate the metadata files for a Lightning interface bundle called "myinterface" in the current directory:
-
-    $ sf lightning generate interface --name myinterface
-
-  Similar to the previous example but generate the files in the "force-app/main/default/aura" directory:
-
-    $ sf lightning generate interface --name myinterface --output-dir force-app/main/default/aura
-
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
-
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
-
-  -n, --name=<value>  Name of the generated Lightning Interface.
-
-    The name can be up to 40 characters and must start with a letter.
-
-  -t, --template=DefaultLightningIntf  Template to use for file creation.
-
-    Supplied parameter values or default values are filled into a copy of the template.
-```
-
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/lightning/generate/interface.ts)_
-
-## `sf lightning generate test`
-
-Generate a Lightning test.
-
-```
-USAGE
-  $ sf lightning generate test -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningTest] [-d <value>]
-    [--api-version <value>]
-
-FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -n, --name=<value>         (required) Name of the generated Lightning Test.
-  -t, --template=<option>    [default: DefaultLightningTest] Template to use for file creation.
-                             <options: DefaultLightningTest>
-      --api-version=<value>  Override the api version used for api requests made by this command
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Generate a Lightning test.
-
-  Generates the test in the specified directory or the current working directory. The .resource file and associated
-  metadata file are generated.
-
-ALIASES
-  $ sf force lightning test create
-
-EXAMPLES
-  Generate the metadata files for the Lightning test called MyLightningTest in the current directory:
-
-    $ sf lightning generate test --name MyLightningTest
-
-  Similar to the previous example but generate the files in the "force-app/main/default/lightningTests" directory:
-
-    $ sf lightning generate test --name MyLightningTest --output-dir force-app/main/default/lightningTests
-
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
-
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
-
-  -n, --name=<value>  Name of the generated Lightning Test.
-
-    Name of the new Lightning test; can be up to 40 characters and must start with a letter.
-
-  -t, --template=DefaultLightningTest  Template to use for file creation.
-
-    Supplied parameter values or default values are filled into a copy of the template.
-```
-
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/lightning/generate/test.ts)_
-
-## `sf logic get test`
-
-Get the results of a test run.
-
-```
-USAGE
-  $ sf logic get test -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>]
-    [--detailed-coverage -c] [-d <value>] [-r human|tap|junit|json] [--concise]
-
-FLAGS
-  -c, --code-coverage           Retrieve code coverage results.
-  -d, --output-dir=<value>      Directory in which to store test result files.
-  -i, --test-run-id=<value>     (required) ID of the test run.
-  -o, --target-org=<value>      (required) Username or alias of the target org. Not required if the `target-org`
-                                configuration variable is already set.
-  -r, --result-format=<option>  [default: human] Format of the test results.
-                                <options: human|tap|junit|json>
-      --api-version=<value>     Override the api version used for api requests made by this command
-      --concise                 Display only failed test results; works with human-readable output only.
-      --detailed-coverage       Display detailed code coverage per test.
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Get the results of a test run.
-
-  When you run 'sf logic run test' to test Apex classes and Flows asynchronously, it returns a test run ID. Use that ID
-  with this command to see the results.
-
-  To see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level
-  summary of the test run and the code coverage values for classes in your org. If you specify human-readable result
-  format, use the --detailed-coverage flag to see detailed coverage results for each test method run.
-
-EXAMPLES
-  Get the results for a specific test run ID in the default human-readable format; uses your default org:
-
-    $ sf logic get test --test-run-id <test run id>
-
-  Get the results for a specific test run ID, format them as JUnit, and save them to the "test-results/junit"
-  directory; uses the org with alias "my-scratch":
-
-    $ sf logic get test --test-run-id <test run id> --result-format junit --target-org my-scratch
-```
-
-_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.5/src/commands/logic/get/test.ts)_
-
-## `sf logic run test`
-
-Invoke tests for Apex and Flows in an org.
-
-```
-USAGE
-  $ sf logic run test -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-d <value>] [-l
-    RunLocalTests|RunAllTestsInOrg|RunSpecifiedTests] [-n <value>... | -s <value>... | -t <value>... | --test-category
-    Apex|Flow...] [-r human|tap|junit|json] [-w <value>] [-y] [-v -c] [--concise]
+  $ sf logic run test -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-d <value>] [-l
+    RunLocalTests|RunAllTestsInOrg|RunSpecifiedTests] [-n <value>... | -s <value>... | -t <value>... | --test-category
+    Apex|Flow...] [-r human|tap|junit|json] [-w <value>] [-y] [-v -c] [--concise]
 
 FLAGS
   -c, --code-coverage              Retrieve code coverage results.
@@ -4019,7 +3768,7 @@ FLAG DESCRIPTIONS
     --tests Test1 --tests Test2
 ```
 
-_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.5/src/commands/logic/run/test.ts)_
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/3.9.6/src/commands/logic/run/test.ts)_
 
 ## `sf org assign permset`
 
@@ -4065,7 +3814,7 @@ EXAMPLES
     $ sf org assign permset --name DreamHouse --on-behalf-of user1@my.org --on-behalf-of user2 --on-behalf-of user
 ```
 
-_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.48/src/commands/org/assign/permset.ts)_
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.49/src/commands/org/assign/permset.ts)_
 
 ## `sf org assign permsetlicense`
 
@@ -4112,7 +3861,7 @@ EXAMPLES
       user3
 ```
 
-_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.48/src/commands/org/assign/permsetlicense.ts)_
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.49/src/commands/org/assign/permsetlicense.ts)_
 
 ## `sf org create sandbox`
 
@@ -4246,7 +3995,7 @@ FLAG DESCRIPTIONS
     You can specify either --source-sandbox-name or --source-id when cloning an existing sandbox, but not both.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/create/sandbox.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/create/sandbox.ts)_
 
 ## `sf org create scratch`
 
@@ -4428,7 +4177,7 @@ FLAG DESCRIPTIONS
     Omit this flag to have Salesforce generate a unique username for your org.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/create/scratch.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/create/scratch.ts)_
 
 ## `sf org create user`
 
@@ -4536,7 +4285,7 @@ FLAG DESCRIPTIONS
     might be different than what you specify in the definition file.
 ```
 
-_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.48/src/commands/org/create/user.ts)_
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.49/src/commands/org/create/user.ts)_
 
 ## `sf org delete sandbox`
 
@@ -4582,7 +4331,7 @@ EXAMPLES
     $ sf org delete sandbox --target-org my-sandbox --no-prompt
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/delete/sandbox.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/delete/sandbox.ts)_
 
 ## `sf org delete scratch`
 
@@ -4626,7 +4375,7 @@ EXAMPLES
     $ sf org delete scratch --target-org my-scratch-org --no-prompt
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/delete/scratch.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/delete/scratch.ts)_
 
 ## `sf org disable tracking`
 
@@ -4665,7 +4414,7 @@ EXAMPLES
     $ sf org disable tracking
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/disable/tracking.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/disable/tracking.ts)_
 
 ## `sf org display`
 
@@ -4710,7 +4459,7 @@ EXAMPLES
     $ sf org display --target-org TestOrg1 --verbose
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/display.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/display.ts)_
 
 ## `sf org display user`
 
@@ -4749,7 +4498,7 @@ EXAMPLES
     $ sf org display user --target-org me@my.org --json
 ```
 
-_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.48/src/commands/org/display/user.ts)_
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.49/src/commands/org/display/user.ts)_
 
 ## `sf org enable tracking`
 
@@ -4791,7 +4540,7 @@ EXAMPLES
     $ sf org enable tracking
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/enable/tracking.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/enable/tracking.ts)_
 
 ## `sf org generate password`
 
@@ -4858,7 +4607,7 @@ EXAMPLES
     $ sf org generate password --on-behalf-of user1@my.org --on-behalf-of user2@my.org --on-behalf-of user3@my.org
 ```
 
-_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.48/src/commands/org/generate/password.ts)_
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.49/src/commands/org/generate/password.ts)_
 
 ## `sf org list`
 
@@ -4897,7 +4646,7 @@ EXAMPLES
     $ sf org list --clean
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/list.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/list.ts)_
 
 ## `sf org list auth`
 
@@ -4929,7 +4678,7 @@ EXAMPLES
     $ sf org list auth
 ```
 
-_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/4.1.4/src/commands/org/list/auth.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/4.1.5/src/commands/org/list/auth.ts)_
 
 ## `sf org list limits`
 
@@ -4969,7 +4718,7 @@ EXAMPLES
     $ sf org list limits --target-org my-scratch-org
 ```
 
-_See code: [@salesforce/plugin-limits](https://github.com/salesforcecli/plugin-limits/blob/3.3.74/src/commands/org/list/limits.ts)_
+_See code: [@salesforce/plugin-limits](https://github.com/salesforcecli/plugin-limits/blob/3.3.75/src/commands/org/list/limits.ts)_
 
 ## `sf org list metadata`
 
@@ -5036,7 +4785,7 @@ FLAG DESCRIPTIONS
     Examples of metadata types that use folders are Dashboard, Document, EmailTemplate, and Report.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/list/metadata.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/list/metadata.ts)_
 
 ## `sf org list metadata-types`
 
@@ -5091,7 +4840,7 @@ FLAG DESCRIPTIONS
     Override the api version used for api requests made by this command
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/list/metadata-types.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/list/metadata-types.ts)_
 
 ## `sf org list sobject record-counts`
 
@@ -5137,7 +4886,7 @@ EXAMPLES
     $ sf org list sobject record-counts --sobject Account --sobject Lead --target-org my-scratch-org
 ```
 
-_See code: [@salesforce/plugin-limits](https://github.com/salesforcecli/plugin-limits/blob/3.3.74/src/commands/org/list/sobject/record-counts.ts)_
+_See code: [@salesforce/plugin-limits](https://github.com/salesforcecli/plugin-limits/blob/3.3.75/src/commands/org/list/sobject/record-counts.ts)_
 
 ## `sf org list users`
 
@@ -5175,7 +4924,7 @@ EXAMPLES
     $ sf org list users --target-org me@my.org
 ```
 
-_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.48/src/commands/org/list/users.ts)_
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/3.6.49/src/commands/org/list/users.ts)_
 
 ## `sf org login access-token`
 
@@ -5229,7 +4978,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/4.1.4/src/commands/org/login/access-token.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/4.1.5/src/commands/org/login/access-token.ts)_
 
 ## `sf org login jwt`
 
@@ -5320,7 +5069,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/4.1.4/src/commands/org/login/jwt.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/4.1.5/src/commands/org/login/jwt.ts)_
 
 ## `sf org login sfdx-url`
 
@@ -5390,7 +5139,7 @@ EXAMPLES
   $ echo url | sf org login sfdx-url --sfdx-url-stdin
 ```
 
-_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/4.1.4/src/commands/org/login/sfdx-url.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/4.1.5/src/commands/org/login/sfdx-url.ts)_
 
 ## `sf org login web`
 
@@ -5495,7 +5244,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/4.1.4/src/commands/org/login/web.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/4.1.5/src/commands/org/login/web.ts)_
 
 ## `sf org logout`
 
@@ -5561,7 +5310,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/4.1.4/src/commands/org/logout.ts)_
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/4.1.5/src/commands/org/logout.ts)_
 
 ## `sf org open`
 
@@ -5637,7 +5386,7 @@ EXAMPLES
     $ sf org open --source-file force-app/main/default/bots/Coral_Cloud_Agent/Coral_Cloud_Agent.bot-meta.xml
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/open.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/open.ts)_
 
 ## `sf org open agent`
 
@@ -5688,7 +5437,7 @@ EXAMPLES
     $ sf org open agent --target-org MyTestOrg1 --browser firefox --api-name Coral_Cloud_Agent
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/open/agent.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/open/agent.ts)_
 
 ## `sf org open authoring-bundle`
 
@@ -5734,7 +5483,7 @@ EXAMPLES
     $ sf org open authoring-bundle --target-org MyTestOrg1 --browser firefox
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/open/authoring-bundle.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/open/authoring-bundle.ts)_
 
 ## `sf org refresh sandbox`
 
@@ -5837,7 +5586,7 @@ FLAG DESCRIPTIONS
     You can specify either --source-sandbox-name or --source-id when refreshing an existing sandbox, but not both.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/refresh/sandbox.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/refresh/sandbox.ts)_
 
 ## `sf org resume sandbox`
 
@@ -5900,7 +5649,7 @@ FLAG DESCRIPTIONS
     returns the job ID. To resume checking the sandbox creation, rerun this command.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/resume/sandbox.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/resume/sandbox.ts)_
 
 ## `sf org resume scratch`
 
@@ -5953,7 +5702,7 @@ FLAG DESCRIPTIONS
     returns the job ID. To resume checking the scratch creation, rerun this command.
 ```
 
-_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.64/src/commands/org/resume/scratch.ts)_
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.9.66/src/commands/org/resume/scratch.ts)_
 
 ## `sf package convert`
 
@@ -6050,7 +5799,7 @@ FLAG DESCRIPTIONS
     --installation-key-bypass flag is required.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/convert.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/convert.ts)_
 
 ## `sf package create`
 
@@ -6129,7 +5878,7 @@ FLAG DESCRIPTIONS
     Org-Dependent Unlocked Packages" in the Salesforce DX Developer Guide.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/create.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/create.ts)_
 
 ## `sf package delete`
 
@@ -6171,7 +5920,7 @@ EXAMPLES
     $ sf package delete --package 0Ho... --target-dev-hub devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/delete.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/delete.ts)_
 
 ## `sf package install`
 
@@ -6270,7 +6019,7 @@ FLAG DESCRIPTIONS
     - Delete: Delete removed components, except for custom objects and custom fields, that don't have dependencies.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/install.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/install.ts)_
 
 ## `sf package install report`
 
@@ -6303,7 +6052,7 @@ EXAMPLES
     $ sf package install report --request-id 0Hf... --target-org me@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/install/report.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/install/report.ts)_
 
 ## `sf package installed list`
 
@@ -6335,7 +6084,7 @@ EXAMPLES
     $ sf package installed list --target-org me@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/installed/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/installed/list.ts)_
 
 ## `sf package list`
 
@@ -6373,7 +6122,7 @@ EXAMPLES
     $ sf package list --target-dev-hub devhub@example.com --verbose
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/list.ts)_
 
 ## `sf package push-upgrade abort`
 
@@ -6412,7 +6161,7 @@ EXAMPLES
     $ sf package push-upgrade abort --push-request-id 0DV... --target-dev-hub devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/push-upgrade/abort.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/push-upgrade/abort.ts)_
 
 ## `sf package push-upgrade list`
 
@@ -6471,7 +6220,7 @@ EXAMPLES
     $ sf package push-upgrade list --package 033xyz –-status Failed
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/push-upgrade/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/push-upgrade/list.ts)_
 
 ## `sf package push-upgrade report`
 
@@ -6513,7 +6262,7 @@ EXAMPLES
     $ sf package push-upgrade report --push-request-id 0DV... --target-dev-hub devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/push-upgrade/report.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/push-upgrade/report.ts)_
 
 ## `sf package push-upgrade schedule`
 
@@ -6600,7 +6349,7 @@ FLAG DESCRIPTIONS
     Overrides the value of the target-dev-hub configuration variable, if set.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/push-upgrade/schedule.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/push-upgrade/schedule.ts)_
 
 ## `sf package uninstall`
 
@@ -6648,7 +6397,7 @@ EXAMPLES
     $ sf package uninstall --package "Undesirable Package Alias"
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/uninstall.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/uninstall.ts)_
 
 ## `sf package uninstall report`
 
@@ -6681,7 +6430,7 @@ EXAMPLES
     $ sf package uninstall report --request-id 06y... --target-org me@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/uninstall/report.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/uninstall/report.ts)_
 
 ## `sf package update`
 
@@ -6749,7 +6498,7 @@ FLAG DESCRIPTIONS
     the Installed Packages page. Only released package versions can be set as the recommended version.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/update.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/update.ts)_
 
 ## `sf package version create`
 
@@ -6759,9 +6508,9 @@ Create a package version in the Dev Hub org.
 USAGE
   $ sf package version create -v <value> [--json] [--flags-dir <value>] [--api-version <value>] [-b <value>] [-c |
     --skip-validation] [-f <value>] [-k <value>] [-x] [-p <value>] [-d <value>] [--post-install-script <value>]
-    [--post-install-url <value>] [--releasenotes-url <value>] [--skip-ancestor-check] [--async-validation | ] [-t
-    <value>] [--uninstall-script <value>] [-e <value>] [-a <value>] [-n <value>] [-w <value>] [--language <value>]
-    [--verbose]
+    [--post-install-url <value>] [--releasenotes-url <value>] [--skip-ancestor-check] [--async-validation | ]
+    [--generate-pkg-zip] [-t <value>] [--uninstall-script <value>] [-e <value>] [-a <value>] [-n <value>] [-w <value>]
+    [--language <value>] [--verbose]
 
 FLAGS
   -a, --version-name=<value>         Name of the package version to be created; overrides the sfdx-project.json value.
@@ -6788,12 +6537,14 @@ FLAGS
                                      --installation-key-bypass is required)
       --api-version=<value>          Override the api version used for api requests made by this command
       --async-validation             Return a new package version before completing package validations.
+      --generate-pkg-zip             Generate a package ZIP file that you can use for debugging or to examine the
+                                     package contents.
       --language=<value>             Language for the package.
       --post-install-script=<value>  Name of the post-install script; applies to managed packages only.
       --post-install-url=<value>     Post-install instructions URL.
       --releasenotes-url=<value>     Release notes URL.
-      --skip-ancestor-check          Overrides ancestry requirements, which allows you to specify a package ancestor
-                                     that isn’t the highest released package version.
+      --skip-ancestor-check          Override ancestry requirements, which allows you to specify a package ancestor that
+                                     isn’t the highest released package version.
       --skip-validation              Skip validation during package version creation; you can’t promote unvalidated
                                      package versions.
       --uninstall-script=<value>     Uninstall script name; applies to managed packages only.
@@ -6924,7 +6675,7 @@ FLAG DESCRIPTIONS
     periods of no output from commands.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/create.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/create.ts)_
 
 ## `sf package version create list`
 
@@ -6985,7 +6736,7 @@ EXAMPLES
     $ sf package version create list --created-last-days 0 --status Success
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/create/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/create/list.ts)_
 
 ## `sf package version create report`
 
@@ -7028,7 +6779,7 @@ EXAMPLES
     $ sf package version create report --package-create-request-id 08c... --target-dev-hub devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/create/report.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/create/report.ts)_
 
 ## `sf package version delete`
 
@@ -7069,7 +6820,7 @@ EXAMPLES
     $ sf package version delete --package 04t... --target-org devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/delete.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/delete.ts)_
 
 ## `sf package version displayancestry`
 
@@ -7129,7 +6880,7 @@ FLAG DESCRIPTIONS
     You can use the DOT code output in graph visualization software to create tree visualizations.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/displayancestry.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/displayancestry.ts)_
 
 ## `sf package version displaydependencies`
 
@@ -7191,7 +6942,7 @@ FLAG DESCRIPTIONS
     package, which must be installed last.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/displaydependencies.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/displaydependencies.ts)_
 
 ## `sf package version list`
 
@@ -7267,7 +7018,7 @@ EXAMPLES
     $ sf package version list --packages exp-mgr,exp-mgr-util --released --modified-last-days 0
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/list.ts)_
 
 ## `sf package version promote`
 
@@ -7311,7 +7062,7 @@ EXAMPLES
     $ sf package version promote --package "Awesome Package Alias"
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/promote.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/promote.ts)_
 
 ## `sf package version report`
 
@@ -7351,7 +7102,7 @@ EXAMPLES
     $ sf package version report --package "Your Package Alias" --target-dev-hub devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/report.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/report.ts)_
 
 ## `sf package version retrieve`
 
@@ -7396,7 +7147,7 @@ EXAMPLES
     $ sf package version retrieve --package 04tXXX --output-dir my-directory/ --target-dev-hub devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/retrieve.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/retrieve.ts)_
 
 ## `sf package version update`
 
@@ -7449,7 +7200,7 @@ EXAMPLES
     $ sf package version update --package 04t... --version-description "New Package Version Description"
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package/version/update.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package/version/update.ts)_
 
 ## `sf package1 version create`
 
@@ -7516,7 +7267,7 @@ FLAG DESCRIPTIONS
     subscribers.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package1/version/create.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package1/version/create.ts)_
 
 ## `sf package1 version create get`
 
@@ -7549,7 +7300,7 @@ EXAMPLES
     $ sf package1 version create get --request-id 0HD... --target-org myorg@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package1/version/create/get.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package1/version/create/get.ts)_
 
 ## `sf package1 version display`
 
@@ -7583,7 +7334,7 @@ EXAMPLES
     $ sf package1 version display --package-version-id 04t... --target-org myorg@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package1/version/display.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package1/version/display.ts)_
 
 ## `sf package1 version list`
 
@@ -7621,7 +7372,7 @@ FLAG DESCRIPTIONS
     If not specified, shows all versions for all packages (managed and unmanaged) in the org.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.24.11/src/commands/package1/version/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.25.1/src/commands/package1/version/list.ts)_
 
 ## `sf plugins`
 
@@ -7644,7 +7395,7 @@ EXAMPLES
   $ sf plugins
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.55/src/commands/plugins/index.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.56/src/commands/plugins/index.ts)_
 
 ## `sf plugins discover`
 
@@ -7662,7 +7413,7 @@ EXAMPLES
   $ sf plugins discover
 ```
 
-_See code: [@salesforce/plugin-marketplace](https://github.com/salesforcecli/plugin-marketplace/blob/1.3.8/src/commands/plugins/discover.ts)_
+_See code: [@salesforce/plugin-marketplace](https://github.com/salesforcecli/plugin-marketplace/blob/1.3.10/src/commands/plugins/discover.ts)_
 
 ## `sf plugins:inspect PLUGIN...`
 
@@ -7689,7 +7440,7 @@ EXAMPLES
   $ sf plugins inspect @salesforce/plugin-packaging
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.55/src/commands/plugins/inspect.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.56/src/commands/plugins/inspect.ts)_
 
 ## `sf plugins install PLUGIN`
 
@@ -7738,7 +7489,7 @@ EXAMPLES
     $ sf plugins install someuser/someplugin
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.55/src/commands/plugins/install.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.56/src/commands/plugins/install.ts)_
 
 ## `sf plugins link PATH`
 
@@ -7769,7 +7520,7 @@ EXAMPLES
   $ sf plugins link @salesforce/plugin-packaging
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.55/src/commands/plugins/link.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.56/src/commands/plugins/link.ts)_
 
 ## `sf plugins reset`
 
@@ -7784,7 +7535,7 @@ FLAGS
   --reinstall  Reinstall all plugins after uninstalling.
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.55/src/commands/plugins/reset.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.56/src/commands/plugins/reset.ts)_
 
 ## `sf plugins trust verify`
 
@@ -7841,7 +7592,7 @@ EXAMPLES
   $ sf plugins uninstall @salesforce/plugin-packaging
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.55/src/commands/plugins/uninstall.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.56/src/commands/plugins/uninstall.ts)_
 
 ## `sf plugins update`
 
@@ -7859,7 +7610,7 @@ DESCRIPTION
   Update installed plugins.
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.55/src/commands/plugins/update.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.56/src/commands/plugins/update.ts)_
 
 ## `sf project convert mdapi`
 
@@ -7922,7 +7673,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.24.7/src/commands/project/convert/mdapi.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/convert/mdapi.ts)_
 
 ## `sf project convert source`
 
@@ -7995,7 +7746,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.24.7/src/commands/project/convert/source.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/convert/source.ts)_
 
 ## `sf project convert source-behavior`
 
@@ -8054,7 +7805,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.24.7/src/commands/project/convert/source-behavior.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/convert/source-behavior.ts)_
 
 ## `sf project delete source`
 
@@ -8207,7 +7958,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.24.7/src/commands/project/delete/source.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/delete/source.ts)_
 
 ## `sf project delete tracking`
 
@@ -8244,7 +7995,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.24.7/src/commands/project/delete/tracking.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/delete/tracking.ts)_
 
 ## `sf project deploy cancel`
 
@@ -8316,7 +8067,7 @@ FLAG DESCRIPTIONS
     project deploy report".
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.7/src/commands/project/deploy/cancel.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/deploy/cancel.ts)_
 
 ## `sf project deploy preview`
 
@@ -8399,7 +8150,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.24.7/src/commands/project/deploy/preview.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/deploy/preview.ts)_
 
 ## `sf project deploy quick`
 
@@ -8492,7 +8243,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.24.7/src/commands/project/deploy/quick.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/deploy/quick.ts)_
 
 ## `sf project deploy report`
 
@@ -8584,7 +8335,7 @@ FLAG DESCRIPTIONS
     --coverage-formatters lcov --coverage-formatters clover
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.7/src/commands/project/deploy/report.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/deploy/report.ts)_
 
 ## `sf project deploy resume`
 
@@ -8681,7 +8432,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.24.7/src/commands/project/deploy/resume.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/deploy/resume.ts)_
 
 ## `sf project deploy start`
 
@@ -8947,7 +8698,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.24.7/src/commands/project/deploy/start.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/deploy/start.ts)_
 
 ## `sf project deploy validate`
 
@@ -9151,122 +8902,17 @@ ERROR CODES
   Canceling (69)         The deploy is being canceled.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.7/src/commands/project/deploy/validate.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/deploy/validate.ts)_
 
-## `sf project generate`
+## `sf project generate manifest`
 
-Generate a Salesforce DX project.
+Create a project manifest that lists the metadata components you want to deploy or retrieve.
 
 ```
 USAGE
-  $ sf project generate -n <value> [--json] [--flags-dir <value>] [-t standard|empty|analytics] [-d <value>] [-s
-    <value>] [-p <value>] [-x] [--api-version <value>]
-
-FLAGS
-  -d, --output-dir=<value>           [default: .] Directory for saving the created files.
-  -n, --name=<value>                 (required) Name of the generated project.
-  -p, --default-package-dir=<value>  [default: force-app] Default package directory name.
-  -s, --namespace=<value>            Namespace associated with this project and any connected scratch orgs.
-  -t, --template=<option>            [default: standard] Template to use for project creation.
-                                     <options: standard|empty|analytics>
-  -x, --manifest                     Generate a manifest (package.xml) for change-set based development.
-      --api-version=<value>          Will set this version as sourceApiVersion in the sfdx-project.json file
-
-GLOBAL FLAGS
-  --flags-dir=<value>  Import flag values from a directory.
-  --json               Format output as json.
-
-DESCRIPTION
-  Generate a Salesforce DX project.
-
-  A Salesforce DX project has a specific structure and a configuration file (sfdx-project.json) that identifies the
-  directory as a Salesforce DX project. This command generates the necessary configuration files and directories to get
-  you started.
-
-  By default, the generated sfdx-project.json file sets the sourceApiVersion property to the default API version
-  currently used by Salesforce CLI. To specify a different version, set the apiVersion configuration variable. For
-  example: "sf config set apiVersion=57.0 --global".
-
-ALIASES
-  $ sf force project create
-
-EXAMPLES
-  Generate a project called "mywork":
-
-    $ sf project generate --name mywork
-
-  Similar to previous example, but generate the files in a directory called "myapp":
-
-    $ sf project generate --name mywork --default-package-dir myapp
-
-  Similar to prevoius example, but also generate a default package.xml manifest file:
-
-    $ sf project generate --name mywork --default-package-dir myapp --manifest
-
-  Generate a project with the minimum files and directories:
-
-    $ sf project generate --name mywork --template empty
-
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
-
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
-
-  -n, --name=<value>  Name of the generated project.
-
-    Generates a project directory with this name; any valid directory name is accepted. Also sets the "name" property in
-    the sfdx-project.json file to this name.
-
-  -p, --default-package-dir=<value>  Default package directory name.
-
-    Metadata items such as classes and Lightning bundles are placed inside this folder.
-
-  -t, --template=standard|empty|analytics  Template to use for project creation.
-
-    The template determines the sample configuration files and directories that this command generates. For example, the
-    empty template provides these files and directory to get you started.
-
-    - .forceignore
-    - config/project-scratch-def.json
-    - sfdx-project.json
-    - package.json
-    - force-app (basic source directory structure)
-
-    The standard template provides a complete force-app directory structure so you know where to put your source. It
-    also provides additional files and scripts, especially useful when using Salesforce Extensions for VS Code. For
-    example:
-
-    - .gitignore: Use Git for version control.
-    - .prettierrc and .prettierignore: Use Prettier to format your Aura components.
-    - .vscode/extensions.json: When launched, Visual Studio Code, prompts you to install the recommended extensions for
-    your project.
-    - .vscode/launch.json: Configures Replay Debugger.
-    - .vscode/settings.json: Additional configuration settings.
-
-    The analytics template provides similar files and the force-app/main/default/waveTemplates directory.
-
-  -x, --manifest  Generate a manifest (package.xml) for change-set based development.
-
-    Generates a default manifest (package.xml) for fetching Apex, Visualforce, Lightning components, and static
-    resources.
-
-  --api-version=<value>  Will set this version as sourceApiVersion in the sfdx-project.json file
-
-    Override the api version used for api requests made by this command
-```
-
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/project/generate.ts)_
-
-## `sf project generate manifest`
-
-Create a project manifest that lists the metadata components you want to deploy or retrieve.
-
-```
-USAGE
-  $ sf project generate manifest [--json] [--flags-dir <value>] [--api-version <value>] [-m <value>...] [-p <value>...] [-n
-    <value> | -t pre|post|destroy|package] [-c managed|unlocked... --from-org <value>] [--excluded-metadata <value>...]
-    [-d <value>]
+  $ sf project generate manifest [--json] [--flags-dir <value>] [--api-version <value>] [-m <value>...] [-p <value>...] [-n
+    <value> | -t pre|post|destroy|package] [-c managed|unlocked... --from-org <value>] [--excluded-metadata <value>...]
+    [-d <value>]
 
 FLAGS
   -c, --include-packages=<option>...  Package types (managed, unlocked) whose metadata is included in the manifest; by
@@ -9352,7 +8998,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.24.7/src/commands/project/generate/manifest.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/generate/manifest.ts)_
 
 ## `sf project list ignored`
 
@@ -9394,7 +9040,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.24.7/src/commands/project/list/ignored.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/list/ignored.ts)_
 
 ## `sf project reset tracking`
 
@@ -9443,7 +9089,7 @@ EXAMPLES
     $ sf project reset tracking --revision 30
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.7/src/commands/project/reset/tracking.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/reset/tracking.ts)_
 
 ## `sf project retrieve preview`
 
@@ -9497,7 +9143,7 @@ FLAG DESCRIPTIONS
     production orgs.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.7/src/commands/project/retrieve/preview.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/retrieve/preview.ts)_
 
 ## `sf project retrieve start`
 
@@ -9678,7 +9324,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.24.7/src/commands/project/retrieve/start.ts)_
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.8/src/commands/project/retrieve/start.ts)_
 
 ## `sf schema generate field`
 
@@ -9885,7 +9531,7 @@ DESCRIPTION
   Once you select a command, hit enter and it will show the help for that command.
 ```
 
-_See code: [@oclif/plugin-search](https://github.com/oclif/plugin-search/blob/1.2.37/src/commands/search.ts)_
+_See code: [@oclif/plugin-search](https://github.com/oclif/plugin-search/blob/1.2.38/src/commands/search.ts)_
 
 ## `sf sobject describe`
 
@@ -9932,7 +9578,7 @@ EXAMPLES
     $ sf sobject describe --sobject ApexCodeCoverage --use-tooling-api
 ```
 
-_See code: [@salesforce/plugin-schema](https://github.com/salesforcecli/plugin-schema/blob/3.3.90/src/commands/sobject/describe.ts)_
+_See code: [@salesforce/plugin-schema](https://github.com/salesforcecli/plugin-schema/blob/3.3.91/src/commands/sobject/describe.ts)_
 
 ## `sf sobject list`
 
@@ -9971,143 +9617,131 @@ EXAMPLES
     $ sf sobject list --sobject custom --target-org my-scratch-org
 ```
 
-_See code: [@salesforce/plugin-schema](https://github.com/salesforcecli/plugin-schema/blob/3.3.90/src/commands/sobject/list.ts)_
+_See code: [@salesforce/plugin-schema](https://github.com/salesforcecli/plugin-schema/blob/3.3.91/src/commands/sobject/list.ts)_
 
-## `sf static-resource generate`
+## `sf template generate analytics template`
 
-Generate a static resource.
+Generate a simple Analytics template.
 
 ```
 USAGE
-  $ sf static-resource generate -n <value> [--json] [--flags-dir <value>] [--type <value>] [-d <value>] [--api-version
+  $ sf template generate analytics template -n <value> [--json] [--flags-dir <value>] [-d <value>] [--api-version
   <value>]
 
 FLAGS
   -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -n, --name=<value>         (required) Name of the generated static resource.
+  -n, --name=<value>         (required) Name of the Analytics template.
       --api-version=<value>  Override the api version used for api requests made by this command
-      --type=<value>         [default: application/zip] Content type (mime type) of the generated static resource.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
   --json               Format output as json.
 
 DESCRIPTION
-  Generate a static resource.
+  Generate a simple Analytics template.
 
-  Generates the metadata resource file in the specified directory or the current working directory. Static resource
-  files must be contained in a parent directory called "staticresources" in your package directory. Either run this
-  command from an existing directory of this name, or use the --output-dir flag to create one or point to an existing
-  one.
+  The metadata files associated with the Analytics template must be contained in a parent directory called
+  "waveTemplates" in your package directory. Either run this command from an existing directory of this name, or use the
+  --output-dir flag to generate one or point to an existing one.
 
 ALIASES
-  $ sf force staticresource create
+  $ sf force analytics template create
+  $ sf analytics generate template
 
 EXAMPLES
-  Generate the metadata file for a static resource called MyResource in the current directory:
-
-    $ sf static-resource generate --name MyResource
-
-  Similar to previous example, but specifies a MIME type of application/json:
-
-    $ sf static-resource generate --name MyResource --type application/json
-
-  Generate the resource file in the "force-app/main/default/staticresources" directory:
+  Generate the metadata files for a simple Analytics template file called myTemplate in the
+  force-app/main/default/waveTemplates directory:
 
-    $ sf static-resource generate --name MyResource --output-dir force-app/main/default/staticresources
+    $ sf template generate analytics template --name myTemplate --output-dir force-app/main/default/waveTemplates
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
 
     The location can be an absolute path or relative to the current working directory. The default is the current
     directory.
-
-  -n, --name=<value>  Name of the generated static resource.
-
-    This name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin
-    with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.
-
-  --type=<value>  Content type (mime type) of the generated static resource.
-
-    Must be a valid MIME type such as application/json, application/javascript, application/zip, text/plain, text/css,
-    etc.
 ```
 
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/static-resource/generate.ts)_
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/analytics/template.ts)_
 
-## `sf update [CHANNEL]`
+## `sf template generate apex class`
 
-update the sf CLI
+Generate an Apex class.
 
 ```
 USAGE
-  $ sf update [CHANNEL] [--force |  | [-a | -v <value> | -i]] [-b ]
+  $ sf template generate apex class -n <value> [--json] [--flags-dir <value>] [-t
+    ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService] [-d <value>] [--api-version <value>]
 
 FLAGS
-  -a, --available        See available versions.
-  -b, --verbose          Show more details about the available versions.
-  -i, --interactive      Interactively select version to install. This is ignored if a channel is provided.
-  -v, --version=<value>  Install a specific version.
-      --force            Force a re-download of the requested version.
-
-DESCRIPTION
-  update the sf CLI
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Apex class.
+  -t, --template=<option>    [default: DefaultApexClass] Template to use for file creation.
+                             <options: ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService>
+      --api-version=<value>  Override the api version used for api requests made by this command
 
-EXAMPLES
-  Update to the stable channel:
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
 
-    $ sf update stable
+DESCRIPTION
+  Generate an Apex class.
 
-  Update to a specific version:
+  Generates the Apex *.cls file and associated metadata file. These files must be contained in a parent directory called
+  "classes" in your package directory. Either run this command from an existing directory of this name, or use the
+  --output-dir flag to generate one or point to an existing one.
 
-    $ sf update --version 1.0.0
+ALIASES
+  $ sf force apex class create
+  $ sf apex generate class
 
-  Interactively select version:
+EXAMPLES
+  Generate two metadata files associated with the MyClass Apex class (MyClass.cls and MyClass.cls-meta.xml) in the
+  current directory:
 
-    $ sf update --interactive
+    $ sf template generate apex class --name MyClass
 
-  See available versions:
+  Similar to previous example, but generates the files in the "force-app/main/default/classes" directory:
 
-    $ sf update --available
-```
+    $ sf template generate apex class --name MyClass --output-dir force-app/main/default/classes
 
-_See code: [@oclif/plugin-update](https://github.com/oclif/plugin-update/blob/4.7.18/src/commands/update.ts)_
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
 
-## `sf version`
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
 
-```
-USAGE
-  $ sf version [--json] [--verbose]
+  -n, --name=<value>  Name of the generated Apex class.
 
-FLAGS
-  --verbose  Show additional information about the CLI.
+    The name can be up to 40 characters and must start with a letter.
 
-GLOBAL FLAGS
-  --json  Format output as json.
+  -t, --template=ApexException|ApexUnitTest|BasicUnitTest|DefaultApexClass|InboundEmailService
 
-FLAG DESCRIPTIONS
-  --verbose  Show additional information about the CLI.
+    Template to use for file creation.
 
-    Additionally shows the architecture, node version, operating system, and versions of plugins that the CLI is using.
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [@oclif/plugin-version](https://github.com/oclif/plugin-version/blob/2.2.36/src/commands/version.ts)_
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/apex/class.ts)_
 
-## `sf visualforce generate component`
+## `sf template generate apex trigger`
 
-Generate a Visualforce Component.
+Generate an Apex trigger.
 
 ```
 USAGE
-  $ sf visualforce generate component -n <value> -l <value> [--json] [--flags-dir <value>] [-t DefaultVFComponent] [-d <value>]
-    [--api-version <value>]
+  $ sf template generate apex trigger -n <value> [--json] [--flags-dir <value>] [-t ApexTrigger] [-d <value>] [--api-version
+    <value>] [-s <value>] [-e before insert|before update|before delete|after insert|after update|after delete|after
+    undelete...]
 
 FLAGS
   -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -l, --label=<value>        (required) Visualforce Component label.
-  -n, --name=<value>         (required) Name of the generated Visualforce Component.
-  -t, --template=<option>    [default: DefaultVFComponent] Template to use for file creation.
-                             <options: DefaultVFComponent>
+  -e, --event=<option>...    [default: before insert] Events that fire the trigger.
+                             <options: before insert|before update|before delete|after insert|after update|after
+                             delete|after undelete>
+  -n, --name=<value>         (required) Name of the generated Apex trigger
+  -s, --sobject=<value>      [default: SOBJECT] Salesforce object to generate a trigger on.
+  -t, --template=<option>    [default: ApexTrigger] Template to use for file creation.
+                             <options: ApexTrigger>
       --api-version=<value>  Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
@@ -10115,22 +9749,32 @@ GLOBAL FLAGS
   --json               Format output as json.
 
 DESCRIPTION
-  Generate a Visualforce Component.
+  Generate an Apex trigger.
 
-  The command generates the .Component file and associated metadata file in the specified directory or the current
-  working directory by default.
+  Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent
+  directory called "triggers" in your package directory. Either run this command from an existing directory of this
+  name, or use the --output-dir flag to generate one or point to an existing one.
+
+  If you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with
+  the Salesforce object you want to generate a trigger for. If you don't specify --event, "before insert" is used.
 
 ALIASES
-  $ sf force visualforce component create
+  $ sf force apex trigger create
+  $ sf apex generate trigger
 
 EXAMPLES
-  Generate the metadata files for a Visualforce component in the current directory:
+  Generate two files associated with the MyTrigger Apex trigger (MyTrigger.trigger and MyTrigger.trigger-meta.xml) in
+  the current directory:
 
-    $ sf visualforce generate component --name mycomponent --label mylabel
+    $ sf template generate apex trigger --name MyTrigger
 
-  Similar to previous example, but generate the files in the directory "force-app/main/default/components":
+  Similar to the previous example, but generate the files in the "force-app/main/default/triggers" directory:
+
+    $ sf template generate apex trigger --name MyTrigger --output-dir force-app/main/default/triggers
 
-    $ sf visualforce generate component --name mycomponent --label mylabel --output-dir components
+  Generate files for a trigger that fires on the Account object before and after an insert:
+
+    $ sf template generate apex trigger --name MyTrigger --sobject Account --event "before insert,after insert"
 
 FLAG DESCRIPTIONS
   -d, --output-dir=<value>  Directory for saving the created files.
@@ -10138,66 +9782,695 @@ FLAG DESCRIPTIONS
     The location can be an absolute path or relative to the current working directory. The default is the current
     directory.
 
-  -n, --name=<value>  Name of the generated Visualforce Component.
+  -n, --name=<value>  Name of the generated Apex trigger
 
     The name can be up to 40 characters and must start with a letter.
 
-  -t, --template=DefaultVFComponent  Template to use for file creation.
+  -t, --template=ApexTrigger  Template to use for file creation.
 
     Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/visualforce/generate/component.ts)_
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/apex/trigger.ts)_
 
-## `sf visualforce generate page`
+## `sf template generate digital-experience site`
 
-Generate a Visualforce Page.
+Generate an Experience Cloud site.
 
 ```
 USAGE
-  $ sf visualforce generate page -n <value> -l <value> [--json] [--flags-dir <value>] [-d <value>] [--api-version
-  <value>]
+  $ sf template generate digital-experience site -n <value> -t BuildYourOwnLWR [--json] [--flags-dir <value>] [-o <value>] [-p <value>] [-e
+    <value>] [-d <value>]
 
 FLAGS
-  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
-  -l, --label=<value>        (required) Visualforce Page label.
-  -n, --name=<value>         (required) Name of the generated Visualforce Page.
-      --api-version=<value>  Override the api version used for api requests made by this command
+  -d, --output-dir=<value>       Directory to generate the site files in.
+  -e, --admin-email=<value>      Email address for the site administrator. Defaults to the username of the currently
+                                 authenticated user.
+  -n, --name=<value>             (required) Name of the Experience Cloud site to generate.
+  -o, --target-org=<value>       Username or alias of the target org.
+  -p, --url-path-prefix=<value>  URL path prefix for the site; must contain only alphanumeric characters.
+  -t, --template=<option>        (required) Template to use when generating the site.
+                                 <options: BuildYourOwnLWR>
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
   --json               Format output as json.
 
 DESCRIPTION
-  Generate a Visualforce Page.
-
-  The command generates the .Page file and associated metadata file in the specified directory or the current working
-  directory by default.
+  Generate an Experience Cloud site.
 
-ALIASES
-  $ sf force visualforce page create
+  Creates an Experience Cloud site with the specified template, name, and URL path prefix. The site includes all
+  necessary metadata files, including DigitalExperienceConfig, DigitalExperienceBundle, Network, and CustomSite.
 
 EXAMPLES
-  Generate the metadata files for a Visualforce page in the current directory:
+  Generate an Experience Cloud site using the BuildYourOwnLWR template. The site is called "mysite" and has the URL
+  path prefix "mysite":
 
-    $ sf visualforce generate page --name mypage --label mylabel
+    $ sf template generate digital-experience site --template BuildYourOwnLWR --name mysite --url-path-prefix mysite
 
-  Similar to previous example, but generate the files in the directory "force-app/main/default/pages":
+  Generate an Experience Cloud site like the last example, but generate the files into the specified output directory:
 
-    $ sf visualforce generate page --name mypage --label mylabel --output-dir pages
+    $ sf template generate digital-experience site --template BuildYourOwnLWR --name mysite --url-path-prefix mysite \
+      --output-dir force-app/main/default
 
 FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory for saving the created files.
+  -d, --output-dir=<value>  Directory to generate the site files in.
 
-    The location can be an absolute path or relative to the current working directory. The default is the current
-    directory.
+    The location can be an absolute path or relative to the current working directory. If not specified, the command
+    reads your sfdx-project.json file and uses the default package directory. When running outside a Salesforce DX
+    project, defaults to the current directory.
+```
 
-  -n, --name=<value>  Name of the generated Visualforce Page.
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/digital-experience/site.ts)_
+
+## `sf template generate lightning app`
+
+Generate a Lightning App.
 
-    The name can be up to 40 characters and must start with a letter.
 ```
+USAGE
+  $ sf template generate lightning app -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningApp] [-d <value>] [--api-version
+    <value>]
 
-_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.4.7/src/commands/visualforce/generate/page.ts)_
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning App.
+  -t, --template=<option>    [default: DefaultLightningApp] Template to use for file creation.
+                             <options: DefaultLightningApp>
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate a Lightning App.
+
+  Generates a Lightning App bundle in the specified directory or the current working directory. The bundle consists of
+  multiple files in a folder with the designated name.
+
+ALIASES
+  $ sf force lightning app create
+  $ sf lightning generate app
+
+EXAMPLES
+  Generate the metadata files for a Lightning app bundle called "myapp" in the current directory:
+
+    $ sf template generate lightning app --name myapp
+
+  Similar to the previous example, but generate the files in the "force-app/main/default/aura" directory:
+
+    $ sf template generate lightning app --name myapp --output-dir force-app/main/default/aura
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning App.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningApp  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/app.ts)_
+
+## `sf template generate lightning component`
+
+Generate a bundle for an Aura component or a Lightning web component.
+
+```
+USAGE
+  $ sf template generate lightning component -n <value> [--json] [--flags-dir <value>] [-t
+    default|analyticsDashboard|analyticsDashboardWithStep] [-d <value>] [--api-version <value>] [--type aura|lwc]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning Component.
+  -t, --template=<option>    [default: default] Template to use for file creation.
+                             <options: default|analyticsDashboard|analyticsDashboardWithStep>
+      --api-version=<value>  Override the api version used for api requests made by this command
+      --type=<option>        [default: aura] Type of the component bundle.
+                             <options: aura|lwc>
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate a bundle for an Aura component or a Lightning web component.
+
+  Generates the bundle in the specified directory or the current working directory. The bundle consists of multiple
+  files in a directory with the designated name. Lightning web components are contained in the directory with name
+  "lwc", Aura components in "aura".
+
+  To generate a Lightning web component, pass "--type lwc" to the command. If you don’t specify --type, Salesforce CLI
+  generates an Aura component by default.
+
+ALIASES
+  $ sf force lightning component create
+  $ sf lightning generate component
+
+EXAMPLES
+  Generate the metadata files for an Aura component bundle in the current directory:
+
+    $ sf template generate lightning component --name mycomponent
+
+  Generate a Lightning web component bundle in the current directory:
+
+    $ sf template generate lightning component --name mycomponent --type lwc
+
+  Generate an Aura component bundle in the "force-app/main/default/aura" directory:
+
+    $ sf template generate lightning component --name mycomponent --output-dir force-app/main/default/aura
+
+  Generate a Lightning web component bundle in the "force-app/main/default/lwc" directory:
+
+    $ sf template generate lightning component --name mycomponent --type lwc --output-dir force-app/main/default/lwc
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Component.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=default|analyticsDashboard|analyticsDashboardWithStep  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/component.ts)_
+
+## `sf template generate lightning event`
+
+Generate a Lightning Event.
+
+```
+USAGE
+  $ sf template generate lightning event -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningEvt] [-d <value>] [--api-version
+    <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning Event.
+  -t, --template=<option>    [default: DefaultLightningEvt] Template to use for file creation.
+                             <options: DefaultLightningEvt>
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate a Lightning Event.
+
+  Generates a Lightning Event bundle in the specified directory or the current working directory. The bundle consists of
+  multiple files in a folder with the designated name.
+
+ALIASES
+  $ sf force lightning event create
+  $ sf lightning generate event
+
+EXAMPLES
+  Generate the metadata files for a Lightning event bundle called "myevent" in the current directory:
+
+    $ sf template generate lightning event --name myevent
+
+  Similar to previous example, but generate the files in the "force-app/main/default/aura" directory:
+
+    $ sf template generate lightning event --name myevent --output-dir force-app/main/default/aura
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Event.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningEvt  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/event.ts)_
+
+## `sf template generate lightning interface`
+
+Generate a Lightning Interface.
+
+```
+USAGE
+  $ sf template generate lightning interface -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningIntf] [-d <value>]
+    [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning Interface.
+  -t, --template=<option>    [default: DefaultLightningIntf] Template to use for file creation.
+                             <options: DefaultLightningIntf>
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate a Lightning Interface.
+
+  Generates a Lightning Interface bundle in the specified directory or the current working directory. The bundle
+  consists of multiple files in a folder with the designated name.
+
+ALIASES
+  $ sf force lightning interface create
+  $ sf lightning generate interface
+
+EXAMPLES
+  Generate the metadata files for a Lightning interface bundle called "myinterface" in the current directory:
+
+    $ sf template generate lightning interface --name myinterface
+
+  Similar to the previous example but generate the files in the "force-app/main/default/aura" directory:
+
+    $ sf template generate lightning interface --name myinterface --output-dir force-app/main/default/aura
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Interface.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningIntf  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/interface.ts)_
+
+## `sf template generate lightning test`
+
+Generate a Lightning test.
+
+```
+USAGE
+  $ sf template generate lightning test -n <value> [--json] [--flags-dir <value>] [-t DefaultLightningTest] [-d <value>]
+    [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning Test.
+  -t, --template=<option>    [default: DefaultLightningTest] Template to use for file creation.
+                             <options: DefaultLightningTest>
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate a Lightning test.
+
+  Generates the test in the specified directory or the current working directory. The .resource file and associated
+  metadata file are generated.
+
+ALIASES
+  $ sf force lightning test create
+  $ sf lightning generate test
+
+EXAMPLES
+  Generate the metadata files for the Lightning test called MyLightningTest in the current directory:
+
+    $ sf template generate lightning test --name MyLightningTest
+
+  Similar to the previous example but generate the files in the "force-app/main/default/lightningTests" directory:
+
+    $ sf template generate lightning test --name MyLightningTest --output-dir force-app/main/default/lightningTests
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Test.
+
+    Name of the new Lightning test; can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningTest  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/lightning/test.ts)_
+
+## `sf template generate project`
+
+Generate a Salesforce DX project.
+
+```
+USAGE
+  $ sf template generate project -n <value> [--json] [--flags-dir <value>] [-t standard|empty|analytics] [-d <value>] [-s
+    <value>] [-p <value>] [-x] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>           [default: .] Directory for saving the created files.
+  -n, --name=<value>                 (required) Name of the generated project.
+  -p, --default-package-dir=<value>  [default: force-app] Default package directory name.
+  -s, --namespace=<value>            Namespace associated with this project and any connected scratch orgs.
+  -t, --template=<option>            [default: standard] Template to use for project creation.
+                                     <options: standard|empty|analytics>
+  -x, --manifest                     Generate a manifest (package.xml) for change-set based development.
+      --api-version=<value>          Will set this version as sourceApiVersion in the sfdx-project.json file
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate a Salesforce DX project.
+
+  A Salesforce DX project has a specific structure and a configuration file (sfdx-project.json) that identifies the
+  directory as a Salesforce DX project. This command generates the necessary configuration files and directories to get
+  you started.
+
+  By default, the generated sfdx-project.json file sets the sourceApiVersion property to the default API version
+  currently used by Salesforce CLI. To specify a different version, set the apiVersion configuration variable. For
+  example: "sf config set apiVersion=57.0 --global".
+
+ALIASES
+  $ sf force project create
+  $ sf project generate
+
+EXAMPLES
+  Generate a project called "mywork":
+
+    $ sf template generate project --name mywork
+
+  Similar to previous example, but generate the files in a directory called "myapp":
+
+    $ sf template generate project --name mywork --default-package-dir myapp
+
+  Similar to prevoius example, but also generate a default package.xml manifest file:
+
+    $ sf template generate project --name mywork --default-package-dir myapp --manifest
+
+  Generate a project with the minimum files and directories:
+
+    $ sf template generate project --name mywork --template empty
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated project.
+
+    Generates a project directory with this name; any valid directory name is accepted. Also sets the "name" property in
+    the sfdx-project.json file to this name.
+
+  -p, --default-package-dir=<value>  Default package directory name.
+
+    Metadata items such as classes and Lightning bundles are placed inside this folder.
+
+  -t, --template=standard|empty|analytics  Template to use for project creation.
+
+    The template determines the sample configuration files and directories that this command generates. For example, the
+    empty template provides these files and directory to get you started.
+
+    - .forceignore
+    - config/project-scratch-def.json
+    - sfdx-project.json
+    - package.json
+    - force-app (basic source directory structure)
+
+    The standard template provides a complete force-app directory structure so you know where to put your source. It
+    also provides additional files and scripts, especially useful when using Salesforce Extensions for VS Code. For
+    example:
+
+    - .gitignore: Use Git for version control.
+    - .prettierrc and .prettierignore: Use Prettier to format your Aura components.
+    - .vscode/extensions.json: When launched, Visual Studio Code, prompts you to install the recommended extensions for
+    your project.
+    - .vscode/launch.json: Configures Replay Debugger.
+    - .vscode/settings.json: Additional configuration settings.
+
+    The analytics template provides similar files and the force-app/main/default/waveTemplates directory.
+
+  -x, --manifest  Generate a manifest (package.xml) for change-set based development.
+
+    Generates a default manifest (package.xml) for fetching Apex, Visualforce, Lightning components, and static
+    resources.
+
+  --api-version=<value>  Will set this version as sourceApiVersion in the sfdx-project.json file
+
+    Override the api version used for api requests made by this command
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/project/index.ts)_
+
+## `sf template generate static-resource`
+
+Generate a static resource.
+
+```
+USAGE
+  $ sf template generate static-resource -n <value> [--json] [--flags-dir <value>] [--type <value>] [-d <value>]
+  [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated static resource.
+      --api-version=<value>  Override the api version used for api requests made by this command
+      --type=<value>         [default: application/zip] Content type (mime type) of the generated static resource.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate a static resource.
+
+  Generates the metadata resource file in the specified directory or the current working directory. Static resource
+  files must be contained in a parent directory called "staticresources" in your package directory. Either run this
+  command from an existing directory of this name, or use the --output-dir flag to create one or point to an existing
+  one.
+
+ALIASES
+  $ sf force staticresource create
+  $ sf static-resource generate
+
+EXAMPLES
+  Generate the metadata file for a static resource called MyResource in the current directory:
+
+    $ sf template generate static-resource --name MyResource
+
+  Similar to previous example, but specifies a MIME type of application/json:
+
+    $ sf template generate static-resource --name MyResource --type application/json
+
+  Generate the resource file in the "force-app/main/default/staticresources" directory:
+
+    $ sf template generate static-resource --name MyResource --output-dir force-app/main/default/staticresources
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated static resource.
+
+    This name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin
+    with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.
+
+  --type=<value>  Content type (mime type) of the generated static resource.
+
+    Must be a valid MIME type such as application/json, application/javascript, application/zip, text/plain, text/css,
+    etc.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/static-resource/index.ts)_
+
+## `sf template generate visualforce component`
+
+Generate a Visualforce Component.
+
+```
+USAGE
+  $ sf template generate visualforce component -n <value> -l <value> [--json] [--flags-dir <value>] [-t DefaultVFComponent] [-d <value>]
+    [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -l, --label=<value>        (required) Visualforce Component label.
+  -n, --name=<value>         (required) Name of the generated Visualforce Component.
+  -t, --template=<option>    [default: DefaultVFComponent] Template to use for file creation.
+                             <options: DefaultVFComponent>
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate a Visualforce Component.
+
+  The command generates the .Component file and associated metadata file in the specified directory or the current
+  working directory by default.
+
+ALIASES
+  $ sf force visualforce component create
+  $ sf visualforce generate component
+
+EXAMPLES
+  Generate the metadata files for a Visualforce component in the current directory:
+
+    $ sf template generate visualforce component --name mycomponent --label mylabel
+
+  Similar to previous example, but generate the files in the directory "force-app/main/default/components":
+
+    $ sf template generate visualforce component --name mycomponent --label mylabel --output-dir components
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Visualforce Component.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultVFComponent  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/visualforce/component.ts)_
+
+## `sf template generate visualforce page`
+
+Generate a Visualforce Page.
+
+```
+USAGE
+  $ sf template generate visualforce page -n <value> -l <value> [--json] [--flags-dir <value>] [-d <value>]
+  [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -l, --label=<value>        (required) Visualforce Page label.
+  -n, --name=<value>         (required) Name of the generated Visualforce Page.
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate a Visualforce Page.
+
+  The command generates the .Page file and associated metadata file in the specified directory or the current working
+  directory by default.
+
+ALIASES
+  $ sf force visualforce page create
+  $ sf visualforce generate page
+
+EXAMPLES
+  Generate the metadata files for a Visualforce page in the current directory:
+
+    $ sf template generate visualforce page --name mypage --label mylabel
+
+  Similar to previous example, but generate the files in the directory "force-app/main/default/pages":
+
+    $ sf template generate visualforce page --name mypage --label mylabel --output-dir pages
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Visualforce Page.
+
+    The name can be up to 40 characters and must start with a letter.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/56.7.0/src/commands/template/generate/visualforce/page.ts)_
+
+## `sf update [CHANNEL]`
+
+update the sf CLI
+
+```
+USAGE
+  $ sf update [CHANNEL] [--force |  | [-a | -v <value> | -i]] [-b ]
+
+FLAGS
+  -a, --available        See available versions.
+  -b, --verbose          Show more details about the available versions.
+  -i, --interactive      Interactively select version to install. This is ignored if a channel is provided.
+  -v, --version=<value>  Install a specific version.
+      --force            Force a re-download of the requested version.
+
+DESCRIPTION
+  update the sf CLI
+
+EXAMPLES
+  Update to the stable channel:
+
+    $ sf update stable
+
+  Update to a specific version:
+
+    $ sf update --version 1.0.0
+
+  Interactively select version:
+
+    $ sf update --interactive
+
+  See available versions:
+
+    $ sf update --available
+```
+
+_See code: [@oclif/plugin-update](https://github.com/oclif/plugin-update/blob/4.7.19/src/commands/update.ts)_
+
+## `sf version`
+
+```
+USAGE
+  $ sf version [--json] [--verbose]
+
+FLAGS
+  --verbose  Show additional information about the CLI.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+FLAG DESCRIPTIONS
+  --verbose  Show additional information about the CLI.
+
+    Additionally shows the architecture, node version, operating system, and versions of plugins that the CLI is using.
+```
+
+_See code: [@oclif/plugin-version](https://github.com/oclif/plugin-version/blob/2.2.36/src/commands/version.ts)_
 
 ## `sf which`
 
diff --git a/package.json b/package.json
index 2b33159e..086e1e93 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "2.123.0",
+  "version": "2.123.1",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run.js",
@@ -149,32 +149,32 @@
     "@oclif/plugin-commands": "4.1.40",
     "@oclif/plugin-help": "6.2.37",
     "@oclif/plugin-not-found": "3.2.74",
-    "@oclif/plugin-plugins": "5.4.55",
-    "@oclif/plugin-search": "1.2.37",
-    "@oclif/plugin-update": "4.7.18",
+    "@oclif/plugin-plugins": "5.4.56",
+    "@oclif/plugin-search": "1.2.38",
+    "@oclif/plugin-update": "4.7.19",
     "@oclif/plugin-version": "2.2.36",
     "@oclif/plugin-warn-if-update-available": "3.1.55",
     "@oclif/plugin-which": "3.2.43",
     "@salesforce/core": "^8.25.0",
     "@salesforce/kit": "^3.1.6",
-    "@salesforce/plugin-agent": "1.27.5",
-    "@salesforce/plugin-apex": "3.9.5",
-    "@salesforce/plugin-api": "1.3.8",
-    "@salesforce/plugin-auth": "4.1.4",
-    "@salesforce/plugin-data": "4.0.67",
-    "@salesforce/plugin-deploy-retrieve": "3.24.7",
-    "@salesforce/plugin-info": "3.4.100",
-    "@salesforce/plugin-limits": "3.3.74",
-    "@salesforce/plugin-marketplace": "1.3.8",
-    "@salesforce/plugin-org": "5.9.64",
-    "@salesforce/plugin-packaging": "2.24.11",
-    "@salesforce/plugin-schema": "3.3.90",
-    "@salesforce/plugin-settings": "2.4.54",
+    "@salesforce/plugin-agent": "1.29.0",
+    "@salesforce/plugin-apex": "3.9.6",
+    "@salesforce/plugin-api": "1.3.9",
+    "@salesforce/plugin-auth": "4.1.5",
+    "@salesforce/plugin-data": "4.0.68",
+    "@salesforce/plugin-deploy-retrieve": "3.24.8",
+    "@salesforce/plugin-info": "3.4.101",
+    "@salesforce/plugin-limits": "3.3.75",
+    "@salesforce/plugin-marketplace": "1.3.10",
+    "@salesforce/plugin-org": "5.9.66",
+    "@salesforce/plugin-packaging": "2.25.1",
+    "@salesforce/plugin-schema": "3.3.91",
+    "@salesforce/plugin-settings": "2.4.55",
     "@salesforce/plugin-sobject": "1.4.82",
-    "@salesforce/plugin-telemetry": "3.6.71",
-    "@salesforce/plugin-templates": "56.4.7",
+    "@salesforce/plugin-telemetry": "3.7.2",
+    "@salesforce/plugin-templates": "56.7.0",
     "@salesforce/plugin-trust": "3.7.113",
-    "@salesforce/plugin-user": "3.6.48",
+    "@salesforce/plugin-user": "3.6.49",
     "@salesforce/sf-plugins-core": "12.2.6",
     "ansis": "^3.12.0"
   },
diff --git a/yarn.lock b/yarn.lock
index 9079a8e9..946b9f68 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -1705,10 +1705,10 @@
     wordwrap "^1.0.0"
     wrap-ansi "^7.0.0"
 
-"@oclif/multi-stage-output@^0.8.28", "@oclif/multi-stage-output@^0.8.29":
-  version "0.8.29"
-  resolved "https://registry.yarnpkg.com/@oclif/multi-stage-output/-/multi-stage-output-0.8.29.tgz#eae75f72cc6f5f5b868ee2f1d6866385fec31ea7"
-  integrity sha512-P5Kuc9KpPRAJeofFYt7RO4TH/IVoaNKgQvKhRtDUMCH0+n5Fa0L5xUCqotIWu7UehmXxhFogQRbWI2yAEY/UiQ==
+"@oclif/multi-stage-output@^0.8.28", "@oclif/multi-stage-output@^0.8.29", "@oclif/multi-stage-output@^0.8.30":
+  version "0.8.30"
+  resolved "https://registry.yarnpkg.com/@oclif/multi-stage-output/-/multi-stage-output-0.8.30.tgz#c95261d669bc466ce06701e26248f49282034a12"
+  integrity sha512-WNEqTdK9GsZGc/yOgm/2drpdTXp7FGDxH3nbWSpMJBJU5CqrWmvoqNqrXZmlVRQHjKCo8qW3hI9FXse5brFVNg==
   dependencies:
     "@oclif/core" "^4"
     "@types/react" "^18.3.12"
@@ -1770,10 +1770,10 @@
     ansis "^3.17.0"
     fast-levenshtein "^3.0.0"
 
-"@oclif/plugin-plugins@5.4.55":
-  version "5.4.55"
-  resolved "https://registry.yarnpkg.com/@oclif/plugin-plugins/-/plugin-plugins-5.4.55.tgz#0c330ca6fd47a48aa0e457d3ddad61c11d921150"
-  integrity sha512-Dmcryvss0CJwaGSVimhIcnWfQto1rAMA5nMN6v6syrOhR76ygw2X7YWvkI6PXCFB/aekT2LJeQHy9Hl/OQJiYQ==
+"@oclif/plugin-plugins@5.4.56":
+  version "5.4.56"
+  resolved "https://registry.yarnpkg.com/@oclif/plugin-plugins/-/plugin-plugins-5.4.56.tgz#3e7c8d964f011ac4f891d5178a13aa356752902c"
+  integrity sha512-mZjRudlmVSr6Stz0CVFuaIZOjwZ5DqjWepQCR/yK9nbs8YunGautpuxBx/CcqaEH29xiQfsuNOIUWa1w/+3VSA==
   dependencies:
     "@oclif/core" "^4.8.0"
     ansis "^3.17.0"
@@ -1782,24 +1782,24 @@
     npm-package-arg "^11.0.3"
     npm-run-path "^5.3.0"
     object-treeify "^4.0.1"
-    semver "^7.7.3"
+    semver "^7.7.4"
     validate-npm-package-name "^5.0.1"
     which "^4.0.0"
     yarn "^1.22.22"
 
-"@oclif/plugin-search@1.2.37":
-  version "1.2.37"
-  resolved "https://registry.yarnpkg.com/@oclif/plugin-search/-/plugin-search-1.2.37.tgz#7c05a226fcd21a60a9f89a0c57720be8dfd6ee3d"
-  integrity sha512-/ELl28Dl7rlOHRqta4BKafahUZmLm9tjBP26nNMPK1S5Ce/OZ4nUtLSHR9CpWCLRadNmCSsaF+SlBPoCUbPrZw==
+"@oclif/plugin-search@1.2.38":
+  version "1.2.38"
+  resolved "https://registry.yarnpkg.com/@oclif/plugin-search/-/plugin-search-1.2.38.tgz#c0f9fe46ed5470cc7f477f1e9fdda3a7b649a67e"
+  integrity sha512-Hsp74C4bpR3hfFHB5mywF+2DcjsnOtUK3+CpeYP5EMPsgSj4gpHLZPt7DUcRHiWkbdntz/YLiCihyMrsDR1FHQ==
   dependencies:
     "@oclif/core" "^4"
-    ansi-escapes "^7.2.0"
+    ansi-escapes "^7.3.0"
     inquirer-autocomplete-standalone "^0.8.1"
 
-"@oclif/plugin-update@4.7.18":
-  version "4.7.18"
-  resolved "https://registry.yarnpkg.com/@oclif/plugin-update/-/plugin-update-4.7.18.tgz#b1b3862327e358a56768b6f4a5f424a266792fd7"
-  integrity sha512-2XxWBBhrk7qKz2nAC2QjNOz8UoTmNJITrnn6hQ8Lntr6wfDXsAGOYakZ6j6DoRIHbcUcRM4CYUsvewMp0MUG6Q==
+"@oclif/plugin-update@4.7.19":
+  version "4.7.19"
+  resolved "https://registry.yarnpkg.com/@oclif/plugin-update/-/plugin-update-4.7.19.tgz#1f53939355b505e9614c398c20231fda8ece4008"
+  integrity sha512-UZOMrgOq4N/UrM6Hh4w9U7ZIgyrUhzXDOAHGL6tTtLkOTeo9eVqXeqR30pKXW9OOfcH6BXihwQB5G4ejteLBpw==
   dependencies:
     "@inquirer/select" "^2.5.0"
     "@oclif/core" "^4"
@@ -1809,7 +1809,7 @@
     filesize "^6.1.0"
     got "^13"
     proxy-agent "^6.5.0"
-    semver "^7.7.3"
+    semver "^7.7.4"
     tar-fs "^2.1.4"
 
 "@oclif/plugin-version@2.2.36":
@@ -2067,16 +2067,16 @@
   resolved "https://registry.yarnpkg.com/@protobufjs/utf8/-/utf8-1.1.0.tgz#a777360b5b39a1a2e5106f8e858f2fd2d060c570"
   integrity sha512-Vvn3zZrhQZkkBE8LSuW3em98c0FwgO4nxzv6OdSxPKJIEKY2bGbHn+mhGIPerzI4twdxaP8/0+06HBpwf345Lw==
 
-"@salesforce/agents@^0.22.1":
-  version "0.22.2"
-  resolved "https://registry.yarnpkg.com/@salesforce/agents/-/agents-0.22.2.tgz#b9c6612040938c37cfa85f250cb6ee5a0a055135"
-  integrity sha512-TF/hvrM2wv3rSLWkBbLCjBGax6y5EaO5t6cevM+i/VMX140M+ls63O/8AaoXAwjNo3udorNUhm0wbs1HE3QfRw==
+"@salesforce/agents@^0.22.6":
+  version "0.22.6"
+  resolved "https://registry.yarnpkg.com/@salesforce/agents/-/agents-0.22.6.tgz#35ea2ec80b3da6489b6ff18c63a9a7c4f2ca6e96"
+  integrity sha512-FOJFNVPsJeDEZ9TBk1YL0O0iwovDhXCdk+gw0+Ow1XB2h0eAY4FFOWWzexTXnYKflsVVvA+1lgEeFQS4bwgJSw==
   dependencies:
-    "@salesforce/core" "^8.24.0"
+    "@salesforce/core" "^8.25.1"
     "@salesforce/kit" "^3.2.4"
-    "@salesforce/source-deploy-retrieve" "^12.31.6"
-    "@salesforce/types" "^1.5.0"
-    fast-xml-parser "^5.3.4"
+    "@salesforce/source-deploy-retrieve" "^12.31.10"
+    "@salesforce/types" "^1.6.0"
+    fast-xml-parser "^5.3.5"
     nock "^13.5.6"
     yaml "^2.8.2"
 
@@ -2111,10 +2111,10 @@
     strip-ansi "6.0.1"
     ts-retry-promise "^0.8.1"
 
-"@salesforce/core@^8.18.1", "@salesforce/core@^8.18.7", "@salesforce/core@^8.23.5", "@salesforce/core@^8.24.0", "@salesforce/core@^8.24.3", "@salesforce/core@^8.25.0", "@salesforce/core@^8.5.1", "@salesforce/core@^8.8.0", "@salesforce/core@^8.8.1", "@salesforce/core@^8.8.5":
-  version "8.25.0"
-  resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-8.25.0.tgz#2cf53f38aee8fb6ea1b0e6b6e301b66bc0d81d1c"
-  integrity sha512-LdUDEK8mmiWpnKn6wtaSDcvZc2Svrg/xldint1OGyVhCGZUAQLjCWRKkBT5DdIVV3g9QrDNhLboi904jcwDe1g==
+"@salesforce/core@^8.18.1", "@salesforce/core@^8.18.7", "@salesforce/core@^8.23.5", "@salesforce/core@^8.24.0", "@salesforce/core@^8.25.0", "@salesforce/core@^8.25.1", "@salesforce/core@^8.5.1", "@salesforce/core@^8.8.0", "@salesforce/core@^8.8.1", "@salesforce/core@^8.8.5":
+  version "8.25.1"
+  resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-8.25.1.tgz#7646025598bb59b6f95b3656baf8eb0b63a43052"
+  integrity sha512-Jon0a9uZpp+mNa5PiY+y8dTjaPcsMaxXEkswdzWotrdrZ4g84MmPKSEv+Q/LtXw3uc9i4RmqBJBUXSIvZhgrjg==
   dependencies:
     "@jsforce/jsforce-node" "^3.10.13"
     "@salesforce/kit" "^3.2.4"
@@ -2180,10 +2180,10 @@
   dependencies:
     "@salesforce/ts-types" "^2.0.12"
 
-"@salesforce/o11y-reporter@1.6.0":
-  version "1.6.0"
-  resolved "https://registry.yarnpkg.com/@salesforce/o11y-reporter/-/o11y-reporter-1.6.0.tgz#b2c5e538d64337c44b69ce5ec8b43c55d6c409eb"
-  integrity sha512-FAdmfTtRlpuCwXSwPFrpp+mYn8h47EUAaHKL1PpVZYU+DoktVXrDoKTm3MxKRarcqtK1fc4PaO3UOcL5tIT1iA==
+"@salesforce/o11y-reporter@1.7.3":
+  version "1.7.3"
+  resolved "https://registry.yarnpkg.com/@salesforce/o11y-reporter/-/o11y-reporter-1.7.3.tgz#14e58bc511fa3529077eff7e6712182574c52a1c"
+  integrity sha512-Krd2EgHYrTW1j1Wo5q+4kya6F7WjGvJsD4oUKzefLRw92Pb5b7aMorLFsKMEvLTZSGmTZZClLmQMap0gLOV6qw==
   dependencies:
     o11y "^258.7.0"
     o11y_schema "256.154.0"
@@ -2208,21 +2208,21 @@
     jszip "^3.10.1"
     object-treeify "^2"
 
-"@salesforce/plugin-agent@1.27.5":
-  version "1.27.5"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-agent/-/plugin-agent-1.27.5.tgz#bfbd232f75a02931755ee15b629e0a5ea3975072"
-  integrity sha512-20Yaz+pbcMufQ7xGauWP9M+dn9XBkAHUfx/kRRLEOf+3mOwEkSUIOQ1nfuxOiYqSR9bNB2LPGIJ4l54ADGA4mQ==
+"@salesforce/plugin-agent@1.29.0":
+  version "1.29.0"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-agent/-/plugin-agent-1.29.0.tgz#a0c493372a00ce9c2ec6f3e126d8f0bf7f9816c7"
+  integrity sha512-F0VTYHOn8tD1LsPUsFJbuI0vtBR/DgZM/qGLs1f+GCAURZczWZ3b08Dmf+dHE4xtYW9x7on7Tvz5V8dDtpb4Qg==
   dependencies:
     "@inquirer/core" "^10.3.2"
     "@inquirer/prompts" "^7.10.1"
     "@oclif/core" "^4"
     "@oclif/multi-stage-output" "^0.8.29"
-    "@salesforce/agents" "^0.22.1"
-    "@salesforce/core" "^8.24.3"
+    "@salesforce/agents" "^0.22.6"
+    "@salesforce/core" "^8.25.1"
     "@salesforce/kit" "^3.2.4"
     "@salesforce/sf-plugins-core" "^12.2.6"
     "@salesforce/source-deploy-retrieve" "^12.31.10"
-    "@salesforce/types" "^1.5.0"
+    "@salesforce/types" "^1.6.0"
     ansis "^3.3.2"
     fast-xml-parser "^5.3.4"
     glob "^11.0.3"
@@ -2232,10 +2232,10 @@
     react "^18.3.1"
     yaml "^2.8.2"
 
-"@salesforce/plugin-apex@3.9.5":
-  version "3.9.5"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-apex/-/plugin-apex-3.9.5.tgz#f68766a89c758996355221ff0176a577e0fd3381"
-  integrity sha512-mC+hqCHba7FDMx8G9GKYbnqF0xcKYs4XQdka4cwMPXfUEW6WLyDexi7jz670AUYQ3ee91tat9oBDLU8PE9jC4Q==
+"@salesforce/plugin-apex@3.9.6":
+  version "3.9.6"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-apex/-/plugin-apex-3.9.6.tgz#51a96a6394130325b1b6011cd5704d01ba95bf13"
+  integrity sha512-pnuZKQpIrygU5bcj3LiU++SBCmYKzVdzskQdPF366f+zZqGGQI0Xwi8OEpke/tRDwrObk4OlO5+g/5jm2INDgQ==
   dependencies:
     "@salesforce/apex-node" "^8.4.2"
     "@salesforce/core" "^8.24.0"
@@ -2243,10 +2243,10 @@
     "@salesforce/sf-plugins-core" "^12.2.6"
     ansis "^3.3.1"
 
-"@salesforce/plugin-api@1.3.8":
-  version "1.3.8"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-api/-/plugin-api-1.3.8.tgz#497d4f4c28fc7f127b03481abe6d7d65c4a93c22"
-  integrity sha512-yXqXmoXmbyALzVbGZ/b98yEAbgcZE1YoEfEWn/VRmul9W7/ZLCtBd5AKia5AAEWT1ilOf6P3pj83D8TlrcGk2Q==
+"@salesforce/plugin-api@1.3.9":
+  version "1.3.9"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-api/-/plugin-api-1.3.9.tgz#97da29e20bed2e28bdd17c56a39ccc70fd7b5819"
+  integrity sha512-KCWhOsyd/CgiFVPPdrpI9n4cKdSYhXqgGtZP0p9n/4C1elTr3dfaO1EqIr6iDKhv5FWjTdM6GBtZAaCX06KqvQ==
   dependencies:
     "@oclif/core" "^4"
     "@salesforce/core" "^8.8.1"
@@ -2258,15 +2258,15 @@
     got "^13.0.0"
     proxy-agent "^6.4.0"
 
-"@salesforce/plugin-auth@4.1.4":
-  version "4.1.4"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-auth/-/plugin-auth-4.1.4.tgz#e1b649d0439b41bc56c5497b79516a9da3708e8c"
-  integrity sha512-Ili0F+oKIpxmxBq1fG+A7Fh/DUs2ES4wVyrwna7Kw5Virm6CqE1qq0kAqrmtqITmEpLS1LWhPT+mZ2n8Krxj0w==
+"@salesforce/plugin-auth@4.1.5":
+  version "4.1.5"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-auth/-/plugin-auth-4.1.5.tgz#4a742783d3e98b1b5ae0d5a90b98beea6a3a6e5f"
+  integrity sha512-LZgALVC7L+b7/2DNAJCp3EEUrjHQwUmMTlSmL4CKvIb12OvnUT6YdWv/rNs6c1oJE+ZTkOcJPC8l4Q4gc9l+BQ==
   dependencies:
     "@inquirer/checkbox" "^2.5.0"
     "@inquirer/select" "^2.5.0"
     "@oclif/core" "^4"
-    "@salesforce/core" "^8.25.0"
+    "@salesforce/core" "^8.25.1"
     "@salesforce/kit" "^3.2.4"
     "@salesforce/plugin-info" "^3.4.100"
     "@salesforce/sf-plugins-core" "^12.2.6"
@@ -2287,10 +2287,10 @@
     debug "^4.4.0"
     handlebars "^4.7.8"
 
-"@salesforce/plugin-data@4.0.67":
-  version "4.0.67"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-data/-/plugin-data-4.0.67.tgz#5c291ca6b0c5985c642d85d3b410066fc1c809b5"
-  integrity sha512-wVIQseHwfSyrSGzQn6Gsbv1grO6RkYAukwPikjiTgXvxDZcmZd7rQjP/kUKukHMAbcpfc1tcNDxrb6nIwvGN4A==
+"@salesforce/plugin-data@4.0.68":
+  version "4.0.68"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-data/-/plugin-data-4.0.68.tgz#32917f7b74aab690c3c182fff1ca4407a508f7e1"
+  integrity sha512-eGXkdwKymmbw9+Fpt42vhvMxIRNUWGDjsFij3hAzPVbGpol3XOs6PrbH/tgZkRDF9ehnwC1LRflnITEf5R8cFw==
   dependencies:
     "@jsforce/jsforce-node" "^3.10.8"
     "@oclif/multi-stage-output" "^0.8.29"
@@ -2306,29 +2306,29 @@
     terminal-link "^3.0.0"
     zod "^4.2.1"
 
-"@salesforce/plugin-deploy-retrieve@3.24.7":
-  version "3.24.7"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-3.24.7.tgz#c8dde84b06a5496c003b17887dc53571cf9db14b"
-  integrity sha512-zecaF9d4o5U/bdrGhKHdiDcZfS6B0/t4gkyU5NE8r1EAP+wnXEjL/js6XNvA/Cw68p0qlBvO9fOSdejyFgYoQA==
+"@salesforce/plugin-deploy-retrieve@3.24.8":
+  version "3.24.8"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-3.24.8.tgz#4515ab17987982dd7fa28fa8ef40bc580537f97e"
+  integrity sha512-RY6OhYmNCVWw8+d1o4l+zGZf8iUb3dZMbp32u5sIvZMeXR3YrZGclM3GmfTDCYuEtdZIx5TUIYV6/k7FbmG/cw==
   dependencies:
     "@inquirer/prompts" "^7.8.3"
     "@oclif/core" "^4.8.0"
     "@oclif/multi-stage-output" "^0.8.28"
     "@salesforce/apex-node" "^8.3.5"
-    "@salesforce/core" "^8.24.0"
+    "@salesforce/core" "^8.25.1"
     "@salesforce/kit" "^3.2.4"
     "@salesforce/plugin-info" "^3.4.93"
     "@salesforce/sf-plugins-core" "^12.2.5"
-    "@salesforce/source-deploy-retrieve" "^12.31.3"
+    "@salesforce/source-deploy-retrieve" "^12.31.11"
     "@salesforce/source-tracking" "^7.8.0"
     "@salesforce/ts-types" "^2.0.12"
     ansis "^3.17.0"
     terminal-link "^3.0.0"
 
-"@salesforce/plugin-info@3.4.100", "@salesforce/plugin-info@^3.4.100", "@salesforce/plugin-info@^3.4.74", "@salesforce/plugin-info@^3.4.93":
-  version "3.4.100"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-info/-/plugin-info-3.4.100.tgz#8f3775c67e03b24b84ece332b80c155648d28211"
-  integrity sha512-dGY8TPPTDgzisMl1sdCk3mc6HpmyI/OlKD/4zxrXvMKncRGO3wOcw95fBhHy4dW9SDMoXK60i+1TibnOBlbZdA==
+"@salesforce/plugin-info@3.4.101", "@salesforce/plugin-info@^3.4.100", "@salesforce/plugin-info@^3.4.74", "@salesforce/plugin-info@^3.4.93":
+  version "3.4.101"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-info/-/plugin-info-3.4.101.tgz#3551bcb5152cbdff8a002d64516b04029ea09fd2"
+  integrity sha512-Pfgr8aDYU0tpxNzM3Twem+oL5hhB7i2C9upjED2usgRB7wdjAWGB9JY7yi2ctVc1fkoN1Iu1RIj4aAjFuPdv2w==
   dependencies:
     "@inquirer/input" "^2.3.0"
     "@jsforce/jsforce-node" "^3.10.10"
@@ -2343,33 +2343,33 @@
     proxy-agent "^6.5.0"
     semver "^7.7.3"
 
-"@salesforce/plugin-limits@3.3.74":
-  version "3.3.74"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-limits/-/plugin-limits-3.3.74.tgz#c6d9ae617fb400427ac4e9dc98525ae242991087"
-  integrity sha512-5+lndVVnjdSP4RZe6dYAJ8TEDT6VMMmMXVIdlawWwwlxCuMbAMS0GtMWWPMWw3dn/5+oIl4WaJpsC6jRkUvZUQ==
+"@salesforce/plugin-limits@3.3.75":
+  version "3.3.75"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-limits/-/plugin-limits-3.3.75.tgz#dceb0988da0acdf36e9df5951b8eae34f10c74cb"
+  integrity sha512-pUVNP2u+DX8U+1UITr43mTwnfZ5yPmUSIAJhKqtk4P/RzARiyFJDhQwrjy3zEl39teq6jHzJL54EM4Roc9+/iQ==
   dependencies:
     "@salesforce/core" "^8.24.0"
     "@salesforce/sf-plugins-core" "^12.2.6"
 
-"@salesforce/plugin-marketplace@1.3.8":
-  version "1.3.8"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-marketplace/-/plugin-marketplace-1.3.8.tgz#dd38c550c2b857ca6a775713aacbebaf66e63976"
-  integrity sha512-6sLIKj1NqN9cm04bzVnSldcKCTaKiUo+olyc1vrqWcQQ8CqXxJAJXnoRrSApwfSFtSBYUxYMvsxBiv7rEceKsg==
+"@salesforce/plugin-marketplace@1.3.10":
+  version "1.3.10"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-marketplace/-/plugin-marketplace-1.3.10.tgz#3b9f590cf2c6dc96c26284cd0039d796314d1aa9"
+  integrity sha512-NRUmchR/8LrFv4rxC2eBLwabAITHWJoI6If+pQFMvhcrfeBaOxHSTV4TdPtj7VysnCFkL+MtMFCPNb6KrvqtPQ==
   dependencies:
-    "@salesforce/core" "^8.8.0"
-    "@salesforce/kit" "^3.2.1"
-    "@salesforce/sf-plugins-core" "^12.0.13"
+    "@salesforce/core" "^8.25.1"
+    "@salesforce/kit" "^3.2.4"
+    "@salesforce/sf-plugins-core" "^12.2.6"
     got "^13.0.0"
-    proxy-agent "^6.4.0"
+    proxy-agent "^6.5.0"
 
-"@salesforce/plugin-org@5.9.64":
-  version "5.9.64"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-org/-/plugin-org-5.9.64.tgz#24a113156e8ae2293edb0901a4b10016d664f7aa"
-  integrity sha512-4Z+l5LoewN1uK4/egOzis3a0oPPmTpmELG5s24ZuJTSdmVNU6BmBl+wo6ULigOzz6P932i2vYHyp8HDitU0yqA==
+"@salesforce/plugin-org@5.9.66":
+  version "5.9.66"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-org/-/plugin-org-5.9.66.tgz#9e3b28834fe69a9d28fd049a20bed3177f166e74"
+  integrity sha512-gSl2EhlOQaRzRaWRJ6zb94f2vKcKAg6A0WJBKTfF2krOE38homKYPF6PJc/E2Aw9NcBGW0ABhRoz0O6K0K6Ugg==
   dependencies:
     "@oclif/core" "^4.5.6"
-    "@oclif/multi-stage-output" "^0.8.29"
-    "@salesforce/core" "^8.25.0"
+    "@oclif/multi-stage-output" "^0.8.30"
+    "@salesforce/core" "^8.25.1"
     "@salesforce/kit" "^3.2.4"
     "@salesforce/sf-plugins-core" "^12.2.6"
     "@salesforce/source-deploy-retrieve" "^12.31.10"
@@ -2380,13 +2380,13 @@
     open "^10.2.0"
     terminal-link "^3.0.0"
 
-"@salesforce/plugin-packaging@2.24.11":
-  version "2.24.11"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-packaging/-/plugin-packaging-2.24.11.tgz#c0efee7ad0ed5edad0b9352ea1b9b8c60ed63fae"
-  integrity sha512-xRzQO4cwndmh7T2jVNku2uKOILEL9u6ZbsyKzxnIX3Vr9H9FAdFo+oGpHscb2ZcYwc67JyxFLfnctCeByOLJ0A==
+"@salesforce/plugin-packaging@2.25.1":
+  version "2.25.1"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-packaging/-/plugin-packaging-2.25.1.tgz#c10ac6435e6a6d0a8420fe0cfc512749f8eb664f"
+  integrity sha512-wmrFkzW5Ysj9F/Y/zMK/0gHgZ7+idy0jOl7JLlWR7E6eTur/PegCpI5kUj5cy1ncGqpRX1ORMS4cVSVkauJ/0w==
   dependencies:
     "@oclif/core" "^4"
-    "@salesforce/core" "^8.25.0"
+    "@salesforce/core" "^8.25.1"
     "@salesforce/kit" "^3.2.4"
     "@salesforce/packaging" "^4.20.1"
     "@salesforce/sf-plugins-core" "^12.2.6"
@@ -2420,19 +2420,19 @@
     strip-ansi "^6"
     yarn-deduplicate "^6.0.2"
 
-"@salesforce/plugin-schema@3.3.90":
-  version "3.3.90"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-schema/-/plugin-schema-3.3.90.tgz#196f304f29442bd31c083613fe3c2c6026ca8fdc"
-  integrity sha512-/ihjzWA1f+KZ7xlvfzKndTO9i1/ucWVmKdT3weTfAHTjweVF9i5QK9YMFZCqlND8Q+t+e8qTTFALQS612eUIhA==
+"@salesforce/plugin-schema@3.3.91":
+  version "3.3.91"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-schema/-/plugin-schema-3.3.91.tgz#ca99ca3dcc95bf2ca95033553e938493ae15fdd3"
+  integrity sha512-lHE8Q7UG7sN0FePQpIIUR2snKQnNU5EfEr8fCSB55msUHHf79qlRjFi8pVQ3M+Br4j4aRElwv42lUYlRiJsekg==
   dependencies:
     "@oclif/core" "^4"
     "@salesforce/core" "^8.24.0"
     "@salesforce/sf-plugins-core" "^11.3.12"
 
-"@salesforce/plugin-settings@2.4.54":
-  version "2.4.54"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-settings/-/plugin-settings-2.4.54.tgz#379565e090d15efc8af16d78ebbf5fed6b2e6d5a"
-  integrity sha512-DstYBUyBddd1/FYNEh1vG8S6luoD6gInoeo1Zkc8DEDI4BXJb5mObXrEkIPslQzbL1WFBaj/NDBPYRFQ8VE09g==
+"@salesforce/plugin-settings@2.4.55":
+  version "2.4.55"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-settings/-/plugin-settings-2.4.55.tgz#218ca4267bad434e277ff3441ec82d32369e3077"
+  integrity sha512-JA8sjT/U/LlXC6Cg/S+NlSx2PzICG7EFmQmbgZvL5kybTVqPgLNduNoY99DefkdMbE6wQ93JsscCNNfO+lzH9A==
   dependencies:
     "@oclif/core" "^4"
     "@salesforce/core" "^8.24.0"
@@ -2455,27 +2455,27 @@
     fast-xml-parser "^5.3.4"
     js2xmlparser "^4.0.2"
 
-"@salesforce/plugin-telemetry@3.6.71":
-  version "3.6.71"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-telemetry/-/plugin-telemetry-3.6.71.tgz#ab6f84acf588331bb7ac8d5d7837824fc530a4ad"
-  integrity sha512-QaHesm9I19G7A2l18g8c3hmDGHtAb+Mg9W7GovRYR6aG9mXmOUQ5YKLT0WLXIZ0UMuj9CvUqQ4LNHupO4phhAQ==
+"@salesforce/plugin-telemetry@3.7.2":
+  version "3.7.2"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-telemetry/-/plugin-telemetry-3.7.2.tgz#ed84293ff992052aacede31c44e7045401505764"
+  integrity sha512-nfnYjeZecSUK5njxGRshrok6BdQgndxvWIaqW0uSf0ReVTFmeR8tFYmx8NtKyA3tnrXvYcuyUmTncBdVHR2yBQ==
   dependencies:
     "@oclif/core" "^4.8.0"
-    "@salesforce/core" "^8.24.0"
-    "@salesforce/kit" "^3.2.3"
+    "@salesforce/core" "^8.25.1"
+    "@salesforce/kit" "^3.2.4"
     "@salesforce/sf-plugins-core" "^12"
-    "@salesforce/telemetry" "^6.4.3"
-    "@salesforce/ts-types" "^2.0.11"
+    "@salesforce/telemetry" "^6.6.0"
+    "@salesforce/ts-types" "^2.0.12"
     debug "^4.4.3"
 
-"@salesforce/plugin-templates@56.4.7":
-  version "56.4.7"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-templates/-/plugin-templates-56.4.7.tgz#40c170a331544aa2c34e74a99580f8cb95a1a364"
-  integrity sha512-HHFydBGkHCo/0m0Qp1eUTrxQSCE4eQ4PgqkWcog+nQmHHdATdd8m1So2NHG8bjNKXLWYobjuMEXzLcmiw+MlJw==
+"@salesforce/plugin-templates@56.7.0":
+  version "56.7.0"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-templates/-/plugin-templates-56.7.0.tgz#ab1878cf35f026c35dd2f1f481d9de41cb8fa7f9"
+  integrity sha512-2nnG7TYuQ/HMwQ96CAICGNVCGA9cA0XoCmtogqozjdaKN8381YLty9NZXITE9jZvx/eDF/l4O/VwIPI+JDZXxg==
   dependencies:
-    "@salesforce/core" "^8.25.0"
+    "@salesforce/core" "^8.25.1"
     "@salesforce/sf-plugins-core" "^12"
-    "@salesforce/templates" "^65.4.3"
+    "@salesforce/templates" "^65.5.3"
 
 "@salesforce/plugin-trust@3.7.113", "@salesforce/plugin-trust@^3.7.69":
   version "3.7.113"
@@ -2494,12 +2494,12 @@
     semver "^7.7.2"
     shelljs "0.8.5"
 
-"@salesforce/plugin-user@3.6.48":
-  version "3.6.48"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-user/-/plugin-user-3.6.48.tgz#86d30f65361f0ffd7cb17ad7cc7713cc59afe523"
-  integrity sha512-GxEUSUlsMu09SDGT9zz74iLpjfxjGb9gUIBia1JkK5MJ4sf7Uxyg16nVM0vShzYvaAYnWsXAz8rIUuo8nqGSSQ==
+"@salesforce/plugin-user@3.6.49":
+  version "3.6.49"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-user/-/plugin-user-3.6.49.tgz#0613d574c3f82afa626e340519d33c7e7edd8047"
+  integrity sha512-NOROvlP0xsVLyUzaWGpDhW6ByUzi8FbFpJ/WhDWC5q4tha6QYv8MdSDSu8BW3hMgwQ7vmNRC8FL5XJvWwSlozQ==
   dependencies:
-    "@salesforce/core" "^8.25.0"
+    "@salesforce/core" "^8.25.1"
     "@salesforce/kit" "^3.2.4"
     "@salesforce/sf-plugins-core" "^12.2.6"
     "@salesforce/ts-types" "^2.0.11"
@@ -2514,7 +2514,7 @@
   resolved "https://registry.yarnpkg.com/@salesforce/schemas/-/schemas-1.10.3.tgz#52c867fdd60679cf216110aa49542b7ad391f5d1"
   integrity sha512-FKfvtrYTcvTXE9advzS25/DEY9yJhEyLvStm++eQFtnAaX1pe4G3oGHgiQ0q55BM5+0AlCh0+0CVtQv1t4oJRA==
 
-"@salesforce/sf-plugins-core@12.2.6", "@salesforce/sf-plugins-core@^12", "@salesforce/sf-plugins-core@^12.0.13", "@salesforce/sf-plugins-core@^12.2.0", "@salesforce/sf-plugins-core@^12.2.5", "@salesforce/sf-plugins-core@^12.2.6":
+"@salesforce/sf-plugins-core@12.2.6", "@salesforce/sf-plugins-core@^12", "@salesforce/sf-plugins-core@^12.2.0", "@salesforce/sf-plugins-core@^12.2.5", "@salesforce/sf-plugins-core@^12.2.6":
   version "12.2.6"
   resolved "https://registry.yarnpkg.com/@salesforce/sf-plugins-core/-/sf-plugins-core-12.2.6.tgz#856303e786f5fac1c6aa6dcd42f282cb1ac703e8"
   integrity sha512-EDKE72f/gGk9vL7KI9wsFO5wl/jFVvA2l5XBGR+6sJ1+FTMUbTGRMLObkkYJACk7bKvUFx00xdur2R6K8SWNvg==
@@ -2548,10 +2548,10 @@
     string-width "^7.2.0"
     terminal-link "^3.0.0"
 
-"@salesforce/source-deploy-retrieve@^12.30.0", "@salesforce/source-deploy-retrieve@^12.31.10", "@salesforce/source-deploy-retrieve@^12.31.3", "@salesforce/source-deploy-retrieve@^12.31.6", "@salesforce/source-deploy-retrieve@^12.31.9":
-  version "12.31.10"
-  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.31.10.tgz#612886356d81c87eb9053bbc9173546556fd5f36"
-  integrity sha512-kUdJicJUd3/lzNQOvDW1Sc5iBl8PVv2Tz7L59YA/Le0fzZCYM72oyKwdbl/f6kc+MzJpMVia2+AxrvVZir8oJw==
+"@salesforce/source-deploy-retrieve@^12.30.0", "@salesforce/source-deploy-retrieve@^12.31.10", "@salesforce/source-deploy-retrieve@^12.31.11", "@salesforce/source-deploy-retrieve@^12.31.9":
+  version "12.31.11"
+  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.31.11.tgz#58c51ebb54bd2fc2242c6374ce25fc3a3b71aea0"
+  integrity sha512-7LGWY4GsXl8iFz/ZvZrRdufnefQ5iezi0Pm1YQVRmJfqpBY/4kz/98gRW65h3XERASuuvAfVRLXfPVKtCHW4yA==
   dependencies:
     "@salesforce/core" "^8.24.0"
     "@salesforce/kit" "^3.2.4"
@@ -2582,30 +2582,33 @@
     isomorphic-git "^1.34.2"
     ts-retry-promise "^0.8.1"
 
-"@salesforce/telemetry@^6.4.3":
-  version "6.4.3"
-  resolved "https://registry.yarnpkg.com/@salesforce/telemetry/-/telemetry-6.4.3.tgz#593c844e992ac1684323a4f27a3e9712f35d5efc"
-  integrity sha512-O2/bkrBxpwm5xIKO6m9eP2N5gyCDj57J5pTmagWCMs3fwMurmi/rW3H8tlHnJBWU+iBDdPcxCY7L6QNrmupAPA==
+"@salesforce/telemetry@^6.6.0":
+  version "6.6.1"
+  resolved "https://registry.yarnpkg.com/@salesforce/telemetry/-/telemetry-6.6.1.tgz#e0f153022b4861d8590911c32350c0a201973e4e"
+  integrity sha512-7zWvGM3lco9d74Uv9K8ftzfrJlhAHbkrbsvRTjEQ7sUzfVKapxtEE17VQkbViXAK/2UU2kV8txVOgwCWUJZHzA==
   dependencies:
-    "@salesforce/core" "^8.24.0"
+    "@salesforce/core" "^8.25.1"
     "@salesforce/kit" "^3.2.4"
-    "@salesforce/o11y-reporter" "1.6.0"
+    "@salesforce/o11y-reporter" "1.7.3"
     applicationinsights "^2.9.8"
     got "^11"
+    o11y_schema "^260.41.0"
     proxy-agent "^6.5.0"
 
-"@salesforce/templates@^65.4.3":
-  version "65.4.4"
-  resolved "https://registry.yarnpkg.com/@salesforce/templates/-/templates-65.4.4.tgz#e02ebe76b075580842884800738543969e576995"
-  integrity sha512-hQj6j4lVlW/otwnyZ4fAhogNbgoF0O6yRsIUpP7iXJEIF+awzFOa492Z+gbkIoShqNm/bGvY0zgzZD4eiCHzbw==
+"@salesforce/templates@^65.5.3":
+  version "65.5.7"
+  resolved "https://registry.yarnpkg.com/@salesforce/templates/-/templates-65.5.7.tgz#a82757f851db74bcd691bc7a28a6596bc4a8feec"
+  integrity sha512-/r6HiOhbXa+8pyI2iecaDiJllz6cW6gsUoDDRMYPmIOyM6nAB9iJCdpGH8oByc55RdqhYFAFG8qOjpgM+uhygA==
   dependencies:
     "@salesforce/kit" "^3.2.4"
+    "@salesforce/webapp-template-base-react-app-experimental" "^1.17.1"
+    "@salesforce/webapp-template-base-web-app-experimental" "^1.17.1"
     ejs "^3.1.10"
     got "^11.8.6"
     hpagent "^1.2.0"
     mime-types "^3.0.2"
     proxy-from-env "^1.1.0"
-    tar "^7.5.6"
+    tar "^7.5.7"
     tslib "^2.8.1"
 
 "@salesforce/ts-sinon@^1.4.31":
@@ -2622,11 +2625,21 @@
   resolved "https://registry.yarnpkg.com/@salesforce/ts-types/-/ts-types-2.0.12.tgz#60420622812a7ec7e46d220667bc29b42dc247ff"
   integrity sha512-BIJyduJC18Kc8z+arUm5AZ9VkPRyw1KKAm+Tk+9LT99eOzhNilyfKzhZ4t+tG2lIGgnJpmytZfVDZ0e2kFul8g==
 
-"@salesforce/types@^1.5.0", "@salesforce/types@^1.6.0":
+"@salesforce/types@^1.6.0":
   version "1.6.0"
   resolved "https://registry.yarnpkg.com/@salesforce/types/-/types-1.6.0.tgz#926515ce3f6b16c8efe2afcc86475001d419c6cc"
   integrity sha512-UHk1L3QRaa3WfIqQn5RLmcZmxErXvpFPUteLLgIxlFLrxhcKevvEwkMJF2xNIHpfT4Xj7PcYvqtrRYapX4Pp+A==
 
+"@salesforce/webapp-template-base-react-app-experimental@^1.17.1":
+  version "1.22.0"
+  resolved "https://registry.yarnpkg.com/@salesforce/webapp-template-base-react-app-experimental/-/webapp-template-base-react-app-experimental-1.22.0.tgz#9e7d317af85d292a10222b2084c16cf17f4640c4"
+  integrity sha512-ZryThpjrcFpVNbUpFZAdxM/KXcLOWm733iaV4FcAm1tacRjvrVvugU4Ikjpg/iDVLjA4wPXl3T2Ibqz1dVJFAg==
+
+"@salesforce/webapp-template-base-web-app-experimental@^1.17.1":
+  version "1.22.0"
+  resolved "https://registry.yarnpkg.com/@salesforce/webapp-template-base-web-app-experimental/-/webapp-template-base-web-app-experimental-1.22.0.tgz#c685710b40c4ec3b4fa531a21a0f087658c24fbc"
+  integrity sha512-J2vdAfprb9fDuGHFsZRmpbJUbkrqWmk9W2VZEExggP2nUwUtLKIEkjbLxtOoPgxhEyPzD+zgPSRWHy7QroE/gA==
+
 "@shikijs/core@1.29.2":
   version "1.29.2"
   resolved "https://registry.yarnpkg.com/@shikijs/core/-/core-1.29.2.tgz#9c051d3ac99dd06ae46bd96536380c916e552bf3"
@@ -3788,10 +3801,10 @@ ansi-escapes@^5.0.0:
   dependencies:
     type-fest "^1.0.2"
 
-ansi-escapes@^7.0.0, ansi-escapes@^7.2.0:
-  version "7.2.0"
-  resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-7.2.0.tgz#31b25afa3edd3efc09d98c2fee831d460ff06b49"
-  integrity sha512-g6LhBsl+GBPRWGWsBtutpzBYuIIdBkLEvad5C/va/74Db018+5TZiyA26cZJAr3Rft5lprVqOIPxf5Vid6tqAw==
+ansi-escapes@^7.0.0, ansi-escapes@^7.3.0:
+  version "7.3.0"
+  resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-7.3.0.tgz#5395bb74b2150a4a1d6e3c2565f4aeca78d28627"
+  integrity sha512-BvU8nYgGQBxcmMuEeUEmNTvrMVjJNSH7RgW24vXexN4Ven6qCvy4TntnvlnwnMLTVlcRQQdbRY8NKnaIoeWDNg==
   dependencies:
     environment "^1.0.0"
 
@@ -5891,7 +5904,7 @@ fast-uri@^3.0.1:
   resolved "https://registry.yarnpkg.com/fast-uri/-/fast-uri-3.0.1.tgz#cddd2eecfc83a71c1be2cc2ef2061331be8a7134"
   integrity sha512-MWipKbbYiYI0UC7cl8m/i/IWTqfC8YXsqjzybjddLsFjStroQzsHXkc73JutMvBiXmOvapk+axIl79ig5t55Bw==
 
-fast-xml-parser@5.3.4, fast-xml-parser@^5.3.4:
+fast-xml-parser@5.3.4:
   version "5.3.4"
   resolved "https://registry.yarnpkg.com/fast-xml-parser/-/fast-xml-parser-5.3.4.tgz#06f39aafffdbc97bef0321e626c7ddd06a043ecf"
   integrity sha512-EFd6afGmXlCx8H8WTZHhAoDaWaGyuIBoZJ2mknrNxug+aZKjkp0a0dlars9Izl+jF+7Gu1/5f/2h68cQpe0IiA==
@@ -5905,6 +5918,13 @@ fast-xml-parser@^4.5.3:
   dependencies:
     strnum "^1.1.1"
 
+fast-xml-parser@^5.3.4, fast-xml-parser@^5.3.5:
+  version "5.3.5"
+  resolved "https://registry.yarnpkg.com/fast-xml-parser/-/fast-xml-parser-5.3.5.tgz#3e914cb852e636923cb555deaa356f7366e18b49"
+  integrity sha512-JeaA2Vm9ffQKp9VjvfzObuMCjUYAp5WDYhRYL5LrBPY/jUDlUtOvDfot0vKSkB9tuX885BDHjtw4fZadD95wnA==
+  dependencies:
+    strnum "^2.1.2"
+
 fastest-levenshtein@^1.0.16, fastest-levenshtein@^1.0.7:
   version "1.0.16"
   resolved "https://registry.npmjs.org/fastest-levenshtein/-/fastest-levenshtein-1.0.16.tgz"
@@ -8845,6 +8865,11 @@ o11y_schema@256.154.0:
   resolved "https://registry.yarnpkg.com/o11y_schema/-/o11y_schema-256.154.0.tgz#1f2f94f1e42d07e62a3e18e09b026345b057dc0c"
   integrity sha512-czvU/9cibyZptbr0gLJSM70U7zLlhWC2D2L5e9nOG84Wnqmn4F5YzVjrH1ZQzAzDbBbtbeU6WTS3F/SHqtMQ5g==
 
+o11y_schema@^260.41.0:
+  version "260.43.0"
+  resolved "https://registry.yarnpkg.com/o11y_schema/-/o11y_schema-260.43.0.tgz#67bc897b014f7c678a96ce35d8c51a726a981c55"
+  integrity sha512-j0jvPggMkpmveQq3mm1ZsaLRJvNcrxDfGH8ZI50hLxFWmp/pJvUfhxYkg/Gf0bA1ASBoj0QUAEoJ/UtYv8tbXA==
+
 object-hash@^3.0.0:
   version "3.0.0"
   resolved "https://registry.yarnpkg.com/object-hash/-/object-hash-3.0.0.tgz#73f97f753e7baffc0e2cc9d6e079079744ac82e9"
@@ -10586,10 +10611,10 @@ strnum@^1.1.1:
   resolved "https://registry.yarnpkg.com/strnum/-/strnum-1.1.2.tgz#57bca4fbaa6f271081715dbc9ed7cee5493e28e4"
   integrity sha512-vrN+B7DBIoTTZjnPNewwhx6cBA/H+IS7rfW68n7XxC1y7uoiGQBxaKzqucGUgavX15dJgiGztLJ8vxuEzwqBdA==
 
-strnum@^2.1.0:
-  version "2.1.1"
-  resolved "https://registry.yarnpkg.com/strnum/-/strnum-2.1.1.tgz#cf2a6e0cf903728b8b2c4b971b7e36b4e82d46ab"
-  integrity sha512-7ZvoFTiCnGxBtDqJ//Cu6fWtZtc7Y3x+QOirG15wztbdngGSkht27o2pyGWrVy0b4WAy3jbKmnoK6g5VlVNUUw==
+strnum@^2.1.0, strnum@^2.1.2:
+  version "2.1.2"
+  resolved "https://registry.yarnpkg.com/strnum/-/strnum-2.1.2.tgz#a5e00ba66ab25f9cafa3726b567ce7a49170937a"
+  integrity sha512-l63NF9y/cLROq/yqKXSLtcMeeyOfnSQlfMSlzFt/K73oIaD8DGaQWd7Z34X9GPiKqP5rbSh84Hl4bOlLcjiSrQ==
 
 supports-color@^5.3.0, supports-color@^5.4.0:
   version "5.5.0"
@@ -10663,10 +10688,10 @@ tar@^6.1.11, tar@^6.2.1:
     mkdirp "^1.0.3"
     yallist "^4.0.0"
 
-tar@^7.4.3, tar@^7.5.6:
-  version "7.5.6"
-  resolved "https://registry.yarnpkg.com/tar/-/tar-7.5.6.tgz#2db7a210748a82f0a89cc31527b90d3a24984fb7"
-  integrity sha512-xqUeu2JAIJpXyvskvU3uvQW8PAmHrtXp2KDuMJwQqW8Sqq0CaZBAQ+dKS3RBXVhU4wC5NjAdKrmh84241gO9cA==
+tar@^7.4.3, tar@^7.5.7:
+  version "7.5.7"
+  resolved "https://registry.yarnpkg.com/tar/-/tar-7.5.7.tgz#adf99774008ba1c89819f15dbd6019c630539405"
+  integrity sha512-fov56fJiRuThVFXD6o6/Q354S7pnWMJIVlDBYijsTNx6jKSE4pvrDTs6lUnmGvNyfJwFQQwWy3owKz1ucIhveQ==
   dependencies:
     "@isaacs/fs-minipass" "^4.0.0"
     chownr "^3.0.0"

From 875b6a67310e287acc7bcd5cba90a5df47ff37ad Mon Sep 17 00:00:00 2001
From: Eric Willhoit <ewillhoit@salesforce.com>
Date: Wed, 11 Feb 2026 11:57:42 -0600
Subject: [PATCH 2/2] fix: pause plugin-template release

---
 package.json |  2 +-
 yarn.lock    | 79 ++++++++++++++--------------------------------------
 2 files changed, 22 insertions(+), 59 deletions(-)

diff --git a/package.json b/package.json
index 086e1e93..29617f99 100644
--- a/package.json
+++ b/package.json
@@ -172,7 +172,7 @@
     "@salesforce/plugin-settings": "2.4.55",
     "@salesforce/plugin-sobject": "1.4.82",
     "@salesforce/plugin-telemetry": "3.7.2",
-    "@salesforce/plugin-templates": "56.7.0",
+    "@salesforce/plugin-templates": "56.4.7",
     "@salesforce/plugin-trust": "3.7.113",
     "@salesforce/plugin-user": "3.6.49",
     "@salesforce/sf-plugins-core": "12.2.6",
diff --git a/yarn.lock b/yarn.lock
index 946b9f68..a53d5a59 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -2468,14 +2468,14 @@
     "@salesforce/ts-types" "^2.0.12"
     debug "^4.4.3"
 
-"@salesforce/plugin-templates@56.7.0":
-  version "56.7.0"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-templates/-/plugin-templates-56.7.0.tgz#ab1878cf35f026c35dd2f1f481d9de41cb8fa7f9"
-  integrity sha512-2nnG7TYuQ/HMwQ96CAICGNVCGA9cA0XoCmtogqozjdaKN8381YLty9NZXITE9jZvx/eDF/l4O/VwIPI+JDZXxg==
+"@salesforce/plugin-templates@56.4.7":
+  version "56.4.7"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-templates/-/plugin-templates-56.4.7.tgz#40c170a331544aa2c34e74a99580f8cb95a1a364"
+  integrity sha512-HHFydBGkHCo/0m0Qp1eUTrxQSCE4eQ4PgqkWcog+nQmHHdATdd8m1So2NHG8bjNKXLWYobjuMEXzLcmiw+MlJw==
   dependencies:
-    "@salesforce/core" "^8.25.1"
+    "@salesforce/core" "^8.25.0"
     "@salesforce/sf-plugins-core" "^12"
-    "@salesforce/templates" "^65.5.3"
+    "@salesforce/templates" "^65.4.3"
 
 "@salesforce/plugin-trust@3.7.113", "@salesforce/plugin-trust@^3.7.69":
   version "3.7.113"
@@ -2595,20 +2595,18 @@
     o11y_schema "^260.41.0"
     proxy-agent "^6.5.0"
 
-"@salesforce/templates@^65.5.3":
-  version "65.5.7"
-  resolved "https://registry.yarnpkg.com/@salesforce/templates/-/templates-65.5.7.tgz#a82757f851db74bcd691bc7a28a6596bc4a8feec"
-  integrity sha512-/r6HiOhbXa+8pyI2iecaDiJllz6cW6gsUoDDRMYPmIOyM6nAB9iJCdpGH8oByc55RdqhYFAFG8qOjpgM+uhygA==
+"@salesforce/templates@^65.4.3":
+  version "65.4.4"
+  resolved "https://registry.yarnpkg.com/@salesforce/templates/-/templates-65.4.4.tgz#e02ebe76b075580842884800738543969e576995"
+  integrity sha512-hQj6j4lVlW/otwnyZ4fAhogNbgoF0O6yRsIUpP7iXJEIF+awzFOa492Z+gbkIoShqNm/bGvY0zgzZD4eiCHzbw==
   dependencies:
     "@salesforce/kit" "^3.2.4"
-    "@salesforce/webapp-template-base-react-app-experimental" "^1.17.1"
-    "@salesforce/webapp-template-base-web-app-experimental" "^1.17.1"
     ejs "^3.1.10"
     got "^11.8.6"
     hpagent "^1.2.0"
     mime-types "^3.0.2"
     proxy-from-env "^1.1.0"
-    tar "^7.5.7"
+    tar "^7.5.6"
     tslib "^2.8.1"
 
 "@salesforce/ts-sinon@^1.4.31":
@@ -2630,16 +2628,6 @@
   resolved "https://registry.yarnpkg.com/@salesforce/types/-/types-1.6.0.tgz#926515ce3f6b16c8efe2afcc86475001d419c6cc"
   integrity sha512-UHk1L3QRaa3WfIqQn5RLmcZmxErXvpFPUteLLgIxlFLrxhcKevvEwkMJF2xNIHpfT4Xj7PcYvqtrRYapX4Pp+A==
 
-"@salesforce/webapp-template-base-react-app-experimental@^1.17.1":
-  version "1.22.0"
-  resolved "https://registry.yarnpkg.com/@salesforce/webapp-template-base-react-app-experimental/-/webapp-template-base-react-app-experimental-1.22.0.tgz#9e7d317af85d292a10222b2084c16cf17f4640c4"
-  integrity sha512-ZryThpjrcFpVNbUpFZAdxM/KXcLOWm733iaV4FcAm1tacRjvrVvugU4Ikjpg/iDVLjA4wPXl3T2Ibqz1dVJFAg==
-
-"@salesforce/webapp-template-base-web-app-experimental@^1.17.1":
-  version "1.22.0"
-  resolved "https://registry.yarnpkg.com/@salesforce/webapp-template-base-web-app-experimental/-/webapp-template-base-web-app-experimental-1.22.0.tgz#c685710b40c4ec3b4fa531a21a0f087658c24fbc"
-  integrity sha512-J2vdAfprb9fDuGHFsZRmpbJUbkrqWmk9W2VZEExggP2nUwUtLKIEkjbLxtOoPgxhEyPzD+zgPSRWHy7QroE/gA==
-
 "@shikijs/core@1.29.2":
   version "1.29.2"
   resolved "https://registry.yarnpkg.com/@shikijs/core/-/core-1.29.2.tgz#9c051d3ac99dd06ae46bd96536380c916e552bf3"
@@ -8866,9 +8854,9 @@ o11y_schema@256.154.0:
   integrity sha512-czvU/9cibyZptbr0gLJSM70U7zLlhWC2D2L5e9nOG84Wnqmn4F5YzVjrH1ZQzAzDbBbtbeU6WTS3F/SHqtMQ5g==
 
 o11y_schema@^260.41.0:
-  version "260.43.0"
-  resolved "https://registry.yarnpkg.com/o11y_schema/-/o11y_schema-260.43.0.tgz#67bc897b014f7c678a96ce35d8c51a726a981c55"
-  integrity sha512-j0jvPggMkpmveQq3mm1ZsaLRJvNcrxDfGH8ZI50hLxFWmp/pJvUfhxYkg/Gf0bA1ASBoj0QUAEoJ/UtYv8tbXA==
+  version "260.44.0"
+  resolved "https://registry.yarnpkg.com/o11y_schema/-/o11y_schema-260.44.0.tgz#f44612ae5587efc5c8c58662a2ff549bdf9bfeb9"
+  integrity sha512-JedjLmiTwPyHy/O7jPgQG/WXr4L9Mc717YN7TjsTZ3NAFynrnhV7ecjYvumXNK2IKN2KwcYn/Xqa1nYAHMjeWQ==
 
 object-hash@^3.0.0:
   version "3.0.0"
@@ -10467,16 +10455,7 @@ standard-version@^9.5.0:
     stringify-package "^1.0.1"
     yargs "^16.0.0"
 
-"string-width-cjs@npm:string-width@^4.2.0":
-  version "4.2.3"
-  resolved "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz"
-  integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==
-  dependencies:
-    emoji-regex "^8.0.0"
-    is-fullwidth-code-point "^3.0.0"
-    strip-ansi "^6.0.1"
-
-string-width@^4.0.0, string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.3:
+"string-width-cjs@npm:string-width@^4.2.0", string-width@^4.0.0, string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.3:
   version "4.2.3"
   resolved "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz"
   integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==
@@ -10558,14 +10537,7 @@ stringify-package@^1.0.1:
   resolved "https://registry.npmjs.org/stringify-package/-/stringify-package-1.0.1.tgz"
   integrity sha512-sa4DUQsYciMP1xhKWGuFM04fB0LG/9DlluZoSVywUMRNvzid6XucHK0/90xGxRoHrAaROrcHK1aPKaijCtSrhg==
 
-"strip-ansi-cjs@npm:strip-ansi@^6.0.1":
-  version "6.0.1"
-  resolved "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz"
-  integrity sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==
-  dependencies:
-    ansi-regex "^5.0.1"
-
-strip-ansi@6.0.1, strip-ansi@^6, strip-ansi@^6.0.0, strip-ansi@^6.0.1:
+"strip-ansi-cjs@npm:strip-ansi@^6.0.1", strip-ansi@6.0.1, strip-ansi@^6, strip-ansi@^6.0.0, strip-ansi@^6.0.1:
   version "6.0.1"
   resolved "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz"
   integrity sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==
@@ -10688,10 +10660,10 @@ tar@^6.1.11, tar@^6.2.1:
     mkdirp "^1.0.3"
     yallist "^4.0.0"
 
-tar@^7.4.3, tar@^7.5.7:
-  version "7.5.7"
-  resolved "https://registry.yarnpkg.com/tar/-/tar-7.5.7.tgz#adf99774008ba1c89819f15dbd6019c630539405"
-  integrity sha512-fov56fJiRuThVFXD6o6/Q354S7pnWMJIVlDBYijsTNx6jKSE4pvrDTs6lUnmGvNyfJwFQQwWy3owKz1ucIhveQ==
+tar@^7.4.3, tar@^7.5.6:
+  version "7.5.6"
+  resolved "https://registry.yarnpkg.com/tar/-/tar-7.5.6.tgz#2db7a210748a82f0a89cc31527b90d3a24984fb7"
+  integrity sha512-xqUeu2JAIJpXyvskvU3uvQW8PAmHrtXp2KDuMJwQqW8Sqq0CaZBAQ+dKS3RBXVhU4wC5NjAdKrmh84241gO9cA==
   dependencies:
     "@isaacs/fs-minipass" "^4.0.0"
     chownr "^3.0.0"
@@ -11378,7 +11350,7 @@ workerpool@^6.5.1:
   resolved "https://registry.yarnpkg.com/workerpool/-/workerpool-6.5.1.tgz#060f73b39d0caf97c6db64da004cd01b4c099544"
   integrity sha512-Fs4dNYcsdpYSAfVxhnl1L5zTksjvOJxtC5hzMNl+1t9B8hTJTdKDyZ5ju7ztgPy+ft9tBFXoOlDNiOT9WUXZlA==
 
-"wrap-ansi-cjs@npm:wrap-ansi@^7.0.0":
+"wrap-ansi-cjs@npm:wrap-ansi@^7.0.0", wrap-ansi@^7.0.0:
   version "7.0.0"
   resolved "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz"
   integrity sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==
@@ -11396,15 +11368,6 @@ wrap-ansi@^6.2.0:
     string-width "^4.1.0"
     strip-ansi "^6.0.0"
 
-wrap-ansi@^7.0.0:
-  version "7.0.0"
-  resolved "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz"
-  integrity sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==
-  dependencies:
-    ansi-styles "^4.0.0"
-    string-width "^4.1.0"
-    strip-ansi "^6.0.0"
-
 wrap-ansi@^8.1.0:
   version "8.1.0"
   resolved "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-8.1.0.tgz"