@salesforce/plugin-deploy-retrieve 3.22.30 → 3.22.32

package/oclif.manifest.json

@@ -752,16 +752,17 @@
         "tracking:delete:project"
       ]
     },
-    "project:deploy:cancel": {
+    "project:list:ignored": {
       "aliases": [
-        "deploy:metadata:cancel"
+        "force:source:ignored:list"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "Use this command to cancel a deploy operation that hasn't yet completed in the org. Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations.\n\nRun this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.",
+      "description": "When deploying or retrieving metadata between your local project and an org, you can specify the source files you want to exclude with a .forceignore file. The .forceignore file structure mimics the .gitignore structure. Each line in .forceignore specifies a pattern that corresponds to one or more files. The files typically represent metadata components, but can be any files you want to exclude, such as LWC configuration JSON files or tests.",
       "examples": [
-        "Cancel a deploy operation using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
-        "Cancel the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --use-most-recent"
+        "List all the files in all package directories that are ignored:\n<%= config.bin %> <%= command.id %>",
+        "List all the files in a specific directory that are ignored:\n<%= config.bin %> <%= command.id %> --source-dir force-app",
+        "Check if a particular file is ignored:\n<%= config.bin %> <%= command.id %> --source-dir package.xml"
       ],
       "flags": {
         "json": {
@@ -779,103 +780,86 @@
           "multiple": false,
           "type": "option"
         },
-        "target-org": {
-          "char": "o",
-          "name": "target-org",
-          "noCacheDefault": true,
-          "summary": "Username or alias of the target org.",
-          "hasDynamicHelp": true,
-          "multiple": false,
-          "type": "option"
-        },
-        "async": {
-          "description": "The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To resume watching the cancellation, run \"<%= config.bin %> project deploy resume\". To check the status of the cancellation, run \"<%= config.bin %> project deploy report\".",
-          "exclusive": [
-            "wait"
+        "source-dir": {
+          "aliases": [
+            "sourcepath"
           ],
-          "name": "async",
-          "summary": "Run the command asynchronously.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "job-id": {
-          "char": "i",
-          "description": "These commands return a job ID if they time out or you specified the --async flag:\n\n- <%= config.bin %> project deploy start\n- <%= config.bin %> project deploy validate\n- <%= config.bin %> project deploy quick\n- <%= config.bin %> project deploy cancel\n\nThe job ID is valid for 10 days from when you started the deploy operation.",
-          "name": "job-id",
-          "summary": "Job ID of the deploy operation you want to cancel.",
+          "char": "p",
+          "deprecateAliases": true,
+          "name": "source-dir",
+          "summary": "File or directory of files that the command checks for foreceignored files.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        },
-        "use-most-recent": {
-          "char": "r",
-          "description": "For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less. If your most recent deploy operations was more than 3 days ago, this flag won't find a job ID.",
-          "name": "use-most-recent",
-          "summary": "Use the job ID of the most recent deploy operation.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "wait": {
-          "char": "w",
-          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the cancellation, run \"<%= config.bin %> project deploy resume\". To check the status of the cancellation, run \"<%= config.bin %> project deploy report\".",
-          "exclusive": [
-            "async"
-          ],
-          "name": "wait",
-          "summary": "Number of minutes to wait for the command to complete and display results.",
-          "hasDynamicHelp": true,
-          "helpValue": "<minutes>",
-          "multiple": false,
-          "type": "option"
         }
       },
-      "hasDynamicHelp": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "project:deploy:cancel",
+      "id": "project:list:ignored",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Cancel a deploy operation.",
+      "summary": "Check your local project package directories for forceignored files.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "project",
-        "deploy",
-        "cancel.js"
+        "list",
+        "ignored.js"
       ],
       "aliasPermutations": [
-        "deploy:metadata:cancel",
-        "metadata:deploy:cancel",
-        "metadata:cancel:deploy",
-        "deploy:cancel:metadata",
-        "cancel:deploy:metadata",
-        "cancel:metadata:deploy"
+        "force:source:ignored:list",
+        "source:force:ignored:list",
+        "source:ignored:force:list",
+        "source:ignored:list:force",
+        "force:ignored:source:list",
+        "ignored:force:source:list",
+        "ignored:source:force:list",
+        "ignored:source:list:force",
+        "force:ignored:list:source",
+        "ignored:force:list:source",
+        "ignored:list:force:source",
+        "ignored:list:source:force",
+        "force:source:list:ignored",
+        "source:force:list:ignored",
+        "source:list:force:ignored",
+        "source:list:ignored:force",
+        "force:list:source:ignored",
+        "list:force:source:ignored",
+        "list:source:force:ignored",
+        "list:source:ignored:force",
+        "force:list:ignored:source",
+        "list:force:ignored:source",
+        "list:ignored:force:source",
+        "list:ignored:source:force"
       ],
       "permutations": [
-        "project:deploy:cancel",
-        "deploy:project:cancel",
-        "deploy:cancel:project",
-        "project:cancel:deploy",
-        "cancel:project:deploy",
-        "cancel:deploy:project"
+        "project:list:ignored",
+        "list:project:ignored",
+        "list:ignored:project",
+        "project:ignored:list",
+        "ignored:project:list",
+        "ignored:list:project"
       ]
     },
-    "project:deploy:preview": {
+    "project:generate:manifest": {
       "aliases": [
-        "deploy:metadata:preview"
+        "force:source:manifest:create"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "You must run this command from within a project.\n\nThe command outputs a table that describes what will happen if you run the \"<%= config.bin %> project deploy start\" command. The table lists the metadata components that will be deployed and deleted. The table also lists the current conflicts between files in your local project and components in the org. Finally, the table lists the files that won't be deployed because they're included in your .forceignore file.\n\nIf your org allows source tracking, then this command displays potential conflicts between the org and your local project. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the \"<%= config.bin %> org create scratch|sandbox\" commands.\n\nTo preview the deployment of multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --source-dir.",
+      "description": "Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-dir). You can specify either of these flags, not both.\n\nUse --type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this flag, and their respective file names, are:\n\n    * package : package.xml (default)\n    * pre : destructiveChangesPre.xml\n    * post : destructiveChangesPost.xml\n    * destroy : destructiveChanges.xml\n\nSee https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files.\n\nUse --name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --type or --name, but not both.\n\nTo include multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --include-packages and --source-dir.\n\nTo build a manifest from the metadata in an org, use the --from-org flag. You can combine --from-org with the --metadata flag to include only certain metadata types, or with the --excluded-metadata flag to exclude certain metadata types. When building a manifest from an org, the command makes many concurrent API calls to discover the metadata that exists in the org. To limit the number of concurrent requests, use the SF_LIST_METADATA_BATCH_SIZE environment variable and set it to a size that works best for your org and environment. If you experience timeouts or inconsistent manifest contents, then setting this environment variable can improve accuracy. However, the command takes longer to run because it sends fewer requests at a time.",
       "examples": [
-        "NOTE: The commands to preview a deployment and actually deploy it use similar flags. We provide a few preview examples here, but see the help for \"<%= config.bin %> project deploy start\" for more examples that you can adapt for previewing.",
-        "Preview the deployment of source files in a directory, such as force-app, to your default org:\n<%= config.bin %> <%= command.id %>  --source-dir force-app",
-        "Preview the deployment of all Apex classes to an org with alias \"my-scratch\":\n<%= config.bin %> <%= command.id %> --metadata ApexClass --target-org my-scratch",
-        "Preview deployment of a specific Apex class:\n<%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass",
-        "Preview deployment of all components listed in a manifest:\n<%= config.bin %> <%= command.id %> --manifest path/to/package.xml"
+        "Create a manifest for deploying or retrieving all Apex classes and custom objects:\n$ <%= config.bin %> <%= command.id %> --metadata ApexClass --metadata CustomObject",
+        "Create a manifest for deleting the specified Apex class:\n$ <%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass --type destroy",
+        "Create a manifest for deploying or retrieving all the metadata components in the specified local directory; name the file myNewManifest.xml:\n$ <%= config.bin %> <%= command.id %> --source-dir force-app --name myNewManifest",
+        "Create a manifest from the metadata components in the specified org and include metadata in any unlocked packages:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --include-packages unlocked",
+        "Create a manifest from specific metadata types in an org:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --metadata ApexClass,CustomObject,CustomLabels",
+        "Create a manifest from all metadata components in an org excluding specific metadata types:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --excluded-metadata StandardValueSet"
       ],
       "flags": {
         "json": {
@@ -893,287 +877,213 @@
           "multiple": false,
           "type": "option"
         },
-        "ignore-conflicts": {
-          "char": "c",
-          "description": "This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as production orgs.",
-          "name": "ignore-conflicts",
-          "summary": "Don't display conflicts in preview of the deployment.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "manifest": {
-          "char": "x",
-          "description": "All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.",
-          "exclusive": [
-            "source-dir",
-            "metadata"
+        "api-version": {
+          "aliases": [
+            "apiversion"
           ],
-          "name": "manifest",
-          "summary": "Full file path for manifest (package.xml) of components to preview.",
+          "deprecateAliases": true,
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "loglevel": {
+          "deprecated": {
+            "message": "The loglevel flag is no longer in use on this command. You may use it without error, but it will be ignored.\nSet the log level using the `SFDX_LOG_LEVEL` environment variable."
+          },
+          "hidden": true,
+          "name": "loglevel",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "metadata": {
           "char": "m",
-          "exclusive": [
-            "manifest",
-            "source-dir"
-          ],
           "name": "metadata",
-          "summary": "Metadata component names to preview.",
+          "summary": "Names of metadata components to include in the manifest.",
+          "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
         },
         "source-dir": {
-          "char": "d",
-          "description": "The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its subdirectories).\n\nIf you specify this flag, don’t specify --metadata or --manifest.",
-          "exclusive": [
-            "manifest",
-            "metadata"
+          "aliases": [
+            "sourcepath"
           ],
+          "char": "p",
+          "deprecateAliases": true,
           "name": "source-dir",
-          "summary": "Path to the local source files to preview.",
+          "summary": "Paths to the local source files to include in the manifest.",
+          "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
         },
-        "target-org": {
-          "char": "o",
-          "name": "target-org",
-          "noCacheDefault": true,
-          "required": true,
-          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
-          "hasDynamicHelp": true,
+        "name": {
+          "aliases": [
+            "manifestname"
+          ],
+          "char": "n",
+          "deprecateAliases": true,
+          "exclusive": [
+            "type"
+          ],
+          "name": "name",
+          "summary": "Name of a custom manifest file to create.",
+          "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "concise": {
-          "name": "concise",
-          "summary": "Show only the changes that will be deployed; omits files that are forceignored.",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": true,
-      "hiddenAliases": [],
-      "id": "project:deploy:preview",
-      "pluginAlias": "@salesforce/plugin-deploy-retrieve",
-      "pluginName": "@salesforce/plugin-deploy-retrieve",
-      "pluginType": "core",
-      "strict": true,
-      "summary": "Preview a deployment to see what will deploy to the org, the potential conflicts, and the ignored files.",
-      "enableJsonFlag": true,
-      "requiresProject": true,
-      "isESM": true,
-      "relativePath": [
-        "lib",
-        "commands",
-        "project",
-        "deploy",
-        "preview.js"
-      ],
-      "aliasPermutations": [
-        "deploy:metadata:preview",
-        "metadata:deploy:preview",
-        "metadata:preview:deploy",
-        "deploy:preview:metadata",
-        "preview:deploy:metadata",
-        "preview:metadata:deploy"
-      ],
-      "permutations": [
-        "project:deploy:preview",
-        "deploy:project:preview",
-        "deploy:preview:project",
-        "project:preview:deploy",
-        "preview:project:deploy",
-        "preview:deploy:project"
-      ]
-    },
-    "project:deploy:quick": {
-      "aliases": [
-        "deploy:metadata:quick"
-      ],
-      "args": {},
-      "deprecateAliases": true,
-      "description": "Before you run this command, first create a validated deployment with the \"<%= config.bin %> project deploy validate\" command, which returns a job ID. Validated deployments haven't been deployed to the org yet; you deploy them with this command. Either pass the job ID to this command or use the --use-most-recent flag to use the job ID of the most recently validated deployment. For the quick deploy to succeed, the associated validated deployment must also have succeeded.\n\nExecuting this quick deploy command takes less time than a standard deploy because it skips running Apex tests. These tests were previously run as part of the validation. Validating first and then running a quick deploy is useful if the deployment to your production org take several hours and you don’t want to risk a failed deploy.\n\nThis command doesn't support source-tracking. The source you deploy overwrites the corresponding metadata in your org. This command doesn’t attempt to merge your source with the versions in your org.\n\nNote: Don't use this command on sandboxes; the command is intended to be used on production orgs. By default, sandboxes don't run tests during a deploy. Use \"<%= config.bin %> project deploy start\" instead.",
-      "examples": [
-        "Run a quick deploy to your default org using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
-        "Asynchronously run a quick deploy of the most recently validated deployment to an org with alias \"my-prod-org\":\n<%= config.bin %> <%= command.id %> --async --use-most-recent --target-org my-prod-org"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "flags-dir": {
-          "helpGroup": "GLOBAL",
-          "name": "flags-dir",
-          "summary": "Import flag values from a directory.",
+        "type": {
+          "aliases": [
+            "manifesttype"
+          ],
+          "char": "t",
+          "deprecateAliases": true,
+          "exclusive": [
+            "name"
+          ],
+          "name": "type",
+          "summary": "Type of manifest to create; the type determines the name of the created file.",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "pre",
+            "post",
+            "destroy",
+            "package"
+          ],
           "type": "option"
         },
-        "async": {
-          "description": "The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To resume watching the deploy, run \"<%= config.bin %> project deploy resume\". To check the status of the deploy, run \"<%= config.bin %> project deploy report\".",
-          "exclusive": [
-            "wait"
+        "include-packages": {
+          "aliases": [
+            "includepackages"
           ],
-          "name": "async",
-          "summary": "Run the command asynchronously.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "concise": {
-          "exclusive": [
-            "verbose"
+          "char": "c",
+          "dependsOn": [
+            "from-org"
           ],
-          "name": "concise",
-          "summary": "Show concise output of the deploy result.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "job-id": {
-          "char": "i",
-          "description": "The job ID is valid for 10 days from when you started the validation.",
-          "name": "job-id",
-          "summary": "Job ID of the deployment you want to quick deploy.",
+          "deprecateAliases": true,
+          "name": "include-packages",
+          "summary": "Package types (managed, unlocked) whose metadata is included in the manifest; by default, metadata in managed and unlocked packages is excluded. Metadata in unmanaged packages is always included.",
+          "delimiter": ",",
           "hasDynamicHelp": false,
-          "multiple": false,
+          "multiple": true,
+          "options": [
+            "managed",
+            "unlocked"
+          ],
           "type": "option"
         },
-        "target-org": {
-          "char": "o",
-          "name": "target-org",
-          "noCacheDefault": true,
-          "summary": "Username or alias of the target org.",
-          "hasDynamicHelp": true,
-          "multiple": false,
+        "excluded-metadata": {
+          "name": "excluded-metadata",
+          "relationships": [
+            {
+              "type": "some",
+              "flags": [
+                "from-org",
+                "source-dir"
+              ]
+            }
+          ],
+          "summary": "Metadata types to exclude when building a manifest from an org. Specify the name of the type, not the name of a specific component.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
           "type": "option"
         },
-        "use-most-recent": {
-          "char": "r",
-          "description": "For performance reasons, this flag uses only job IDs that were validated in the past 3 days or less. If your most recent deployment validation was more than 3 days ago, this flag won't find a job ID.",
-          "name": "use-most-recent",
-          "summary": "Use the job ID of the most recently validated deployment.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "verbose": {
-          "exclusive": [
-            "concise"
+        "from-org": {
+          "aliases": [
+            "fromorg"
           ],
-          "name": "verbose",
-          "summary": "Show verbose output of the deploy result.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "wait": {
-          "char": "w",
-          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the deploy, run \"<%= config.bin %> project deploy resume\". To check the status of the deploy, run \"<%= config.bin %> project deploy report\".",
+          "deprecateAliases": true,
           "exclusive": [
-            "async"
+            "source-dir"
           ],
-          "name": "wait",
-          "summary": "Number of minutes to wait for the command to complete and display results.",
-          "default": "33 minutes",
-          "hasDynamicHelp": true,
-          "helpValue": "<minutes>",
+          "name": "from-org",
+          "summary": "Username or alias of the org that contains the metadata components from which to build a manifest.",
+          "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
-          "char": "a",
-          "description": "Use this flag to override the default API version with the API version of your package.xml file. The default API version is the latest version supported by the CLI.",
-          "name": "api-version",
-          "summary": "Target API version for the deploy.",
+        "output-dir": {
+          "aliases": [
+            "outputdir",
+            "o"
+          ],
+          "char": "d",
+          "deprecateAliases": true,
+          "name": "output-dir",
+          "summary": "Directory to save the created manifest.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "project:deploy:quick",
+      "id": "project:generate:manifest",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Quickly deploy a validated deployment to an org.",
+      "summary": "Create a project manifest that lists the metadata components you want to deploy or retrieve.",
       "enableJsonFlag": true,
-      "errorCodes": {
-        "header": "ERROR CODES",
-        "body": [
-          {
-            "name": "Succeeded (0)",
-            "description": "The deploy succeeded."
-          },
-          {
-            "name": "Canceled (1)",
-            "description": "The deploy was canceled."
-          },
-          {
-            "name": "Failed (1)",
-            "description": "The deploy failed."
-          },
-          {
-            "name": "SucceededPartial (68)",
-            "description": "The deploy partially succeeded."
-          },
-          {
-            "name": "InProgress (69)",
-            "description": "The deploy is in progress."
-          },
-          {
-            "name": "Pending (69)",
-            "description": "The deploy is pending."
-          },
-          {
-            "name": "Canceling (69)",
-            "description": "The deploy is being canceled."
-          }
-        ]
-      },
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "project",
-        "deploy",
-        "quick.js"
+        "generate",
+        "manifest.js"
       ],
       "aliasPermutations": [
-        "deploy:metadata:quick",
-        "metadata:deploy:quick",
-        "metadata:quick:deploy",
-        "deploy:quick:metadata",
-        "quick:deploy:metadata",
-        "quick:metadata:deploy"
+        "force:source:manifest:create",
+        "source:force:manifest:create",
+        "source:manifest:force:create",
+        "source:manifest:create:force",
+        "force:manifest:source:create",
+        "manifest:force:source:create",
+        "manifest:source:force:create",
+        "manifest:source:create:force",
+        "force:manifest:create:source",
+        "manifest:force:create:source",
+        "manifest:create:force:source",
+        "manifest:create:source:force",
+        "force:source:create:manifest",
+        "source:force:create:manifest",
+        "source:create:force:manifest",
+        "source:create:manifest:force",
+        "force:create:source:manifest",
+        "create:force:source:manifest",
+        "create:source:force:manifest",
+        "create:source:manifest:force",
+        "force:create:manifest:source",
+        "create:force:manifest:source",
+        "create:manifest:force:source",
+        "create:manifest:source:force"
       ],
       "permutations": [
-        "project:deploy:quick",
-        "deploy:project:quick",
-        "deploy:quick:project",
-        "project:quick:deploy",
-        "quick:project:deploy",
-        "quick:deploy:project"
+        "project:generate:manifest",
+        "generate:project:manifest",
+        "generate:manifest:project",
+        "project:manifest:generate",
+        "manifest:project:generate",
+        "manifest:generate:project"
       ]
     },
-    "project:deploy:report": {
+    "project:deploy:cancel": {
       "aliases": [
-        "deploy:metadata:report"
+        "deploy:metadata:cancel"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations.\n\nRun this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation. If you specify the --wait flag, the command polls for the status every second until the timeout of --wait minutes. If you don't specify the --wait flag, the command simply checks and displays the status of the deploy; the command doesn't poll for the status.\n\nYou typically don't specify the --target-org flag because the cached job already references the org to which you deployed. But if you run this command on a computer different than the one from which you deployed, then you must specify the --target-org and it must point to the same org.\n\nThis command doesn't update source tracking information.",
+      "description": "Use this command to cancel a deploy operation that hasn't yet completed in the org. Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations.\n\nRun this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.",
       "examples": [
-        "Check the status using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
-        "Check the status of the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --use-most-recent",
-        "Poll for the status using a job ID and target org:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2 --target-org me@my.org --wait 30"
+        "Cancel a deploy operation using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
+        "Cancel the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --use-most-recent"
       ],
       "flags": {
         "json": {
@@ -1200,124 +1110,219 @@
           "multiple": false,
           "type": "option"
         },
+        "async": {
+          "description": "The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To resume watching the cancellation, run \"<%= config.bin %> project deploy resume\". To check the status of the cancellation, run \"<%= config.bin %> project deploy report\".",
+          "exclusive": [
+            "wait"
+          ],
+          "name": "async",
+          "summary": "Run the command asynchronously.",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "job-id": {
           "char": "i",
           "description": "These commands return a job ID if they time out or you specified the --async flag:\n\n- <%= config.bin %> project deploy start\n- <%= config.bin %> project deploy validate\n- <%= config.bin %> project deploy quick\n- <%= config.bin %> project deploy cancel\n\nThe job ID is valid for 10 days from when you started the deploy operation.",
           "name": "job-id",
-          "summary": "Job ID of the deploy operation you want to check the status of.",
+          "summary": "Job ID of the deploy operation you want to cancel.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "use-most-recent": {
           "char": "r",
-          "description": "For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less. If your most recent operation was more than 3 days ago, this flag won't find a job ID.",
+          "description": "For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less. If your most recent deploy operations was more than 3 days ago, this flag won't find a job ID.",
           "name": "use-most-recent",
           "summary": "Use the job ID of the most recent deploy operation.",
           "allowNo": false,
           "type": "boolean"
         },
-        "coverage-formatters": {
-          "description": "For multiple formatters, repeat the flag for each formatter.\n--coverage-formatters lcov --coverage-formatters clover",
-          "helpGroup": "Test",
-          "name": "coverage-formatters",
-          "summary": "Format of the code coverage results.",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "options": [
-            "clover",
-            "cobertura",
-            "html-spa",
-            "html",
-            "json",
-            "json-summary",
-            "lcovonly",
-            "none",
-            "teamcity",
-            "text",
-            "text-summary"
+        "wait": {
+          "char": "w",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the cancellation, run \"<%= config.bin %> project deploy resume\". To check the status of the cancellation, run \"<%= config.bin %> project deploy report\".",
+          "exclusive": [
+            "async"
           ],
+          "name": "wait",
+          "summary": "Number of minutes to wait for the command to complete and display results.",
+          "hasDynamicHelp": true,
+          "helpValue": "<minutes>",
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "project:deploy:cancel",
+      "pluginAlias": "@salesforce/plugin-deploy-retrieve",
+      "pluginName": "@salesforce/plugin-deploy-retrieve",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Cancel a deploy operation.",
+      "enableJsonFlag": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "project",
+        "deploy",
+        "cancel.js"
+      ],
+      "aliasPermutations": [
+        "deploy:metadata:cancel",
+        "metadata:deploy:cancel",
+        "metadata:cancel:deploy",
+        "deploy:cancel:metadata",
+        "cancel:deploy:metadata",
+        "cancel:metadata:deploy"
+      ],
+      "permutations": [
+        "project:deploy:cancel",
+        "deploy:project:cancel",
+        "deploy:cancel:project",
+        "project:cancel:deploy",
+        "cancel:project:deploy",
+        "cancel:deploy:project"
+      ]
+    },
+    "project:deploy:preview": {
+      "aliases": [
+        "deploy:metadata:preview"
+      ],
+      "args": {},
+      "deprecateAliases": true,
+      "description": "You must run this command from within a project.\n\nThe command outputs a table that describes what will happen if you run the \"<%= config.bin %> project deploy start\" command. The table lists the metadata components that will be deployed and deleted. The table also lists the current conflicts between files in your local project and components in the org. Finally, the table lists the files that won't be deployed because they're included in your .forceignore file.\n\nIf your org allows source tracking, then this command displays potential conflicts between the org and your local project. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the \"<%= config.bin %> org create scratch|sandbox\" commands.\n\nTo preview the deployment of multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --source-dir.",
+      "examples": [
+        "NOTE: The commands to preview a deployment and actually deploy it use similar flags. We provide a few preview examples here, but see the help for \"<%= config.bin %> project deploy start\" for more examples that you can adapt for previewing.",
+        "Preview the deployment of source files in a directory, such as force-app, to your default org:\n<%= config.bin %> <%= command.id %>  --source-dir force-app",
+        "Preview the deployment of all Apex classes to an org with alias \"my-scratch\":\n<%= config.bin %> <%= command.id %> --metadata ApexClass --target-org my-scratch",
+        "Preview deployment of a specific Apex class:\n<%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass",
+        "Preview deployment of all components listed in a manifest:\n<%= config.bin %> <%= command.id %> --manifest path/to/package.xml"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
           "type": "option"
         },
-        "junit": {
-          "helpGroup": "Test",
-          "name": "junit",
-          "summary": "Output JUnit test results.",
+        "ignore-conflicts": {
+          "char": "c",
+          "description": "This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as production orgs.",
+          "name": "ignore-conflicts",
+          "summary": "Don't display conflicts in preview of the deployment.",
           "allowNo": false,
           "type": "boolean"
         },
-        "results-dir": {
-          "helpGroup": "Test",
-          "name": "results-dir",
-          "relationships": [
-            {
-              "type": "some",
-              "flags": [
-                "coverage-formatters",
-                "junit"
-              ]
-            }
+        "manifest": {
+          "char": "x",
+          "description": "All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.",
+          "exclusive": [
+            "source-dir",
+            "metadata"
           ],
-          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
+          "name": "manifest",
+          "summary": "Full file path for manifest (package.xml) of components to preview.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "wait": {
-          "char": "w",
-          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run \"<%= config.bin %> project deploy resume\". To check the status of the deployment, run \"<%= config.bin %> project deploy report\".",
-          "name": "wait",
-          "summary": "Number of minutes to wait for command to complete and display results.",
+        "metadata": {
+          "char": "m",
+          "exclusive": [
+            "manifest",
+            "source-dir"
+          ],
+          "name": "metadata",
+          "summary": "Metadata component names to preview.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "source-dir": {
+          "char": "d",
+          "description": "The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its subdirectories).\n\nIf you specify this flag, don’t specify --metadata or --manifest.",
+          "exclusive": [
+            "manifest",
+            "metadata"
+          ],
+          "name": "source-dir",
+          "summary": "Path to the local source files to preview.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
           "hasDynamicHelp": true,
-          "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
+        },
+        "concise": {
+          "name": "concise",
+          "summary": "Show only the changes that will be deployed; omits files that are forceignored.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:report",
+      "id": "project:deploy:preview",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Check or poll for the status of a deploy operation.",
+      "summary": "Preview a deployment to see what will deploy to the org, the potential conflicts, and the ignored files.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "project",
         "deploy",
-        "report.js"
+        "preview.js"
       ],
       "aliasPermutations": [
-        "deploy:metadata:report",
-        "metadata:deploy:report",
-        "metadata:report:deploy",
-        "deploy:report:metadata",
-        "report:deploy:metadata",
-        "report:metadata:deploy"
+        "deploy:metadata:preview",
+        "metadata:deploy:preview",
+        "metadata:preview:deploy",
+        "deploy:preview:metadata",
+        "preview:deploy:metadata",
+        "preview:metadata:deploy"
       ],
       "permutations": [
-        "project:deploy:report",
-        "deploy:project:report",
-        "deploy:report:project",
-        "project:report:deploy",
-        "report:project:deploy",
-        "report:deploy:project"
+        "project:deploy:preview",
+        "deploy:project:preview",
+        "deploy:preview:project",
+        "project:preview:deploy",
+        "preview:project:deploy",
+        "preview:deploy:project"
       ]
     },
-    "project:deploy:resume": {
+    "project:deploy:quick": {
       "aliases": [
-        "deploy:metadata:resume"
+        "deploy:metadata:quick"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "Use this command to resume watching a deploy operation if the original command times out or you specified the --async flag. Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations. This command doesn't resume the original operation itself, because the operation always continues after you've started it, regardless of whether you're watching it or not. When the deploy completes, source tracking information is updated as needed.\n\nRun this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.",
+      "description": "Before you run this command, first create a validated deployment with the \"<%= config.bin %> project deploy validate\" command, which returns a job ID. Validated deployments haven't been deployed to the org yet; you deploy them with this command. Either pass the job ID to this command or use the --use-most-recent flag to use the job ID of the most recently validated deployment. For the quick deploy to succeed, the associated validated deployment must also have succeeded.\n\nExecuting this quick deploy command takes less time than a standard deploy because it skips running Apex tests. These tests were previously run as part of the validation. Validating first and then running a quick deploy is useful if the deployment to your production org take several hours and you don’t want to risk a failed deploy.\n\nThis command doesn't support source-tracking. The source you deploy overwrites the corresponding metadata in your org. This command doesn’t attempt to merge your source with the versions in your org.\n\nNote: Don't use this command on sandboxes; the command is intended to be used on production orgs. By default, sandboxes don't run tests during a deploy. Use \"<%= config.bin %> project deploy start\" instead.",
       "examples": [
-        "Resume watching a deploy operation using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
-        "Resume watching the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --use-most-recent"
+        "Run a quick deploy to your default org using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
+        "Asynchronously run a quick deploy of the most recently validated deployment to an org with alias \"my-prod-org\":\n<%= config.bin %> <%= command.id %> --async --use-most-recent --target-org my-prod-org"
       ],
       "flags": {
         "json": {
@@ -1335,29 +1340,48 @@
           "multiple": false,
           "type": "option"
         },
+        "async": {
+          "description": "The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To resume watching the deploy, run \"<%= config.bin %> project deploy resume\". To check the status of the deploy, run \"<%= config.bin %> project deploy report\".",
+          "exclusive": [
+            "wait"
+          ],
+          "name": "async",
+          "summary": "Run the command asynchronously.",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "concise": {
           "exclusive": [
             "verbose"
           ],
           "name": "concise",
-          "summary": "Show concise output of the deploy operation result.",
+          "summary": "Show concise output of the deploy result.",
           "allowNo": false,
           "type": "boolean"
         },
         "job-id": {
           "char": "i",
-          "description": "These commands return a job ID if they time out or you specified the --async flag:\n\n- <%= config.bin %> project deploy start\n- <%= config.bin %> project deploy validate\n- <%= config.bin %> project deploy quick\n- <%= config.bin %> project deploy cancel\n\nThe job ID is valid for 10 days from when you started the deploy operation.",
+          "description": "The job ID is valid for 10 days from when you started the validation.",
           "name": "job-id",
-          "summary": "Job ID of the deploy operation you want to resume.",
+          "summary": "Job ID of the deployment you want to quick deploy.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "summary": "Username or alias of the target org.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
         "use-most-recent": {
           "char": "r",
-          "description": "For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less. If your most recent operation was more than 3 days ago, this flag won't find a job ID.",
+          "description": "For performance reasons, this flag uses only job IDs that were validated in the past 3 days or less. If your most recent deployment validation was more than 3 days ago, this flag won't find a job ID.",
           "name": "use-most-recent",
-          "summary": "Use the job ID of the most recent deploy operation.",
+          "summary": "Use the job ID of the most recently validated deployment.",
           "allowNo": false,
           "type": "boolean"
         },
@@ -1366,62 +1390,29 @@
             "concise"
           ],
           "name": "verbose",
-          "summary": "Show verbose output of the deploy operation result.",
+          "summary": "Show verbose output of the deploy result.",
           "allowNo": false,
           "type": "boolean"
         },
         "wait": {
           "char": "w",
-          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the deploy operation, run this command again. To check the status of the deploy operation, run \"<%= config.bin %> project deploy report\".",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the deploy, run \"<%= config.bin %> project deploy resume\". To check the status of the deploy, run \"<%= config.bin %> project deploy report\".",
+          "exclusive": [
+            "async"
+          ],
           "name": "wait",
           "summary": "Number of minutes to wait for the command to complete and display results.",
+          "default": "33 minutes",
           "hasDynamicHelp": true,
           "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
         },
-        "coverage-formatters": {
-          "description": "For multiple formatters, repeat the flag for each formatter.\n--coverage-formatters lcov --coverage-formatters clover",
-          "helpGroup": "Test",
-          "name": "coverage-formatters",
-          "summary": "Format of the code coverage results.",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "options": [
-            "clover",
-            "cobertura",
-            "html-spa",
-            "html",
-            "json",
-            "json-summary",
-            "lcovonly",
-            "none",
-            "teamcity",
-            "text",
-            "text-summary"
-          ],
-          "type": "option"
-        },
-        "junit": {
-          "helpGroup": "Test",
-          "name": "junit",
-          "summary": "Output JUnit test results.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "results-dir": {
-          "helpGroup": "Test",
-          "name": "results-dir",
-          "relationships": [
-            {
-              "type": "some",
-              "flags": [
-                "coverage-formatters",
-                "junit"
-              ]
-            }
-          ],
-          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
+        "api-version": {
+          "char": "a",
+          "description": "Use this flag to override the default API version with the API version of your package.xml file. The default API version is the latest version supported by the CLI.",
+          "name": "api-version",
+          "summary": "Target API version for the deploy.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -1429,22 +1420,13 @@
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:resume",
+      "id": "project:deploy:quick",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Resume watching a deploy operation and update source tracking when the deploy completes.",
+      "summary": "Quickly deploy a validated deployment to an org.",
       "enableJsonFlag": true,
-      "envVariablesSection": {
-        "header": "ENVIRONMENT VARIABLES",
-        "body": [
-          {
-            "name": "SF_USE_PROGRESS_BAR",
-            "description": "Set to false to disable the progress bar when running the metadata deploy command."
-          }
-        ]
-      },
       "errorCodes": {
         "header": "ERROR CODES",
         "body": [
@@ -1484,47 +1466,36 @@
         "commands",
         "project",
         "deploy",
-        "resume.js"
+        "quick.js"
       ],
       "aliasPermutations": [
-        "deploy:metadata:resume",
-        "metadata:deploy:resume",
-        "metadata:resume:deploy",
-        "deploy:resume:metadata",
-        "resume:deploy:metadata",
-        "resume:metadata:deploy"
+        "deploy:metadata:quick",
+        "metadata:deploy:quick",
+        "metadata:quick:deploy",
+        "deploy:quick:metadata",
+        "quick:deploy:metadata",
+        "quick:metadata:deploy"
       ],
       "permutations": [
-        "project:deploy:resume",
-        "deploy:project:resume",
-        "deploy:resume:project",
-        "project:resume:deploy",
-        "resume:project:deploy",
-        "resume:deploy:project"
+        "project:deploy:quick",
+        "deploy:project:quick",
+        "deploy:quick:project",
+        "project:quick:deploy",
+        "quick:project:deploy",
+        "quick:deploy:project"
       ]
     },
-    "project:deploy:start": {
+    "project:deploy:report": {
       "aliases": [
-        "deploy:metadata"
+        "deploy:metadata:report"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "You must run this command from within a project.\n\nMetadata components are deployed in source format by default. Deploy them in metadata format by specifying the --metadata-dir flag, which specifies the root directory or ZIP file that contains the metadata formatted files you want to deploy.\n\nIf your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production orgs, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the \"<%= config.bin %> org create scratch|sandbox\" commands.\n\nTo deploy multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --source-dir.",
+      "description": "Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations.\n\nRun this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation. If you specify the --wait flag, the command polls for the status every second until the timeout of --wait minutes. If you don't specify the --wait flag, the command simply checks and displays the status of the deploy; the command doesn't poll for the status.\n\nYou typically don't specify the --target-org flag because the cached job already references the org to which you deployed. But if you run this command on a computer different than the one from which you deployed, then you must specify the --target-org and it must point to the same org.\n\nThis command doesn't update source tracking information.",
       "examples": [
-        "Deploy local changes not in the org; uses your default org:\n<%= config.bin %> <%= command.id %>",
-        "Deploy all source files in the \"force-app\" directory to an org with alias \"my-scratch\"; show only concise output, in other words don't print a list of all the source that was deployed:\n<%= config.bin %> <%= command.id %>  --source-dir force-app --target-org my-scratch --concise",
-        "Deploy all the Apex classes and custom objects that are in the \"force-app\" directory. The list views, layouts, etc, that are associated with the custom objects are also deployed. Both examples are equivalent:\n<%= config.bin %> <%= command.id %> --source-dir force-app/main/default/classes force-app/main/default/objects\n<%= config.bin %> <%= command.id %> --source-dir force-app/main/default/classes --source-dir force-app/main/default/objects",
-        "Deploy all Apex classes that are in all package directories defined in the \"sfdx-project.json\" file:\n<%= config.bin %> <%= command.id %> --metadata ApexClass",
-        "Deploy a specific Apex class; ignore any conflicts between the local project and org (be careful with this flag, because it will overwrite the Apex class in the org if there are conflicts!):\n<%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass --ignore-conflicts",
-        "Deploy specific Apex classes that match a pattern; in this example, deploy Apex classes whose names contain the string \"MyApex\". Also ignore any deployment warnings (again, be careful with this flag! You typically want to see the warnings):\n<%= config.bin %> <%= command.id %> --metadata 'ApexClass:MyApex*' --ignore-warnings",
-        "Deploy a custom object called ExcitingObject that's in the SBQQ namespace:\nsf <%= command.id %> --metadata CustomObject:SBQQ__ExcitingObject",
-        "Deploy all custom objects in the SBQQ namespace by using a wildcard and quotes:\nsf <%= command.id %> --metadata 'CustomObject:SBQQ__*'",
-        "Deploy all custom objects and Apex classes found in all defined package directories (both examples are equivalent):\n<%= config.bin %> <%= command.id %> --metadata CustomObject ApexClass\n<%= config.bin %> <%= command.id %> --metadata CustomObject --metadata ApexClass",
-        "Deploy all Apex classes and a profile that has a space in its name:\n<%= config.bin %> <%= command.id %> --metadata ApexClass --metadata \"Profile:My Profile\"",
-        "Deploy all components listed in a manifest:\n<%= config.bin %> <%= command.id %> --manifest path/to/package.xml",
-        "Run the tests that aren’t in any managed packages as part of a deployment:\n<%= config.bin %> <%= command.id %> --metadata ApexClass --test-level RunLocalTests",
-        "Deploy all metadata formatted files in the \"MDAPI\" directory:\n<%= config.bin %> <%= command.id %> --metadata-dir MDAPI",
-        "Deploy all metadata formatted files in the \"MDAPI\" directory; items listed in the MDAPI/destructiveChangesPre.xml and MDAPI/destructiveChangesPost.xml manifests are immediately eligible for deletion rather than stored in the Recycle Bin:\n<%= config.bin %> <%= command.id %> --metadata-dir MDAPI --purge-on-delete"
+        "Check the status using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
+        "Check the status of the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --use-most-recent",
+        "Poll for the status using a job ID and target org:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2 --target-org me@my.org --wait 30"
       ],
       "flags": {
         "json": {
@@ -1542,229 +1513,195 @@
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
-          "char": "a",
-          "description": "Use this flag to override the default API version with the API version of your package.xml file. The default API version is the latest version supported by the CLI.",
-          "name": "api-version",
-          "summary": "Target API version for the deploy.",
-          "hasDynamicHelp": false,
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "summary": "Username or alias of the target org.",
+          "hasDynamicHelp": true,
           "multiple": false,
           "type": "option"
         },
-        "async": {
-          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run \"<%= config.bin %> project deploy resume\". To check the status of the deployment, run \"<%= config.bin %> project deploy report\".",
-          "exclusive": [
-            "wait"
-          ],
-          "name": "async",
-          "summary": "Run the command asynchronously.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "concise": {
-          "exclusive": [
-            "verbose"
-          ],
-          "name": "concise",
-          "summary": "Show concise output of the deploy result.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "dry-run": {
-          "name": "dry-run",
-          "summary": "Validate deploy and run Apex tests but don’t save to the org.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "ignore-conflicts": {
-          "char": "c",
-          "description": "This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as production orgs.",
-          "name": "ignore-conflicts",
-          "summary": "Ignore conflicts and deploy local files, even if they overwrite changes in the org.",
-          "allowNo": false,
-          "type": "boolean"
+        "job-id": {
+          "char": "i",
+          "description": "These commands return a job ID if they time out or you specified the --async flag:\n\n- <%= config.bin %> project deploy start\n- <%= config.bin %> project deploy validate\n- <%= config.bin %> project deploy quick\n- <%= config.bin %> project deploy cancel\n\nThe job ID is valid for 10 days from when you started the deploy operation.",
+          "name": "job-id",
+          "summary": "Job ID of the deploy operation you want to check the status of.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "ignore-errors": {
+        "use-most-recent": {
           "char": "r",
-          "description": "Never use this flag when deploying to a production org. If you specify it, components without errors are deployed and components with errors are skipped, and could result in an inconsistent production org.",
-          "name": "ignore-errors",
-          "summary": "Ignore any errors and don’t roll back deployment.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "ignore-warnings": {
-          "char": "g",
-          "description": "If you specify this flag, and a warning occurs, the success status of the deployment is set to true. If you don't specify this flag, and a warning occurs, then the success status is set to false, and the warning is treated like an error.\n\nThis flag is useful in a CI environment and your deployment includes destructive changes; if you try to delete a component that doesn't exist in the org, you get a warning. In this case, to ensure that the command returns a success value of true, specify this flag.",
-          "name": "ignore-warnings",
-          "summary": "Ignore warnings and allow a deployment to complete successfully.",
+          "description": "For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less. If your most recent operation was more than 3 days ago, this flag won't find a job ID.",
+          "name": "use-most-recent",
+          "summary": "Use the job ID of the most recent deploy operation.",
           "allowNo": false,
           "type": "boolean"
         },
-        "manifest": {
-          "char": "x",
-          "description": "All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.",
-          "exclusive": [
-            "source-dir",
-            "metadata",
-            "metadata-dir"
-          ],
-          "helpGroup": "Source Format",
-          "name": "manifest",
-          "summary": "Full file path for manifest (package.xml) of components to deploy.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "metadata": {
-          "char": "m",
-          "exclusive": [
-            "manifest",
-            "source-dir",
-            "metadata-dir"
-          ],
-          "helpGroup": "Source Format",
-          "name": "metadata",
-          "summary": "Metadata component names to deploy. Wildcards (`*` ) supported as long as you use quotes, such as `ApexClass:MyClass*`.",
+        "coverage-formatters": {
+          "description": "For multiple formatters, repeat the flag for each formatter.\n--coverage-formatters lcov --coverage-formatters clover",
+          "helpGroup": "Test",
+          "name": "coverage-formatters",
+          "summary": "Format of the code coverage results.",
           "hasDynamicHelp": false,
           "multiple": true,
-          "type": "option"
-        },
-        "metadata-dir": {
-          "exclusive": [
-            "manifest",
-            "source-dir",
-            "metadata"
+          "options": [
+            "clover",
+            "cobertura",
+            "html-spa",
+            "html",
+            "json",
+            "json-summary",
+            "lcovonly",
+            "none",
+            "teamcity",
+            "text",
+            "text-summary"
           ],
-          "helpGroup": "Metadata API Format",
-          "name": "metadata-dir",
-          "summary": "Root of directory or zip file of metadata formatted files to deploy.",
-          "hasDynamicHelp": false,
-          "multiple": false,
           "type": "option"
         },
-        "single-package": {
-          "dependsOn": [
-            "metadata-dir"
-          ],
-          "helpGroup": "Metadata API Format",
-          "name": "single-package",
-          "summary": "Indicates that the metadata zip file points to a directory structure for a single package.",
+        "junit": {
+          "helpGroup": "Test",
+          "name": "junit",
+          "summary": "Output JUnit test results.",
           "allowNo": false,
           "type": "boolean"
         },
-        "source-dir": {
-          "char": "d",
-          "description": "The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its subdirectories).\n\nIf you specify this flag, don’t specify --metadata or --manifest.",
-          "exclusive": [
-            "manifest",
-            "metadata",
-            "metadata-dir"
+        "results-dir": {
+          "helpGroup": "Test",
+          "name": "results-dir",
+          "relationships": [
+            {
+              "type": "some",
+              "flags": [
+                "coverage-formatters",
+                "junit"
+              ]
+            }
           ],
-          "helpGroup": "Source Format",
-          "name": "source-dir",
-          "summary": "Path to the local source files to deploy.",
+          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
           "type": "option"
         },
-        "target-org": {
-          "char": "o",
-          "name": "target-org",
-          "noCacheDefault": true,
-          "required": true,
-          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+        "wait": {
+          "char": "w",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run \"<%= config.bin %> project deploy resume\". To check the status of the deployment, run \"<%= config.bin %> project deploy report\".",
+          "name": "wait",
+          "summary": "Number of minutes to wait for command to complete and display results.",
           "hasDynamicHelp": true,
+          "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "project:deploy:report",
+      "pluginAlias": "@salesforce/plugin-deploy-retrieve",
+      "pluginName": "@salesforce/plugin-deploy-retrieve",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Check or poll for the status of a deploy operation.",
+      "enableJsonFlag": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "project",
+        "deploy",
+        "report.js"
+      ],
+      "aliasPermutations": [
+        "deploy:metadata:report",
+        "metadata:deploy:report",
+        "metadata:report:deploy",
+        "deploy:report:metadata",
+        "report:deploy:metadata",
+        "report:metadata:deploy"
+      ],
+      "permutations": [
+        "project:deploy:report",
+        "deploy:project:report",
+        "deploy:report:project",
+        "project:report:deploy",
+        "report:project:deploy",
+        "report:deploy:project"
+      ]
+    },
+    "project:deploy:resume": {
+      "aliases": [
+        "deploy:metadata:resume"
+      ],
+      "args": {},
+      "deprecateAliases": true,
+      "description": "Use this command to resume watching a deploy operation if the original command times out or you specified the --async flag. Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations. This command doesn't resume the original operation itself, because the operation always continues after you've started it, regardless of whether you're watching it or not. When the deploy completes, source tracking information is updated as needed.\n\nRun this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.",
+      "examples": [
+        "Resume watching a deploy operation using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
+        "Resume watching the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --use-most-recent"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "tests": {
-          "char": "t",
-          "description": "If a test name contains a space, enclose it in double quotes.\nFor multiple test names, use one of the following formats:\n\n- Repeat the flag for multiple test names: --tests Test1 --tests Test2 --tests \"Test With Space\"\n- Separate the test names with spaces: --tests Test1 Test2 \"Test With Space\"",
-          "helpGroup": "Test",
-          "name": "tests",
-          "summary": "Apex tests to run when --test-level is RunSpecifiedTests.",
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
           "type": "option"
         },
-        "test-level": {
-          "char": "l",
-          "description": "Valid values are:\n\n- NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.\n\n- RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage.\n\n- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages. This test level is the default for production deployments that include Apex classes or triggers.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.\n\n  If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see [Running Tests in a Deployment](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the \"Metadata API Developer Guide\".",
-          "helpGroup": "Test",
-          "name": "test-level",
-          "summary": "Deployment Apex testing level.",
+        "concise": {
+          "exclusive": [
+            "verbose"
+          ],
+          "name": "concise",
+          "summary": "Show concise output of the deploy operation result.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "job-id": {
+          "char": "i",
+          "description": "These commands return a job ID if they time out or you specified the --async flag:\n\n- <%= config.bin %> project deploy start\n- <%= config.bin %> project deploy validate\n- <%= config.bin %> project deploy quick\n- <%= config.bin %> project deploy cancel\n\nThe job ID is valid for 10 days from when you started the deploy operation.",
+          "name": "job-id",
+          "summary": "Job ID of the deploy operation you want to resume.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "NoTestRun",
-            "RunSpecifiedTests",
-            "RunLocalTests",
-            "RunAllTestsInOrg"
-          ],
           "type": "option"
         },
+        "use-most-recent": {
+          "char": "r",
+          "description": "For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less. If your most recent operation was more than 3 days ago, this flag won't find a job ID.",
+          "name": "use-most-recent",
+          "summary": "Use the job ID of the most recent deploy operation.",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "verbose": {
           "exclusive": [
             "concise"
           ],
           "name": "verbose",
-          "summary": "Show verbose output of the deploy result.",
+          "summary": "Show verbose output of the deploy operation result.",
           "allowNo": false,
           "type": "boolean"
         },
         "wait": {
           "char": "w",
-          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run \"<%= config.bin %> project deploy resume\". To check the status of the deployment, run \"<%= config.bin %> project deploy report\".",
-          "exclusive": [
-            "async"
-          ],
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the deploy operation, run this command again. To check the status of the deploy operation, run \"<%= config.bin %> project deploy report\".",
           "name": "wait",
-          "summary": "Number of minutes to wait for command to complete and display results.",
+          "summary": "Number of minutes to wait for the command to complete and display results.",
           "hasDynamicHelp": true,
           "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
         },
-        "purge-on-delete": {
-          "helpGroup": "Delete",
-          "name": "purge-on-delete",
-          "relationships": [
-            {
-              "type": "some",
-              "flags": [
-                "pre-destructive-changes",
-                "manifest",
-                "metadata-dir",
-                "post-destructive-changes"
-              ]
-            }
-          ],
-          "summary": "Specify that deleted components in the destructive changes manifest file are immediately eligible for deletion rather than being stored in the Recycle Bin.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "pre-destructive-changes": {
-          "dependsOn": [
-            "manifest"
-          ],
-          "helpGroup": "Delete",
-          "name": "pre-destructive-changes",
-          "summary": "File path for a manifest (destructiveChangesPre.xml) of components to delete before the deploy.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "post-destructive-changes": {
-          "dependsOn": [
-            "manifest"
-          ],
-          "helpGroup": "Delete",
-          "name": "post-destructive-changes",
-          "summary": "File path for a manifest (destructiveChangesPost.xml) of components to delete after the deploy.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
         "coverage-formatters": {
           "description": "For multiple formatters, repeat the flag for each formatter.\n--coverage-formatters lcov --coverage-formatters clover",
           "helpGroup": "Test",
@@ -1814,33 +1751,16 @@
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:start",
+      "id": "project:deploy:resume",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Deploy metadata to an org from your local project.",
+      "summary": "Resume watching a deploy operation and update source tracking when the deploy completes.",
       "enableJsonFlag": true,
-      "configurationVariablesSection": {
-        "header": "CONFIGURATION VARIABLES",
-        "body": [
-          {
-            "name": "target-org",
-            "description": "Username or alias of the org that all commands run against by default. (sf only)"
-          },
-          {
-            "name": "org-api-version",
-            "description": "API version of your project. Default: API version of your Dev Hub org."
-          }
-        ]
-      },
       "envVariablesSection": {
         "header": "ENVIRONMENT VARIABLES",
         "body": [
-          {
-            "name": "SF_TARGET_ORG",
-            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
-          },
           {
             "name": "SF_USE_PROGRESS_BAR",
             "description": "Set to false to disable the progress bar when running the metadata deploy command."
@@ -1886,34 +1806,47 @@
         "commands",
         "project",
         "deploy",
-        "start.js"
+        "resume.js"
       ],
       "aliasPermutations": [
-        "deploy:metadata",
-        "metadata:deploy"
+        "deploy:metadata:resume",
+        "metadata:deploy:resume",
+        "metadata:resume:deploy",
+        "deploy:resume:metadata",
+        "resume:deploy:metadata",
+        "resume:metadata:deploy"
       ],
       "permutations": [
-        "project:deploy:start",
-        "deploy:project:start",
-        "deploy:start:project",
-        "project:start:deploy",
-        "start:project:deploy",
-        "start:deploy:project"
+        "project:deploy:resume",
+        "deploy:project:resume",
+        "deploy:resume:project",
+        "project:resume:deploy",
+        "resume:project:deploy",
+        "resume:deploy:project"
       ]
     },
-    "project:deploy:validate": {
+    "project:deploy:start": {
       "aliases": [
-        "deploy:metadata:validate"
+        "deploy:metadata"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "Use this command to verify whether a deployment will succeed without actually deploying the metadata to your org. This command is similar to \"<%= config.bin %> project deploy start\", except you're required to run Apex tests, and the command returns a job ID rather than executing the deployment. If the validation succeeds, then you pass this job ID to the \"<%= config.bin %> project deploy quick\" command to actually deploy the metadata. This quick deploy takes less time because it skips running Apex tests. The job ID is valid for 10 days from when you started the validation. Validating first is useful if the deployment to your production org take several hours and you don’t want to risk a failed deploy.\n\nYou must run this command from within a project.\n\nThis command doesn't support source-tracking. When you quick deploy with the resulting job ID, the source you deploy overwrites the corresponding metadata in your org.\n\nTo validate the deployment of multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --source-dir.\n\nNote: Don't use this command on sandboxes; the command is intended to be used on production orgs. By default, sandboxes don't run tests during a deploy. If you want to validate a deployment with tests on a sandbox, use \"<%= config.bin %> project deploy start --dry-run --test-level RunLocalTests\" instead.",
+      "description": "You must run this command from within a project.\n\nMetadata components are deployed in source format by default. Deploy them in metadata format by specifying the --metadata-dir flag, which specifies the root directory or ZIP file that contains the metadata formatted files you want to deploy.\n\nIf your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production orgs, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the \"<%= config.bin %> org create scratch|sandbox\" commands.\n\nTo deploy multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --source-dir.",
       "examples": [
-        "NOTE: These examples focus on validating large deployments. See the help for \"<%= config.bin %> project deploy start\" for examples of deploying smaller sets of metadata which you can also use to validate.",
-        "Validate the deployment of all source files in the \"force-app\" directory to the default org:\n<%= config.bin %> <%= command.id %> --source-dir force-app",
-        "Validate the deployment of all source files in two directories: \"force-app\" and \"force-app-utils\":\n<%= config.bin %> <%= command.id %> --source-dir force-app --source-dir force-app-utils",
-        "Asynchronously validate the deployment and run all tests in the org with alias \"my-prod-org\"; command immediately returns the job ID:\n<%= config.bin %> <%= command.id %> --source-dir force-app --async --test-level RunAllTestsInOrg --target-org my-prod-org",
-        "Validate the deployment of all components listed in a manifest:\n<%= config.bin %> <%= command.id %> --manifest path/to/package.xml"
+        "Deploy local changes not in the org; uses your default org:\n<%= config.bin %> <%= command.id %>",
+        "Deploy all source files in the \"force-app\" directory to an org with alias \"my-scratch\"; show only concise output, in other words don't print a list of all the source that was deployed:\n<%= config.bin %> <%= command.id %>  --source-dir force-app --target-org my-scratch --concise",
+        "Deploy all the Apex classes and custom objects that are in the \"force-app\" directory. The list views, layouts, etc, that are associated with the custom objects are also deployed. Both examples are equivalent:\n<%= config.bin %> <%= command.id %> --source-dir force-app/main/default/classes force-app/main/default/objects\n<%= config.bin %> <%= command.id %> --source-dir force-app/main/default/classes --source-dir force-app/main/default/objects",
+        "Deploy all Apex classes that are in all package directories defined in the \"sfdx-project.json\" file:\n<%= config.bin %> <%= command.id %> --metadata ApexClass",
+        "Deploy a specific Apex class; ignore any conflicts between the local project and org (be careful with this flag, because it will overwrite the Apex class in the org if there are conflicts!):\n<%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass --ignore-conflicts",
+        "Deploy specific Apex classes that match a pattern; in this example, deploy Apex classes whose names contain the string \"MyApex\". Also ignore any deployment warnings (again, be careful with this flag! You typically want to see the warnings):\n<%= config.bin %> <%= command.id %> --metadata 'ApexClass:MyApex*' --ignore-warnings",
+        "Deploy a custom object called ExcitingObject that's in the SBQQ namespace:\nsf <%= command.id %> --metadata CustomObject:SBQQ__ExcitingObject",
+        "Deploy all custom objects in the SBQQ namespace by using a wildcard and quotes:\nsf <%= command.id %> --metadata 'CustomObject:SBQQ__*'",
+        "Deploy all custom objects and Apex classes found in all defined package directories (both examples are equivalent):\n<%= config.bin %> <%= command.id %> --metadata CustomObject ApexClass\n<%= config.bin %> <%= command.id %> --metadata CustomObject --metadata ApexClass",
+        "Deploy all Apex classes and a profile that has a space in its name:\n<%= config.bin %> <%= command.id %> --metadata ApexClass --metadata \"Profile:My Profile\"",
+        "Deploy all components listed in a manifest:\n<%= config.bin %> <%= command.id %> --manifest path/to/package.xml",
+        "Run the tests that aren’t in any managed packages as part of a deployment:\n<%= config.bin %> <%= command.id %> --metadata ApexClass --test-level RunLocalTests",
+        "Deploy all metadata formatted files in the \"MDAPI\" directory:\n<%= config.bin %> <%= command.id %> --metadata-dir MDAPI",
+        "Deploy all metadata formatted files in the \"MDAPI\" directory; items listed in the MDAPI/destructiveChangesPre.xml and MDAPI/destructiveChangesPost.xml manifests are immediately eligible for deletion rather than stored in the Recycle Bin:\n<%= config.bin %> <%= command.id %> --metadata-dir MDAPI --purge-on-delete"
       ],
       "flags": {
         "json": {
@@ -1935,13 +1868,16 @@
           "char": "a",
           "description": "Use this flag to override the default API version with the API version of your package.xml file. The default API version is the latest version supported by the CLI.",
           "name": "api-version",
-          "summary": "Target API version for the validation.",
+          "summary": "Target API version for the deploy.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "async": {
-          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume watching the validation, run \"<%= config.bin %> project deploy resume\". To check the status of the validation, run \"<%= config.bin %> project deploy report\".",
+          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run \"<%= config.bin %> project deploy resume\". To check the status of the deployment, run \"<%= config.bin %> project deploy report\".",
+          "exclusive": [
+            "wait"
+          ],
           "name": "async",
           "summary": "Run the command asynchronously.",
           "allowNo": false,
@@ -1952,40 +1888,75 @@
             "verbose"
           ],
           "name": "concise",
-          "summary": "Show concise output of the validation result.",
+          "summary": "Show concise output of the deploy result.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "dry-run": {
+          "name": "dry-run",
+          "summary": "Validate deploy and run Apex tests but don’t save to the org.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "ignore-conflicts": {
+          "char": "c",
+          "description": "This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as production orgs.",
+          "name": "ignore-conflicts",
+          "summary": "Ignore conflicts and deploy local files, even if they overwrite changes in the org.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "ignore-errors": {
+          "char": "r",
+          "description": "Never use this flag when deploying to a production org. If you specify it, components without errors are deployed and components with errors are skipped, and could result in an inconsistent production org.",
+          "name": "ignore-errors",
+          "summary": "Ignore any errors and don’t roll back deployment.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "ignore-warnings": {
+          "char": "g",
+          "description": "If you specify this flag, and a warning occurs, the success status of the deployment is set to true. If you don't specify this flag, and a warning occurs, then the success status is set to false, and the warning is treated like an error.\n\nThis flag is useful in a CI environment and your deployment includes destructive changes; if you try to delete a component that doesn't exist in the org, you get a warning. In this case, to ensure that the command returns a success value of true, specify this flag.",
+          "name": "ignore-warnings",
+          "summary": "Ignore warnings and allow a deployment to complete successfully.",
           "allowNo": false,
           "type": "boolean"
         },
         "manifest": {
           "char": "x",
           "description": "All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.",
+          "exclusive": [
+            "source-dir",
+            "metadata",
+            "metadata-dir"
+          ],
           "helpGroup": "Source Format",
           "name": "manifest",
-          "summary": "Full file path for manifest (package.xml) of components to validate for deployment.",
+          "summary": "Full file path for manifest (package.xml) of components to deploy.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "metadata": {
           "char": "m",
+          "exclusive": [
+            "manifest",
+            "source-dir",
+            "metadata-dir"
+          ],
           "helpGroup": "Source Format",
           "name": "metadata",
-          "summary": "Metadata component names to validate for deployment.",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "source-dir": {
-          "char": "d",
-          "description": "The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its subdirectories).\n\nIf you specify this flag, don’t specify --metadata or --manifest.",
-          "helpGroup": "Source Format",
-          "name": "source-dir",
-          "summary": "Path to the local source files to validate for deployment.",
+          "summary": "Metadata component names to deploy. Wildcards (`*` ) supported as long as you use quotes, such as `ApexClass:MyClass*`.",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
         },
         "metadata-dir": {
+          "exclusive": [
+            "manifest",
+            "source-dir",
+            "metadata"
+          ],
           "helpGroup": "Metadata API Format",
           "name": "metadata-dir",
           "summary": "Root of directory or zip file of metadata formatted files to deploy.",
@@ -2003,6 +1974,21 @@
           "allowNo": false,
           "type": "boolean"
         },
+        "source-dir": {
+          "char": "d",
+          "description": "The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its subdirectories).\n\nIf you specify this flag, don’t specify --metadata or --manifest.",
+          "exclusive": [
+            "manifest",
+            "metadata",
+            "metadata-dir"
+          ],
+          "helpGroup": "Source Format",
+          "name": "source-dir",
+          "summary": "Path to the local source files to deploy.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
         "target-org": {
           "char": "o",
           "name": "target-org",
@@ -2025,17 +2011,17 @@
         },
         "test-level": {
           "char": "l",
-          "description": "Valid values are:\n\n- RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage.\n\n- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages. This test level is the default.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.",
+          "description": "Valid values are:\n\n- NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.\n\n- RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage.\n\n- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages. This test level is the default for production deployments that include Apex classes or triggers.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.\n\n  If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see [Running Tests in a Deployment](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the \"Metadata API Developer Guide\".",
           "helpGroup": "Test",
           "name": "test-level",
           "summary": "Deployment Apex testing level.",
-          "default": "RunLocalTests",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
-            "RunAllTestsInOrg",
+            "NoTestRun",
+            "RunSpecifiedTests",
             "RunLocalTests",
-            "RunSpecifiedTests"
+            "RunAllTestsInOrg"
           ],
           "type": "option"
         },
@@ -2044,28 +2030,63 @@
             "concise"
           ],
           "name": "verbose",
-          "summary": "Show verbose output of the validation result.",
+          "summary": "Show verbose output of the deploy result.",
           "allowNo": false,
           "type": "boolean"
         },
         "wait": {
           "char": "w",
-          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume watching the validation, run \"<%= config.bin %> project deploy resume\". To check the status of the validation, run \"<%= config.bin %> project deploy report\".",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run \"<%= config.bin %> project deploy resume\". To check the status of the deployment, run \"<%= config.bin %> project deploy report\".",
+          "exclusive": [
+            "async"
+          ],
           "name": "wait",
-          "summary": "Number of minutes to wait for the command to complete and display results.",
+          "summary": "Number of minutes to wait for command to complete and display results.",
           "hasDynamicHelp": true,
           "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
         },
-        "ignore-warnings": {
-          "char": "g",
-          "description": "If you specify this flag, and a warning occurs, the success status of the deployment is set to true. If you don't specify this flag, and a warning occurs, then the success status is set to false, and the warning is treated like an error.\n\nThis flag is useful in a CI environment and your deployment includes destructive changes; if you try to delete a component that doesn't exist in the org, you get a warning. In this case, to ensure that the command returns a success value of true, specify this flag.",
-          "name": "ignore-warnings",
-          "summary": "Ignore warnings and allow a deployment to complete successfully.",
+        "purge-on-delete": {
+          "helpGroup": "Delete",
+          "name": "purge-on-delete",
+          "relationships": [
+            {
+              "type": "some",
+              "flags": [
+                "pre-destructive-changes",
+                "manifest",
+                "metadata-dir",
+                "post-destructive-changes"
+              ]
+            }
+          ],
+          "summary": "Specify that deleted components in the destructive changes manifest file are immediately eligible for deletion rather than being stored in the Recycle Bin.",
           "allowNo": false,
           "type": "boolean"
         },
+        "pre-destructive-changes": {
+          "dependsOn": [
+            "manifest"
+          ],
+          "helpGroup": "Delete",
+          "name": "pre-destructive-changes",
+          "summary": "File path for a manifest (destructiveChangesPre.xml) of components to delete before the deploy.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "post-destructive-changes": {
+          "dependsOn": [
+            "manifest"
+          ],
+          "helpGroup": "Delete",
+          "name": "post-destructive-changes",
+          "summary": "File path for a manifest (destructiveChangesPost.xml) of components to delete after the deploy.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
         "coverage-formatters": {
           "description": "For multiple formatters, repeat the flag for each formatter.\n--coverage-formatters lcov --coverage-formatters clover",
           "helpGroup": "Test",
@@ -2111,57 +2132,16 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        },
-        "purge-on-delete": {
-          "dependsOn": [
-            "manifest"
-          ],
-          "helpGroup": "Delete",
-          "name": "purge-on-delete",
-          "relationships": [
-            {
-              "type": "some",
-              "flags": [
-                "pre-destructive-changes",
-                "post-destructive-changes"
-              ]
-            }
-          ],
-          "summary": "Specify that deleted components in the destructive changes manifest file are immediately eligible for deletion rather than being stored in the Recycle Bin.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "pre-destructive-changes": {
-          "dependsOn": [
-            "manifest"
-          ],
-          "helpGroup": "Delete",
-          "name": "pre-destructive-changes",
-          "summary": "File path for a manifest (destructiveChangesPre.xml) of components to delete before the deploy",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "post-destructive-changes": {
-          "dependsOn": [
-            "manifest"
-          ],
-          "helpGroup": "Delete",
-          "name": "post-destructive-changes",
-          "summary": "File path for a manifest (destructiveChangesPost.xml) of components to delete after the deploy.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:validate",
+      "id": "project:deploy:start",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Validate a metadata deployment without actually executing it.",
+      "summary": "Deploy metadata to an org from your local project.",
       "enableJsonFlag": true,
       "configurationVariablesSection": {
         "header": "CONFIGURATION VARIABLES",
@@ -2228,39 +2208,34 @@
         "commands",
         "project",
         "deploy",
-        "validate.js"
+        "start.js"
       ],
       "aliasPermutations": [
-        "deploy:metadata:validate",
-        "metadata:deploy:validate",
-        "metadata:validate:deploy",
-        "deploy:validate:metadata",
-        "validate:deploy:metadata",
-        "validate:metadata:deploy"
+        "deploy:metadata",
+        "metadata:deploy"
       ],
       "permutations": [
-        "project:deploy:validate",
-        "deploy:project:validate",
-        "deploy:validate:project",
-        "project:validate:deploy",
-        "validate:project:deploy",
-        "validate:deploy:project"
+        "project:deploy:start",
+        "deploy:project:start",
+        "deploy:start:project",
+        "project:start:deploy",
+        "start:project:deploy",
+        "start:deploy:project"
       ]
     },
-    "project:generate:manifest": {
+    "project:deploy:validate": {
       "aliases": [
-        "force:source:manifest:create"
+        "deploy:metadata:validate"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-dir). You can specify either of these flags, not both.\n\nUse --type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this flag, and their respective file names, are:\n\n    * package : package.xml (default)\n    * pre : destructiveChangesPre.xml\n    * post : destructiveChangesPost.xml\n    * destroy : destructiveChanges.xml\n\nSee https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files.\n\nUse --name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --type or --name, but not both.\n\nTo include multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --include-packages and --source-dir.\n\nTo build a manifest from the metadata in an org, use the --from-org flag. You can combine --from-org with the --metadata flag to include only certain metadata types, or with the --excluded-metadata flag to exclude certain metadata types. When building a manifest from an org, the command makes many concurrent API calls to discover the metadata that exists in the org. To limit the number of concurrent requests, use the SF_LIST_METADATA_BATCH_SIZE environment variable and set it to a size that works best for your org and environment. If you experience timeouts or inconsistent manifest contents, then setting this environment variable can improve accuracy. However, the command takes longer to run because it sends fewer requests at a time.",
+      "description": "Use this command to verify whether a deployment will succeed without actually deploying the metadata to your org. This command is similar to \"<%= config.bin %> project deploy start\", except you're required to run Apex tests, and the command returns a job ID rather than executing the deployment. If the validation succeeds, then you pass this job ID to the \"<%= config.bin %> project deploy quick\" command to actually deploy the metadata. This quick deploy takes less time because it skips running Apex tests. The job ID is valid for 10 days from when you started the validation. Validating first is useful if the deployment to your production org take several hours and you don’t want to risk a failed deploy.\n\nYou must run this command from within a project.\n\nThis command doesn't support source-tracking. When you quick deploy with the resulting job ID, the source you deploy overwrites the corresponding metadata in your org.\n\nTo validate the deployment of multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --source-dir.\n\nNote: Don't use this command on sandboxes; the command is intended to be used on production orgs. By default, sandboxes don't run tests during a deploy. If you want to validate a deployment with tests on a sandbox, use \"<%= config.bin %> project deploy start --dry-run --test-level RunLocalTests\" instead.",
       "examples": [
-        "Create a manifest for deploying or retrieving all Apex classes and custom objects:\n$ <%= config.bin %> <%= command.id %> --metadata ApexClass --metadata CustomObject",
-        "Create a manifest for deleting the specified Apex class:\n$ <%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass --type destroy",
-        "Create a manifest for deploying or retrieving all the metadata components in the specified local directory; name the file myNewManifest.xml:\n$ <%= config.bin %> <%= command.id %> --source-dir force-app --name myNewManifest",
-        "Create a manifest from the metadata components in the specified org and include metadata in any unlocked packages:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --include-packages unlocked",
-        "Create a manifest from specific metadata types in an org:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --metadata ApexClass,CustomObject,CustomLabels",
-        "Create a manifest from all metadata components in an org excluding specific metadata types:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --excluded-metadata StandardValueSet"
+        "NOTE: These examples focus on validating large deployments. See the help for \"<%= config.bin %> project deploy start\" for examples of deploying smaller sets of metadata which you can also use to validate.",
+        "Validate the deployment of all source files in the \"force-app\" directory to the default org:\n<%= config.bin %> <%= command.id %> --source-dir force-app",
+        "Validate the deployment of all source files in two directories: \"force-app\" and \"force-app-utils\":\n<%= config.bin %> <%= command.id %> --source-dir force-app --source-dir force-app-utils",
+        "Asynchronously validate the deployment and run all tests in the org with alias \"my-prod-org\"; command immediately returns the job ID:\n<%= config.bin %> <%= command.id %> --source-dir force-app --async --test-level RunAllTestsInOrg --target-org my-prod-org",
+        "Validate the deployment of all components listed in a manifest:\n<%= config.bin %> <%= command.id %> --manifest path/to/package.xml"
       ],
       "flags": {
         "json": {
@@ -2279,294 +2254,319 @@
           "type": "option"
         },
         "api-version": {
-          "aliases": [
-            "apiversion"
-          ],
-          "deprecateAliases": true,
-          "description": "Override the api version used for api requests made by this command",
+          "char": "a",
+          "description": "Use this flag to override the default API version with the API version of your package.xml file. The default API version is the latest version supported by the CLI.",
           "name": "api-version",
+          "summary": "Target API version for the validation.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "loglevel": {
-          "deprecated": {
-            "message": "The loglevel flag is no longer in use on this command. You may use it without error, but it will be ignored.\nSet the log level using the `SFDX_LOG_LEVEL` environment variable."
-          },
-          "hidden": true,
-          "name": "loglevel",
+        "async": {
+          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume watching the validation, run \"<%= config.bin %> project deploy resume\". To check the status of the validation, run \"<%= config.bin %> project deploy report\".",
+          "name": "async",
+          "summary": "Run the command asynchronously.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "concise": {
+          "exclusive": [
+            "verbose"
+          ],
+          "name": "concise",
+          "summary": "Show concise output of the validation result.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "manifest": {
+          "char": "x",
+          "description": "All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.",
+          "helpGroup": "Source Format",
+          "name": "manifest",
+          "summary": "Full file path for manifest (package.xml) of components to validate for deployment.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "metadata": {
           "char": "m",
+          "helpGroup": "Source Format",
           "name": "metadata",
-          "summary": "Names of metadata components to include in the manifest.",
-          "delimiter": ",",
+          "summary": "Metadata component names to validate for deployment.",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
         },
         "source-dir": {
-          "aliases": [
-            "sourcepath"
-          ],
-          "char": "p",
-          "deprecateAliases": true,
+          "char": "d",
+          "description": "The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its subdirectories).\n\nIf you specify this flag, don’t specify --metadata or --manifest.",
+          "helpGroup": "Source Format",
           "name": "source-dir",
-          "summary": "Paths to the local source files to include in the manifest.",
-          "delimiter": ",",
+          "summary": "Path to the local source files to validate for deployment.",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
         },
-        "name": {
-          "aliases": [
-            "manifestname"
-          ],
-          "char": "n",
-          "deprecateAliases": true,
-          "exclusive": [
-            "type"
-          ],
-          "name": "name",
-          "summary": "Name of a custom manifest file to create.",
+        "metadata-dir": {
+          "helpGroup": "Metadata API Format",
+          "name": "metadata-dir",
+          "summary": "Root of directory or zip file of metadata formatted files to deploy.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "type": {
-          "aliases": [
-            "manifesttype"
+        "single-package": {
+          "dependsOn": [
+            "metadata-dir"
           ],
+          "helpGroup": "Metadata API Format",
+          "name": "single-package",
+          "summary": "Indicates that the metadata zip file points to a directory structure for a single package.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "tests": {
           "char": "t",
-          "deprecateAliases": true,
-          "exclusive": [
-            "name"
-          ],
-          "name": "type",
-          "summary": "Type of manifest to create; the type determines the name of the created file.",
+          "description": "If a test name contains a space, enclose it in double quotes.\nFor multiple test names, use one of the following formats:\n\n- Repeat the flag for multiple test names: --tests Test1 --tests Test2 --tests \"Test With Space\"\n- Separate the test names with spaces: --tests Test1 Test2 \"Test With Space\"",
+          "helpGroup": "Test",
+          "name": "tests",
+          "summary": "Apex tests to run when --test-level is RunSpecifiedTests.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "test-level": {
+          "char": "l",
+          "description": "Valid values are:\n\n- RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage.\n\n- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages. This test level is the default.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.",
+          "helpGroup": "Test",
+          "name": "test-level",
+          "summary": "Deployment Apex testing level.",
+          "default": "RunLocalTests",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
-            "pre",
-            "post",
-            "destroy",
-            "package"
+            "RunAllTestsInOrg",
+            "RunLocalTests",
+            "RunSpecifiedTests"
           ],
           "type": "option"
         },
-        "include-packages": {
-          "aliases": [
-            "includepackages"
-          ],
-          "char": "c",
-          "dependsOn": [
-            "from-org"
+        "verbose": {
+          "exclusive": [
+            "concise"
           ],
-          "deprecateAliases": true,
-          "name": "include-packages",
-          "summary": "Package types (managed, unlocked) whose metadata is included in the manifest; by default, metadata in managed and unlocked packages is excluded. Metadata in unmanaged packages is always included.",
-          "delimiter": ",",
+          "name": "verbose",
+          "summary": "Show verbose output of the validation result.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "wait": {
+          "char": "w",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume watching the validation, run \"<%= config.bin %> project deploy resume\". To check the status of the validation, run \"<%= config.bin %> project deploy report\".",
+          "name": "wait",
+          "summary": "Number of minutes to wait for the command to complete and display results.",
+          "hasDynamicHelp": true,
+          "helpValue": "<minutes>",
+          "multiple": false,
+          "type": "option"
+        },
+        "ignore-warnings": {
+          "char": "g",
+          "description": "If you specify this flag, and a warning occurs, the success status of the deployment is set to true. If you don't specify this flag, and a warning occurs, then the success status is set to false, and the warning is treated like an error.\n\nThis flag is useful in a CI environment and your deployment includes destructive changes; if you try to delete a component that doesn't exist in the org, you get a warning. In this case, to ensure that the command returns a success value of true, specify this flag.",
+          "name": "ignore-warnings",
+          "summary": "Ignore warnings and allow a deployment to complete successfully.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "coverage-formatters": {
+          "description": "For multiple formatters, repeat the flag for each formatter.\n--coverage-formatters lcov --coverage-formatters clover",
+          "helpGroup": "Test",
+          "name": "coverage-formatters",
+          "summary": "Format of the code coverage results.",
           "hasDynamicHelp": false,
           "multiple": true,
           "options": [
-            "managed",
-            "unlocked"
+            "clover",
+            "cobertura",
+            "html-spa",
+            "html",
+            "json",
+            "json-summary",
+            "lcovonly",
+            "none",
+            "teamcity",
+            "text",
+            "text-summary"
           ],
           "type": "option"
         },
-        "excluded-metadata": {
-          "name": "excluded-metadata",
+        "junit": {
+          "helpGroup": "Test",
+          "name": "junit",
+          "summary": "Output JUnit test results.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "results-dir": {
+          "helpGroup": "Test",
+          "name": "results-dir",
           "relationships": [
             {
               "type": "some",
               "flags": [
-                "from-org",
-                "source-dir"
+                "coverage-formatters",
+                "junit"
               ]
             }
           ],
-          "summary": "Metadata types to exclude when building a manifest from an org. Specify the name of the type, not the name of a specific component.",
-          "delimiter": ",",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "from-org": {
-          "aliases": [
-            "fromorg"
-          ],
-          "deprecateAliases": true,
-          "exclusive": [
-            "source-dir"
-          ],
-          "name": "from-org",
-          "summary": "Username or alias of the org that contains the metadata components from which to build a manifest.",
+          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "output-dir": {
-          "aliases": [
-            "outputdir",
-            "o"
+        "purge-on-delete": {
+          "dependsOn": [
+            "manifest"
           ],
-          "char": "d",
-          "deprecateAliases": true,
-          "name": "output-dir",
-          "summary": "Directory to save the created manifest.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "project:generate:manifest",
-      "pluginAlias": "@salesforce/plugin-deploy-retrieve",
-      "pluginName": "@salesforce/plugin-deploy-retrieve",
-      "pluginType": "core",
-      "strict": true,
-      "summary": "Create a project manifest that lists the metadata components you want to deploy or retrieve.",
-      "enableJsonFlag": true,
-      "requiresProject": true,
-      "isESM": true,
-      "relativePath": [
-        "lib",
-        "commands",
-        "project",
-        "generate",
-        "manifest.js"
-      ],
-      "aliasPermutations": [
-        "force:source:manifest:create",
-        "source:force:manifest:create",
-        "source:manifest:force:create",
-        "source:manifest:create:force",
-        "force:manifest:source:create",
-        "manifest:force:source:create",
-        "manifest:source:force:create",
-        "manifest:source:create:force",
-        "force:manifest:create:source",
-        "manifest:force:create:source",
-        "manifest:create:force:source",
-        "manifest:create:source:force",
-        "force:source:create:manifest",
-        "source:force:create:manifest",
-        "source:create:force:manifest",
-        "source:create:manifest:force",
-        "force:create:source:manifest",
-        "create:force:source:manifest",
-        "create:source:force:manifest",
-        "create:source:manifest:force",
-        "force:create:manifest:source",
-        "create:force:manifest:source",
-        "create:manifest:force:source",
-        "create:manifest:source:force"
-      ],
-      "permutations": [
-        "project:generate:manifest",
-        "generate:project:manifest",
-        "generate:manifest:project",
-        "project:manifest:generate",
-        "manifest:project:generate",
-        "manifest:generate:project"
-      ]
-    },
-    "project:list:ignored": {
-      "aliases": [
-        "force:source:ignored:list"
-      ],
-      "args": {},
-      "deprecateAliases": true,
-      "description": "When deploying or retrieving metadata between your local project and an org, you can specify the source files you want to exclude with a .forceignore file. The .forceignore file structure mimics the .gitignore structure. Each line in .forceignore specifies a pattern that corresponds to one or more files. The files typically represent metadata components, but can be any files you want to exclude, such as LWC configuration JSON files or tests.",
-      "examples": [
-        "List all the files in all package directories that are ignored:\n<%= config.bin %> <%= command.id %>",
-        "List all the files in a specific directory that are ignored:\n<%= config.bin %> <%= command.id %> --source-dir force-app",
-        "Check if a particular file is ignored:\n<%= config.bin %> <%= command.id %> --source-dir package.xml"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
+          "helpGroup": "Delete",
+          "name": "purge-on-delete",
+          "relationships": [
+            {
+              "type": "some",
+              "flags": [
+                "pre-destructive-changes",
+                "post-destructive-changes"
+              ]
+            }
+          ],
+          "summary": "Specify that deleted components in the destructive changes manifest file are immediately eligible for deletion rather than being stored in the Recycle Bin.",
           "allowNo": false,
           "type": "boolean"
         },
-        "flags-dir": {
-          "helpGroup": "GLOBAL",
-          "name": "flags-dir",
-          "summary": "Import flag values from a directory.",
+        "pre-destructive-changes": {
+          "dependsOn": [
+            "manifest"
+          ],
+          "helpGroup": "Delete",
+          "name": "pre-destructive-changes",
+          "summary": "File path for a manifest (destructiveChangesPre.xml) of components to delete before the deploy",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "source-dir": {
-          "aliases": [
-            "sourcepath"
+        "post-destructive-changes": {
+          "dependsOn": [
+            "manifest"
           ],
-          "char": "p",
-          "deprecateAliases": true,
-          "name": "source-dir",
-          "summary": "File or directory of files that the command checks for foreceignored files.",
+          "helpGroup": "Delete",
+          "name": "post-destructive-changes",
+          "summary": "File path for a manifest (destructiveChangesPost.xml) of components to delete after the deploy.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:list:ignored",
+      "id": "project:deploy:validate",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Check your local project package directories for forceignored files.",
+      "summary": "Validate a metadata deployment without actually executing it.",
       "enableJsonFlag": true,
-      "requiresProject": true,
+      "configurationVariablesSection": {
+        "header": "CONFIGURATION VARIABLES",
+        "body": [
+          {
+            "name": "target-org",
+            "description": "Username or alias of the org that all commands run against by default. (sf only)"
+          },
+          {
+            "name": "org-api-version",
+            "description": "API version of your project. Default: API version of your Dev Hub org."
+          }
+        ]
+      },
+      "envVariablesSection": {
+        "header": "ENVIRONMENT VARIABLES",
+        "body": [
+          {
+            "name": "SF_TARGET_ORG",
+            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
+          },
+          {
+            "name": "SF_USE_PROGRESS_BAR",
+            "description": "Set to false to disable the progress bar when running the metadata deploy command."
+          }
+        ]
+      },
+      "errorCodes": {
+        "header": "ERROR CODES",
+        "body": [
+          {
+            "name": "Succeeded (0)",
+            "description": "The deploy succeeded."
+          },
+          {
+            "name": "Canceled (1)",
+            "description": "The deploy was canceled."
+          },
+          {
+            "name": "Failed (1)",
+            "description": "The deploy failed."
+          },
+          {
+            "name": "SucceededPartial (68)",
+            "description": "The deploy partially succeeded."
+          },
+          {
+            "name": "InProgress (69)",
+            "description": "The deploy is in progress."
+          },
+          {
+            "name": "Pending (69)",
+            "description": "The deploy is pending."
+          },
+          {
+            "name": "Canceling (69)",
+            "description": "The deploy is being canceled."
+          }
+        ]
+      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "project",
-        "list",
-        "ignored.js"
+        "deploy",
+        "validate.js"
       ],
       "aliasPermutations": [
-        "force:source:ignored:list",
-        "source:force:ignored:list",
-        "source:ignored:force:list",
-        "source:ignored:list:force",
-        "force:ignored:source:list",
-        "ignored:force:source:list",
-        "ignored:source:force:list",
-        "ignored:source:list:force",
-        "force:ignored:list:source",
-        "ignored:force:list:source",
-        "ignored:list:force:source",
-        "ignored:list:source:force",
-        "force:source:list:ignored",
-        "source:force:list:ignored",
-        "source:list:force:ignored",
-        "source:list:ignored:force",
-        "force:list:source:ignored",
-        "list:force:source:ignored",
-        "list:source:force:ignored",
-        "list:source:ignored:force",
-        "force:list:ignored:source",
-        "list:force:ignored:source",
-        "list:ignored:force:source",
-        "list:ignored:source:force"
+        "deploy:metadata:validate",
+        "metadata:deploy:validate",
+        "metadata:validate:deploy",
+        "deploy:validate:metadata",
+        "validate:deploy:metadata",
+        "validate:metadata:deploy"
       ],
       "permutations": [
-        "project:list:ignored",
-        "list:project:ignored",
-        "list:ignored:project",
-        "project:ignored:list",
-        "ignored:project:list",
-        "ignored:list:project"
+        "project:deploy:validate",
+        "deploy:project:validate",
+        "deploy:validate:project",
+        "project:validate:deploy",
+        "validate:project:deploy",
+        "validate:deploy:project"
       ]
     },
     "project:reset:tracking": {
@@ -3051,5 +3051,5 @@
       ]
     }
   },
-  "version": "3.22.30"
+  "version": "3.22.32"
 }