@salesforce/plugin-deploy-retrieve 3.22.36 → 3.22.38-dev.0

package/oclif.manifest.json

@@ -405,18 +405,16 @@
         "source:convert:project"
       ]
     },
-    "project:delete:source": {
+    "project:deploy:cancel": {
       "aliases": [
-        "force:source:delete"
+        "deploy:metadata:cancel"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "Use this command to delete components from orgs that don’t have source tracking. To remove deleted items from orgs that have source tracking enabled, \"<%= config.bin %> project deploy start\".\n\nWhen you run this command, both the local source file and the metadata component in the org are deleted.\n\nTo delete 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": "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": [
-        "Delete all local Apex source files and all Apex classes from the org with alias \"my-scratch\":\n<%= config.bin %> <%= command.id %> --metadata ApexClass --target-org my-scratch",
-        "Delete a specific Apex class and a Profile that has a space in it from your default org; don't prompt for confirmation:\n<%= config.bin %> <%= command.id %> --metadata ApexClass:MyFabulousApexClass --metadata \"Profile: My Profile\" --no-prompt",
-        "Run the tests that aren’t in any managed packages as part of the deletion; if the delete succeeds, and the org has source-tracking enabled, update the source tracking information:\n<%= config.bin %> <%= command.id %> --metadata ApexClass --test-level RunLocalTests --track-source",
-        "Delete the Apex source files in a directory and the corresponding components from your default org:\n<%= config.bin %> <%= command.id %> --source-dir force-app/main/default/classes"
+        "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": {
@@ -434,206 +432,103 @@
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
-          "aliases": [
-            "apiversion"
-          ],
-          "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"
-        },
         "target-org": {
-          "aliases": [
-            "targetusername",
-            "u"
-          ],
           "char": "o",
-          "deprecateAliases": true,
           "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.",
+          "summary": "Username or alias of the target org.",
           "hasDynamicHelp": true,
           "multiple": false,
           "type": "option"
         },
-        "check-only": {
-          "aliases": [
-            "checkonly"
+        "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"
           ],
-          "char": "c",
-          "deprecateAliases": true,
-          "description": "IMPORTANT: Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.\n\nValidates the deleted metadata and runs all Apex tests, but prevents the deletion from being saved to the org.\n\nIf you change a field type from Master-Detail to Lookup or vice versa, that change isn’t supported when using the --check-only flag to test a deletion (validation). This kind of change isn’t supported for test deletions to avoid the risk of data loss or corruption. If a change that isn’t supported for test deletions is included in a deletion package, the test deletion fails and issues an error.\n\nIf your deletion package changes a field type from Master-Detail to Lookup or vice versa, you can still validate the changes prior to deploying to Production by performing a full deletion to another test Sandbox. A full deletion includes a validation of the changes as part of the deletion process.\n\nNote: A Metadata API deletion that includes Master-Detail relationships deletes all detail records in the Recycle Bin in the following cases.\n\n    1. For a deletion with a new Master-Detail field, soft delete (send to the Recycle Bin) all detail records before proceeding to delete the Master-Detail field, or the deletion fails. During the deletion, detail records are permanently deleted from the Recycle Bin and cannot be recovered.\n\n    2. For a deletion that converts a Lookup field relationship to a Master-Detail relationship, detail records must reference a master record or be soft-deleted (sent to the Recycle Bin) for the deletion to succeed. However, a successful deletion permanently deletes any detail records in the Recycle Bin.",
-          "name": "check-only",
-          "summary": "Validate delete command but don't delete anything from the org or the local project.",
+          "name": "async",
+          "summary": "Run the command asynchronously.",
           "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.",
-          "name": "wait",
-          "summary": "Number of minutes to wait for the command to finish.",
-          "hasDynamicHelp": true,
-          "multiple": false,
-          "type": "option"
-        },
-        "tests": {
-          "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": {
-          "aliases": [
-            "testlevel"
-          ],
-          "char": "l",
-          "deprecateAliases": true,
-          "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\nIf 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” in the Metadata API Developer Guide.",
-          "helpGroup": "Test",
-          "name": "test-level",
-          "summary": "Deployment Apex testing level.",
+        "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.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "NoTestRun",
-            "RunSpecifiedTests",
-            "RunLocalTests",
-            "RunAllTestsInOrg"
-          ],
           "type": "option"
         },
-        "no-prompt": {
-          "aliases": [
-            "noprompt"
-          ],
+        "use-most-recent": {
           "char": "r",
-          "deprecateAliases": true,
-          "name": "no-prompt",
-          "summary": "Don't prompt for delete confirmation.",
+          "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"
         },
-        "metadata": {
-          "char": "m",
-          "description": "If you specify this flag, don’t specify --source-dir.",
-          "name": "metadata",
-          "summary": "Metadata components to delete.",
-          "delimiter": ",",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "source-dir": {
-          "aliases": [
-            "sourcepath"
-          ],
-          "char": "p",
-          "deprecateAliases": true,
-          "description": "The supplied paths can be a single file (in which case the operation is applied to only one file) or a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories).\n\nIf you specify this flag, don’t specify --metadata.",
-          "name": "source-dir",
-          "summary": "Source file paths to delete.",
-          "delimiter": ",",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "track-source": {
-          "aliases": [
-            "tracksource"
-          ],
-          "char": "t",
-          "deprecateAliases": true,
+        "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": [
-            "check-only"
-          ],
-          "name": "track-source",
-          "summary": "If the delete succeeds, update the source tracking information.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "force-overwrite": {
-          "aliases": [
-            "forceoverwrite"
-          ],
-          "char": "f",
-          "dependsOn": [
-            "track-source"
+            "async"
           ],
-          "deprecateAliases": true,
-          "name": "force-overwrite",
-          "summary": "Ignore conflict warnings and overwrite changes to the org.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "verbose": {
-          "name": "verbose",
-          "summary": "Verbose output of the delete result.",
-          "allowNo": false,
-          "type": "boolean"
+          "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:delete:source",
+      "id": "project:deploy:cancel",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Delete source from your project and from a non-source-tracked org.",
+      "summary": "Cancel a deploy operation.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "project",
-        "delete",
-        "source.js"
+        "deploy",
+        "cancel.js"
       ],
       "aliasPermutations": [
-        "force:source:delete",
-        "source:force:delete",
-        "source:delete:force",
-        "force:delete:source",
-        "delete:force:source",
-        "delete:source:force"
+        "deploy:metadata:cancel",
+        "metadata:deploy:cancel",
+        "metadata:cancel:deploy",
+        "deploy:cancel:metadata",
+        "cancel:deploy:metadata",
+        "cancel:metadata:deploy"
       ],
       "permutations": [
-        "project:delete:source",
-        "delete:project:source",
-        "delete:source:project",
-        "project:source:delete",
-        "source:project:delete",
-        "source:delete:project"
+        "project:deploy:cancel",
+        "deploy:project:cancel",
+        "deploy:cancel:project",
+        "project:cancel:deploy",
+        "cancel:project:deploy",
+        "cancel:deploy:project"
       ]
     },
-    "project:delete:tracking": {
+    "project:deploy:preview": {
       "aliases": [
-        "force:source:tracking:clear"
+        "deploy:metadata:preview"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "WARNING: This command deletes or overwrites all existing source tracking files. Use with extreme caution.\n\nDeletes all local source tracking information. When you next run 'project deploy preview', Salesforce CLI displays all local and remote files as changed, and any files with the same name are listed as conflicts.",
+      "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": [
-        "Delete local source tracking for the org with alias \"my-scratch\":\n$ <%= config.bin %> <%= command.id %> --target-org my-scratch"
+        "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": {
@@ -651,279 +546,37 @@
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
-          "aliases": [
-            "apiversion"
+        "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"
           ],
-          "deprecateAliases": true,
-          "description": "Override the api version used for api requests made by this command",
-          "name": "api-version",
+          "name": "manifest",
+          "summary": "Full file path for manifest (package.xml) of components to preview.",
           "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",
+        "metadata": {
+          "char": "m",
+          "exclusive": [
+            "manifest",
+            "source-dir"
+          ],
+          "name": "metadata",
+          "summary": "Metadata component names to preview.",
           "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "target-org": {
-          "aliases": [
-            "targetusername",
-            "u"
-          ],
-          "char": "o",
-          "deprecateAliases": true,
-          "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"
-        },
-        "no-prompt": {
-          "aliases": [
-            "noprompt"
-          ],
-          "char": "p",
-          "deprecateAliases": true,
-          "name": "no-prompt",
-          "summary": "Don't prompt for source tracking override confirmation.",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": true,
-      "hiddenAliases": [],
-      "id": "project:delete:tracking",
-      "pluginAlias": "@salesforce/plugin-deploy-retrieve",
-      "pluginName": "@salesforce/plugin-deploy-retrieve",
-      "pluginType": "core",
-      "strict": true,
-      "summary": "Delete all local source tracking information.",
-      "enableJsonFlag": true,
-      "requiresProject": true,
-      "isESM": true,
-      "relativePath": [
-        "lib",
-        "commands",
-        "project",
-        "delete",
-        "tracking.js"
-      ],
-      "aliasPermutations": [
-        "force:source:tracking:clear",
-        "source:force:tracking:clear",
-        "source:tracking:force:clear",
-        "source:tracking:clear:force",
-        "force:tracking:source:clear",
-        "tracking:force:source:clear",
-        "tracking:source:force:clear",
-        "tracking:source:clear:force",
-        "force:tracking:clear:source",
-        "tracking:force:clear:source",
-        "tracking:clear:force:source",
-        "tracking:clear:source:force",
-        "force:source:clear:tracking",
-        "source:force:clear:tracking",
-        "source:clear:force:tracking",
-        "source:clear:tracking:force",
-        "force:clear:source:tracking",
-        "clear:force:source:tracking",
-        "clear:source:force:tracking",
-        "clear:source:tracking:force",
-        "force:clear:tracking:source",
-        "clear:force:tracking:source",
-        "clear:tracking:force:source",
-        "clear:tracking:source:force"
-      ],
-      "permutations": [
-        "project:delete:tracking",
-        "delete:project:tracking",
-        "delete:tracking:project",
-        "project:tracking:delete",
-        "tracking:project:delete",
-        "tracking:delete:project"
-      ]
-    },
-    "project:deploy:cancel": {
-      "aliases": [
-        "deploy:metadata:cancel"
-      ],
-      "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.",
-      "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"
-      ],
-      "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"
-        },
-        "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"
-          ],
-          "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.",
-          "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,
-      "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"
-        },
-        "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"
-          ],
-          "name": "manifest",
-          "summary": "Full file path for manifest (package.xml) of components to preview.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "metadata": {
-          "char": "m",
-          "exclusive": [
-            "manifest",
-            "source-dir"
-          ],
-          "name": "metadata",
-          "summary": "Metadata component names to preview.",
-          "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": true,
           "type": "option"
         },
         "source-dir": {
@@ -1429,16 +1082,418 @@
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:resume",
+      "id": "project:deploy:resume",
+      "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.",
+      "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": [
+          {
+            "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",
+        "deploy",
+        "resume.js"
+      ],
+      "aliasPermutations": [
+        "deploy:metadata:resume",
+        "metadata:deploy:resume",
+        "metadata:resume:deploy",
+        "deploy:resume:metadata",
+        "resume:deploy:metadata",
+        "resume:metadata:deploy"
+      ],
+      "permutations": [
+        "project:deploy:resume",
+        "deploy:project:resume",
+        "deploy:resume:project",
+        "project:resume:deploy",
+        "resume:project:deploy",
+        "resume:deploy:project"
+      ]
+    },
+    "project:deploy:start": {
+      "aliases": [
+        "deploy:metadata"
+      ],
+      "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.",
+      "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"
+      ],
+      "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"
+        },
+        "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"
+        },
+        "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"
+        },
+        "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 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*`.",
+          "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.",
+          "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.",
+          "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",
+          "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",
+          "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- 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.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "NoTestRun",
+            "RunSpecifiedTests",
+            "RunLocalTests",
+            "RunAllTestsInOrg"
+          ],
+          "type": "option"
+        },
+        "verbose": {
+          "exclusive": [
+            "concise"
+          ],
+          "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 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 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",
+          "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.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "project:deploy:start",
       "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": "Deploy metadata to an org from your local project.",
       "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."
@@ -1484,47 +1539,34 @@
         "commands",
         "project",
         "deploy",
-        "resume.js"
+        "start.js"
       ],
       "aliasPermutations": [
-        "deploy:metadata:resume",
-        "metadata:deploy:resume",
-        "metadata:resume:deploy",
-        "deploy:resume:metadata",
-        "resume:deploy:metadata",
-        "resume:metadata:deploy"
+        "deploy:metadata",
+        "metadata:deploy"
       ],
       "permutations": [
-        "project:deploy:resume",
-        "deploy:project:resume",
-        "deploy:resume:project",
-        "project:resume:deploy",
-        "resume:project:deploy",
-        "resume:deploy:project"
+        "project:deploy:start",
+        "deploy:project:start",
+        "deploy:start:project",
+        "project:start:deploy",
+        "start:project:deploy",
+        "start:deploy:project"
       ]
     },
-    "project:deploy:start": {
+    "project:deploy:validate": {
       "aliases": [
-        "deploy:metadata"
+        "deploy:metadata:validate"
       ],
       "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": "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": [
-        "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"
+        "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": {
@@ -1546,16 +1588,13 @@
           "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.",
+          "summary": "Target API version for the validation.",
           "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 the deployment, run \"<%= config.bin %> project deploy resume\". To check the status of the deployment, run \"<%= config.bin %> project deploy report\".",
-          "exclusive": [
-            "wait"
-          ],
+          "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,
@@ -1566,75 +1605,40 @@
             "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"
-        },
-        "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.",
+          "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.",
-          "exclusive": [
-            "source-dir",
-            "metadata",
-            "metadata-dir"
-          ],
           "helpGroup": "Source Format",
           "name": "manifest",
-          "summary": "Full file path for manifest (package.xml) of components to deploy.",
+          "summary": "Full file path for manifest (package.xml) of components to validate for deployment.",
           "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*`.",
+          "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.",
           "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.",
@@ -1652,21 +1656,6 @@
           "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",
@@ -1689,17 +1678,17 @@
         },
         "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\".",
+          "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": [
-            "NoTestRun",
-            "RunSpecifiedTests",
+            "RunAllTestsInOrg",
             "RunLocalTests",
-            "RunAllTestsInOrg"
+            "RunSpecifiedTests"
           ],
           "type": "option"
         },
@@ -1708,63 +1697,28 @@
             "concise"
           ],
           "name": "verbose",
-          "summary": "Show verbose output of the deploy result.",
+          "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 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 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 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.",
+        "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"
         },
