@salesforce/plugin-deploy-retrieve 3.24.32 → 3.24.34

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,207 +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\n- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See \"@IsTest Annotation\" in the \"Apex Developer Guide\" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.\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\" (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.",
+        "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",
-            "RunRelevantTests"
-          ],
           "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": {
@@ -652,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": {
@@ -2250,20 +1902,18 @@
         "validate:deploy:project"
       ]
     },
-    "project:generate:manifest": {
+    "project:delete:source": {
       "aliases": [
-        "force:source:manifest:create"
+        "force:source:delete"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-dir). You can specify either of these flags, not both.\n\nUse --type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this flag, and their respective file names, are:\n\n    * package : package.xml (default)\n    * pre : destructiveChangesPre.xml\n    * post : destructiveChangesPost.xml\n    * destroy : destructiveChanges.xml\n\nSee https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files.\n\nUse --name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --type or --name, but not both.\n\nTo include multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --include-packages and --source-dir.\n\nTo build a manifest from the metadata in an org, use the --from-org flag. You can combine --from-org with the --metadata flag to include only certain metadata types, or with the --excluded-metadata flag to exclude certain metadata types. When building a manifest from an org, the command makes many concurrent API calls to discover the metadata that exists in the org. To limit the number of concurrent requests, use the SF_LIST_METADATA_BATCH_SIZE environment variable and set it to a size that works best for your org and environment. If you experience timeouts or inconsistent manifest contents, then setting this environment variable can improve accuracy. However, the command takes longer to run because it sends fewer requests at a time.",
+      "description": "Use this command to 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": [
-        "Create a manifest for deploying or retrieving all Apex classes and custom objects:\n$ <%= config.bin %> <%= command.id %> --metadata ApexClass --metadata CustomObject",
-        "Create a manifest for deleting the specified Apex class:\n$ <%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass --type destroy",
-        "Create a manifest for deploying or retrieving all the metadata components in the specified local directory; name the file myNewManifest.xml:\n$ <%= config.bin %> <%= command.id %> --source-dir force-app --name myNewManifest",
-        "Create a manifest from the metadata components in the specified org and include metadata in any unlocked packages:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --include-packages unlocked",
-        "Create a manifest from specific metadata types in an org:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --metadata ApexClass,CustomObject,CustomLabels",
-        "Create a manifest from all metadata components in an org excluding specific metadata types:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --excluded-metadata StandardValueSet"
+        "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": {
@@ -2302,10 +1952,88 @@
           "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"
+        },
+        "check-only": {
+          "aliases": [
+            "checkonly"
+          ],
+          "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"
+        },
+        "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\n- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See \"@IsTest Annotation\" in the \"Apex Developer Guide\" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.\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\" (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",
+            "RunRelevantTests"
+          ],
+          "type": "option"
+        },
+        "no-prompt": {
+          "aliases": [
+            "noprompt"
+          ],
+          "char": "r",
+          "deprecateAliases": true,
+          "name": "no-prompt",
+          "summary": "Don't prompt for delete confirmation.",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "metadata": {
           "char": "m",
+          "description": "If you specify this flag, don’t specify --source-dir.",
           "name": "metadata",
-          "summary": "Names of metadata components to include in the manifest.",
+          "summary": "Metadata components to delete.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -2317,122 +2045,166 @@
           ],
           "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": "Paths to the local source files to include in the manifest.",
+          "summary": "Source file paths to delete.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
         },
-        "name": {
+        "track-source": {
           "aliases": [
-            "manifestname"
+            "tracksource"
           ],
-          "char": "n",
+          "char": "t",
           "deprecateAliases": true,
           "exclusive": [
-            "type"
+            "check-only"
           ],
-          "name": "name",
-          "summary": "Name of a custom manifest file to create.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+          "name": "track-source",
+          "summary": "If the delete succeeds, update the source tracking information.",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "type": {
+        "force-overwrite": {
           "aliases": [
-            "manifesttype"
+            "forceoverwrite"
           ],
-          "char": "t",
-          "deprecateAliases": true,
-          "exclusive": [
-            "name"
+          "char": "f",
+          "dependsOn": [
+            "track-source"
           ],
-          "name": "type",
-          "summary": "Type of manifest to create; the type determines the name of the created file.",
+          "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"
+        },
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "pre",
-            "post",
-            "destroy",
-            "package"
-          ],
           "type": "option"
         },
-        "include-packages": {
+        "api-version": {
           "aliases": [
-            "includepackages"
-          ],
-          "char": "c",
-          "dependsOn": [
-            "from-org"
+            "apiversion"
           ],
           "deprecateAliases": true,
-          "name": "include-packages",
-          "summary": "Package types (managed, unlocked) whose metadata is included in the manifest; by default, metadata in managed and unlocked packages is excluded. Metadata in unmanaged packages is always included.",
-          "delimiter": ",",
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
-          "multiple": true,
-          "options": [
-            "managed",
-            "unlocked"
-          ],
+          "multiple": false,
           "type": "option"
         },
-        "excluded-metadata": {
-          "name": "excluded-metadata",
-          "relationships": [
-            {
-              "type": "some",
-              "flags": [
-                "from-org",
-                "source-dir"
-              ]
-            }
-          ],
-          "summary": "Metadata types to exclude when building a manifest from an org. Specify the name of the type, not the name of a specific component.",
-          "delimiter": ",",
+        "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": true,
+          "multiple": false,
           "type": "option"
         },
-        "from-org": {
+        "target-org": {
           "aliases": [
-            "fromorg"
+            "targetusername",
+            "u"
           ],
+          "char": "o",
           "deprecateAliases": true,
-          "exclusive": [
-            "source-dir"
-          ],
-          "name": "from-org",
-          "summary": "Username or alias of the org that contains the metadata components from which to build a manifest.",
-          "hasDynamicHelp": false,
+          "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"
         },
-        "output-dir": {
+        "no-prompt": {
           "aliases": [
-            "outputdir",
-            "o"
+            "noprompt"
           ],
-          "char": "d",
+          "char": "p",
           "deprecateAliases": true,
-          "name": "output-dir",
-          "summary": "Directory to save the created manifest.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+          "name": "no-prompt",
+          "summary": "Don't prompt for source tracking override confirmation.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:generate:manifest",
+      "id": "project:delete:tracking",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Create a project manifest that lists the metadata components you want to deploy or retrieve.",
+      "summary": "Delete all local source tracking information.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "isESM": true,
@@ -2440,42 +2212,42 @@
         "lib",
         "commands",
         "project",
-        "generate",
-        "manifest.js"
+        "delete",
+        "tracking.js"
       ],
       "aliasPermutations": [
-        "force:source:manifest:create",
-        "source:force:manifest:create",
-        "source:manifest:force:create",
-        "source:manifest:create:force",
-        "force:manifest:source:create",
-        "manifest:force:source:create",
-        "manifest:source:force:create",
-        "manifest:source:create:force",
-        "force:manifest:create:source",
-        "manifest:force:create:source",
-        "manifest:create:force:source",
-        "manifest:create:source:force",
-        "force:source:create:manifest",
-        "source:force:create:manifest",
-        "source:create:force:manifest",
-        "source:create:manifest:force",
-        "force:create:source:manifest",
-        "create:force:source:manifest",
-        "create:source:force:manifest",
-        "create:source:manifest:force",
-        "force:create:manifest:source",
-        "create:force:manifest:source",
-        "create:manifest:force:source",
-        "create:manifest:source:force"
+        "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:generate:manifest",
-        "generate:project:manifest",
-        "generate:manifest:project",
-        "project:manifest:generate",
-        "manifest:project:generate",
-        "manifest:generate:project"
+        "project:delete:tracking",
+        "delete:project:tracking",
+        "delete:tracking:project",
+        "project:tracking:delete",
+        "tracking:project:delete",
+        "tracking:delete:project"
       ]
     },
     "project:list:ignored": {
@@ -2708,6 +2480,234 @@
         "tracking:reset:project"
       ]
     },
+    "project:generate:manifest": {
+      "aliases": [
+        "force:source:manifest:create"
+      ],
+      "args": {},
+      "deprecateAliases": true,
+      "description": "Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-dir). You can specify either of these flags, not both.\n\nUse --type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this flag, and their respective file names, are:\n\n    * package : package.xml (default)\n    * pre : destructiveChangesPre.xml\n    * post : destructiveChangesPost.xml\n    * destroy : destructiveChanges.xml\n\nSee https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files.\n\nUse --name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --type or --name, but not both.\n\nTo include multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --include-packages and --source-dir.\n\nTo build a manifest from the metadata in an org, use the --from-org flag. You can combine --from-org with the --metadata flag to include only certain metadata types, or with the --excluded-metadata flag to exclude certain metadata types. When building a manifest from an org, the command makes many concurrent API calls to discover the metadata that exists in the org. To limit the number of concurrent requests, use the SF_LIST_METADATA_BATCH_SIZE environment variable and set it to a size that works best for your org and environment. If you experience timeouts or inconsistent manifest contents, then setting this environment variable can improve accuracy. However, the command takes longer to run because it sends fewer requests at a time.",
+      "examples": [
+        "Create a manifest for deploying or retrieving all Apex classes and custom objects:\n$ <%= config.bin %> <%= command.id %> --metadata ApexClass --metadata CustomObject",
+        "Create a manifest for deleting the specified Apex class:\n$ <%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass --type destroy",
+        "Create a manifest for deploying or retrieving all the metadata components in the specified local directory; name the file myNewManifest.xml:\n$ <%= config.bin %> <%= command.id %> --source-dir force-app --name myNewManifest",
+        "Create a manifest from the metadata components in the specified org and include metadata in any unlocked packages:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --include-packages unlocked",
+        "Create a manifest from specific metadata types in an org:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --metadata ApexClass,CustomObject,CustomLabels",
+        "Create a manifest from all metadata components in an org excluding specific metadata types:\n$ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --excluded-metadata StandardValueSet"
+      ],
+      "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": {
+          "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"
+        },
+        "metadata": {
+          "char": "m",
+          "name": "metadata",
+          "summary": "Names of metadata components to include in the manifest.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "source-dir": {
+          "aliases": [
+            "sourcepath"
+          ],
+          "char": "p",
+          "deprecateAliases": true,
+          "name": "source-dir",
+          "summary": "Paths to the local source files to include in the manifest.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "name": {
+          "aliases": [
+            "manifestname"
+          ],
+          "char": "n",
+          "deprecateAliases": true,
+          "exclusive": [
+            "type"
+          ],
+          "name": "name",
+          "summary": "Name of a custom manifest file to create.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "type": {
+          "aliases": [
+            "manifesttype"
+          ],
+          "char": "t",
+          "deprecateAliases": true,
+          "exclusive": [
+            "name"
+          ],
+          "name": "type",
+          "summary": "Type of manifest to create; the type determines the name of the created file.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "pre",
+            "post",
+            "destroy",
+            "package"
+          ],
+          "type": "option"
+        },
+        "include-packages": {
+          "aliases": [
+            "includepackages"
+          ],
+          "char": "c",
+          "dependsOn": [
+            "from-org"
+          ],
+          "deprecateAliases": true,
+          "name": "include-packages",
+          "summary": "Package types (managed, unlocked) whose metadata is included in the manifest; by default, metadata in managed and unlocked packages is excluded. Metadata in unmanaged packages is always included.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "options": [
+            "managed",
+            "unlocked"
+          ],
+          "type": "option"
+        },
+        "excluded-metadata": {
+          "name": "excluded-metadata",
+          "relationships": [
+            {
+              "type": "some",
+              "flags": [
+                "from-org",
+                "source-dir"
+              ]
+            }
+          ],
+          "summary": "Metadata types to exclude when building a manifest from an org. Specify the name of the type, not the name of a specific component.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "from-org": {
+          "aliases": [
+            "fromorg"
+          ],
+          "deprecateAliases": true,
+          "exclusive": [
+            "source-dir"
+          ],
+          "name": "from-org",
+          "summary": "Username or alias of the org that contains the metadata components from which to build a manifest.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "output-dir": {
+          "aliases": [
+            "outputdir",
+            "o"
+          ],
+          "char": "d",
+          "deprecateAliases": true,
+          "name": "output-dir",
+          "summary": "Directory to save the created manifest.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "project:generate:manifest",
+      "pluginAlias": "@salesforce/plugin-deploy-retrieve",
+      "pluginName": "@salesforce/plugin-deploy-retrieve",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Create a project manifest that lists the metadata components you want to deploy or retrieve.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "project",
+        "generate",
+        "manifest.js"
+      ],
+      "aliasPermutations": [
+        "force:source:manifest:create",
+        "source:force:manifest:create",
+        "source:manifest:force:create",
+        "source:manifest:create:force",
+        "force:manifest:source:create",
+        "manifest:force:source:create",
+        "manifest:source:force:create",
+        "manifest:source:create:force",
+        "force:manifest:create:source",
+        "manifest:force:create:source",
+        "manifest:create:force:source",
+        "manifest:create:source:force",
+        "force:source:create:manifest",
+        "source:force:create:manifest",
+        "source:create:force:manifest",
+        "source:create:manifest:force",
+        "force:create:source:manifest",
+        "create:force:source:manifest",
+        "create:source:force:manifest",
+        "create:source:manifest:force",
+        "force:create:manifest:source",
+        "create:force:manifest:source",
+        "create:manifest:force:source",
+        "create:manifest:source:force"
+      ],
+      "permutations": [
+        "project:generate:manifest",
+        "generate:project:manifest",
+        "generate:manifest:project",
+        "project:manifest:generate",
+        "manifest:project:generate",
+        "manifest:generate:project"
+      ]
+    },
     "project:retrieve:preview": {
       "aliases": [
         "retrieve:metadata:preview"
@@ -3054,5 +3054,5 @@
       ]
     }
   },
-  "version": "3.24.32"
+  "version": "3.24.34"
 }