-        "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",
@@ -1806,7 +1760,48 @@
               ]
             }
           ],
-          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
+          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
+          "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"
@@ -1814,12 +1809,12 @@
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:start",
+      "id": "project:deploy:validate",
       "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": "Validate a metadata deployment without actually executing it.",
       "enableJsonFlag": true,
       "configurationVariablesSection": {
         "header": "CONFIGURATION VARIABLES",
@@ -1886,34 +1881,37 @@
         "commands",
         "project",
         "deploy",
-        "start.js"
+        "validate.js"
       ],
       "aliasPermutations": [
-        "deploy:metadata",
-        "metadata:deploy"
+        "deploy:metadata:validate",
+        "metadata:deploy:validate",
+        "metadata:validate:deploy",
+        "deploy:validate:metadata",
+        "validate:deploy:metadata",
+        "validate:metadata:deploy"
       ],
       "permutations": [
-        "project:deploy:start",
-        "deploy:project:start",
-        "deploy:start:project",
-        "project:start:deploy",
-        "start:project:deploy",
-        "start:deploy:project"
+        "project:deploy:validate",
+        "deploy:project:validate",
+        "deploy:validate:project",
+        "project:validate:deploy",
+        "validate:project:deploy",
+        "validate:deploy:project"
       ]
     },
-    "project:deploy:validate": {
+    "project:delete:source": {
       "aliases": [
-        "deploy:metadata:validate"
+        "force:source:delete"
       ],
       "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": "Use this command to delete components from orgs that don’t have source tracking. To remove deleted items from orgs that have source tracking enabled, \"<%= config.bin %> project deploy start\".\n\nWhen you run this command, both the local source file and the metadata component in the org are deleted.\n\nTo delete 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"
+        "Delete all local Apex source files and all Apex classes from the org with alias \"my-scratch\":\n<%= config.bin %> <%= command.id %> --metadata ApexClass --target-org my-scratch",
+        "Delete a specific Apex class and a Profile that has a space in it from your default org; don't prompt for confirmation:\n<%= config.bin %> <%= command.id %> --metadata ApexClass:MyFabulousApexClass --metadata \"Profile: My Profile\" --no-prompt",
+        "Run the tests that aren’t in any managed packages as part of the deletion; if the delete succeeds, and the org has source-tracking enabled, update the source tracking information:\n<%= config.bin %> <%= command.id %> --metadata ApexClass --test-level RunLocalTests --track-source",
+        "Delete the Apex source files in a directory and the corresponding components from your default org:\n<%= config.bin %> <%= command.id %> --source-dir force-app/main/default/classes"
       ],
       "flags": {
         "json": {
@@ -1932,89 +1930,63 @@
           "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.",
+          "aliases": [
+            "apiversion"
+          ],
+          "deprecateAliases": true,
+          "description": "Override the api version used for api requests made by this command",
           "name": "api-version",
-          "summary": "Target API version for the validation.",
           "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\".",
-          "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.",
+        "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",
-          "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.",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
-        },
-        "metadata-dir": {
-          "helpGroup": "Metadata API Format",
-          "name": "metadata-dir",
-          "summary": "Root of directory or zip file of metadata formatted files to deploy.",
-          "hasDynamicHelp": false,
+        "target-org": {
+          "aliases": [
+            "targetusername",
+            "u"
+          ],
+          "char": "o",
+          "deprecateAliases": true,
+          "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"
         },
-        "single-package": {
-          "dependsOn": [
-            "metadata-dir"
+        "check-only": {
+          "aliases": [
+            "checkonly"
           ],
-          "helpGroup": "Metadata API Format",
-          "name": "single-package",
-          "summary": "Indicates that the metadata zip file points to a directory structure for a single package.",
+          "char": "c",
+          "deprecateAliases": true,
+          "description": "IMPORTANT: Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.\n\nValidates the deleted metadata and runs all Apex tests, but prevents the deletion from being saved to the org.\n\nIf you change a field type from Master-Detail to Lookup or vice versa, that change isn’t supported when using the --check-only flag to test a deletion (validation). This kind of change isn’t supported for test deletions to avoid the risk of data loss or corruption. If a change that isn’t supported for test deletions is included in a deletion package, the test deletion fails and issues an error.\n\nIf your deletion package changes a field type from Master-Detail to Lookup or vice versa, you can still validate the changes prior to deploying to Production by performing a full deletion to another test Sandbox. A full deletion includes a validation of the changes as part of the deletion process.\n\nNote: A Metadata API deletion that includes Master-Detail relationships deletes all detail records in the Recycle Bin in the following cases.\n\n    1. For a deletion with a new Master-Detail field, soft delete (send to the Recycle Bin) all detail records before proceeding to delete the Master-Detail field, or the deletion fails. During the deletion, detail records are permanently deleted from the Recycle Bin and cannot be recovered.\n\n    2. For a deletion that converts a Lookup field relationship to a Master-Detail relationship, detail records must reference a master record or be soft-deleted (sent to the Recycle Bin) for the deletion to succeed. However, a successful deletion permanently deletes any detail records in the Recycle Bin.",
+          "name": "check-only",
+          "summary": "Validate delete command but don't delete anything from the org or the local project.",
           "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.",
+        "wait": {
+          "char": "w",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you.",
+          "name": "wait",
+          "summary": "Number of minutes to wait for the command to finish.",
           "hasDynamicHelp": true,
           "multiple": false,
           "type": "option"
         },
         "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",
@@ -2024,227 +1996,255 @@
           "type": "option"
         },
         "test-level": {
+          "aliases": [
+            "testlevel"
+          ],
           "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.",
+          "deprecateAliases": true,
+          "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\nIf 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” 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"
         },
-        "verbose": {
-          "exclusive": [
-            "concise"
+        "no-prompt": {
+          "aliases": [
+            "noprompt"
           ],
-          "name": "verbose",
-          "summary": "Show verbose output of the validation result.",
+          "char": "r",
+          "deprecateAliases": true,
+          "name": "no-prompt",
+          "summary": "Don't prompt for delete confirmation.",
           "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,
+        "metadata": {
+          "char": "m",
+          "description": "If you specify this flag, don’t specify --source-dir.",
+          "name": "metadata",
+          "summary": "Metadata components to delete.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
           "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.",
+        "source-dir": {
+          "aliases": [
+            "sourcepath"
+          ],
+          "char": "p",
+          "deprecateAliases": true,
+          "description": "The supplied paths can be a single file (in which case the operation is applied to only one file) or a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories).\n\nIf you specify this flag, don’t specify --metadata.",
+          "name": "source-dir",
+          "summary": "Source file paths to delete.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "track-source": {
+          "aliases": [
+            "tracksource"
+          ],
+          "char": "t",
+          "deprecateAliases": true,
+          "exclusive": [
+            "check-only"
+          ],
+          "name": "track-source",
+          "summary": "If the delete succeeds, update the source tracking information.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "force-overwrite": {
+          "aliases": [
+            "forceoverwrite"
+          ],
+          "char": "f",
+          "dependsOn": [
+            "track-source"
+          ],
+          "deprecateAliases": true,
+          "name": "force-overwrite",
+          "summary": "Ignore conflict warnings and overwrite changes to the org.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "verbose": {
+          "name": "verbose",
+          "summary": "Verbose output of the delete result.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "project:delete:source",
+      "pluginAlias": "@salesforce/plugin-deploy-retrieve",
+      "pluginName": "@salesforce/plugin-deploy-retrieve",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Delete source from your project and from a non-source-tracked org.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "project",
+        "delete",
+        "source.js"
+      ],
+      "aliasPermutations": [
+        "force:source:delete",
+        "source:force:delete",
+        "source:delete:force",
+        "force:delete:source",
+        "delete:force:source",
+        "delete:source:force"
+      ],
+      "permutations": [
+        "project:delete:source",
+        "delete:project:source",
+        "delete:source:project",
+        "project:source:delete",
+        "source:project:delete",
+        "source:delete:project"
+      ]
+    },
+    "project:delete:tracking": {
+      "aliases": [
+        "force:source:tracking:clear"
+      ],
+      "args": {},
+      "deprecateAliases": true,
+      "description": "WARNING: This command deletes or overwrites all existing source tracking files. Use with extreme caution.\n\nDeletes all local source tracking information. When you next run 'project deploy preview', Salesforce CLI displays all local and remote files as changed, and any files with the same name are listed as conflicts.",
+      "examples": [
+        "Delete local source tracking for the org with alias \"my-scratch\":\n$ <%= config.bin %> <%= command.id %> --target-org my-scratch"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
           "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.",
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
           "hasDynamicHelp": false,
-          "multiple": true,
-          "options": [
-            "clover",
-            "cobertura",
-            "html-spa",
-            "html",
-            "json",
-            "json-summary",
-            "lcovonly",
-            "none",
-            "teamcity",
-            "text",
-            "text-summary"
-          ],
+          "multiple": false,
           "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"
-              ]
-            }
+        "api-version": {
+          "aliases": [
+            "apiversion"
           ],
-          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
+          "deprecateAliases": true,
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "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",
+        "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"
         },
-        "post-destructive-changes": {
-          "dependsOn": [
-            "manifest"
+        "target-org": {
+          "aliases": [
+            "targetusername",
+            "u"
           ],
-          "helpGroup": "Delete",
-          "name": "post-destructive-changes",
-          "summary": "File path for a manifest (destructiveChangesPost.xml) of components to delete after the deploy.",
-          "hasDynamicHelp": false,
+          "char": "o",
+          "deprecateAliases": true,
+          "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"
+        },
+        "no-prompt": {
+          "aliases": [
+            "noprompt"
+          ],
+          "char": "p",
+          "deprecateAliases": true,
+          "name": "no-prompt",
+          "summary": "Don't prompt for source tracking override confirmation.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:validate",
+      "id": "project:delete:tracking",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Validate a metadata deployment without actually executing it.",
+      "summary": "Delete all local source tracking information.",
       "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."
-          }
-        ]
-      },
-      "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",
-        "validate.js"
+        "delete",
+        "tracking.js"
       ],
       "aliasPermutations": [
-        "deploy:metadata:validate",
-        "metadata:deploy:validate",
-        "metadata:validate:deploy",
-        "deploy:validate:metadata",
-        "validate:deploy:metadata",
-        "validate:metadata:deploy"
+        "force:source:tracking:clear",
+        "source:force:tracking:clear",
+        "source:tracking:force:clear",
+        "source:tracking:clear:force",
+        "force:tracking:source:clear",
+        "tracking:force:source:clear",
+        "tracking:source:force:clear",
+        "tracking:source:clear:force",
+        "force:tracking:clear:source",
+        "tracking:force:clear:source",
+        "tracking:clear:force:source",
+        "tracking:clear:source:force",
+        "force:source:clear:tracking",
+        "source:force:clear:tracking",
+        "source:clear:force:tracking",
+        "source:clear:tracking:force",
+        "force:clear:source:tracking",
+        "clear:force:source:tracking",
+        "clear:source:force:tracking",
+        "clear:source:tracking:force",
+        "force:clear:tracking:source",
+        "clear:force:tracking:source",
+        "clear:tracking:force:source",
+        "clear:tracking:source:force"
       ],
       "permutations": [
-        "project:deploy:validate",
-        "deploy:project:validate",
-        "deploy:validate:project",
-        "project:validate:deploy",
-        "validate:project:deploy",
-        "validate:deploy:project"
+        "project:delete:tracking",
+        "delete:project:tracking",
+        "delete:tracking:project",
+        "project:tracking:delete",
+        "tracking:project:delete",
+        "tracking:delete:project"
       ]
     },
     "project:generate:manifest": {
@@ -2992,6 +2992,15 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "poll-interval": {
+          "name": "poll-interval",
+          "required": false,
+          "summary": "Number of seconds to wait between status checks.",
+          "hasDynamicHelp": true,
+          "helpValue": "<seconds>",
+          "multiple": false,
+          "type": "option"
         }
       },
       "hasDynamicHelp": true,
@@ -3051,5 +3060,5 @@
       ]
     }
   },
-  "version": "3.22.36"
+  "version": "3.22.38-dev.0"
 }