@salesforce/plugin-deploy-retrieve 3.24.26 → 3.24.28

package/README.md

@@ -141,7 +141,7 @@ FLAG DESCRIPTIONS
     If you specify this flag, don’t specify --metadata or --source-dir.
 ```
 
-_See code: [src/commands/project/convert/mdapi.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/convert/mdapi.ts)_
+_See code: [src/commands/project/convert/mdapi.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/convert/mdapi.ts)_
 
 ## `sf project convert source`
 
@@ -214,7 +214,7 @@ FLAG DESCRIPTIONS
     Override the api version used for api requests made by this command
 ```
 
-_See code: [src/commands/project/convert/source.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/convert/source.ts)_
+_See code: [src/commands/project/convert/source.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/convert/source.ts)_
 
 ## `sf project convert source-behavior`
 
@@ -273,7 +273,7 @@ EXAMPLES
     $ sf project convert source-behavior --behavior decomposePermissionSetBeta --dry-run --preserve-temp-dir
 ```
 
-_See code: [src/commands/project/convert/source-behavior.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/convert/source-behavior.ts)_
+_See code: [src/commands/project/convert/source-behavior.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/convert/source-behavior.ts)_
 
 ## `sf project delete source`
 
@@ -426,7 +426,7 @@ FLAG DESCRIPTIONS
     - Separate the test names with spaces: --tests Test1 Test2 "Test With Space"
 ```
 
-_See code: [src/commands/project/delete/source.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/delete/source.ts)_
+_See code: [src/commands/project/delete/source.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/delete/source.ts)_
 
 ## `sf project delete tracking`
 
@@ -463,7 +463,7 @@ EXAMPLES
     $ sf project delete tracking --target-org my-scratch
 ```
 
-_See code: [src/commands/project/delete/tracking.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/delete/tracking.ts)_
+_See code: [src/commands/project/delete/tracking.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/delete/tracking.ts)_
 
 ## `sf project deploy cancel`
 
@@ -535,7 +535,7 @@ FLAG DESCRIPTIONS
     project deploy report".
 ```
 
-_See code: [src/commands/project/deploy/cancel.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/deploy/cancel.ts)_
+_See code: [src/commands/project/deploy/cancel.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/deploy/cancel.ts)_
 
 ## `sf project deploy preview`
 
@@ -618,7 +618,7 @@ FLAG DESCRIPTIONS
     All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.
 ```
 
-_See code: [src/commands/project/deploy/preview.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/deploy/preview.ts)_
+_See code: [src/commands/project/deploy/preview.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/deploy/preview.ts)_
 
 ## `sf project deploy quick`
 
@@ -702,7 +702,7 @@ FLAG DESCRIPTIONS
     deploy report".
 ```
 
-_See code: [src/commands/project/deploy/quick.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/deploy/quick.ts)_
+_See code: [src/commands/project/deploy/quick.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/deploy/quick.ts)_
 
 ## `sf project deploy report`
 
@@ -794,7 +794,7 @@ FLAG DESCRIPTIONS
     --coverage-formatters lcov --coverage-formatters clover
 ```
 
-_See code: [src/commands/project/deploy/report.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/deploy/report.ts)_
+_See code: [src/commands/project/deploy/report.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/deploy/report.ts)_
 
 ## `sf project deploy resume`
 
@@ -879,7 +879,7 @@ FLAG DESCRIPTIONS
     --coverage-formatters lcov --coverage-formatters clover
 ```
 
-_See code: [src/commands/project/deploy/resume.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/deploy/resume.ts)_
+_See code: [src/commands/project/deploy/resume.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/deploy/resume.ts)_
 
 ## `sf project deploy start`
 
@@ -1128,7 +1128,7 @@ FLAG DESCRIPTIONS
     --coverage-formatters lcov --coverage-formatters clover
 ```
 
-_See code: [src/commands/project/deploy/start.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/deploy/start.ts)_
+_See code: [src/commands/project/deploy/start.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/deploy/start.ts)_
 
 ## `sf project deploy validate`
 
@@ -1315,7 +1315,7 @@ FLAG DESCRIPTIONS
     --coverage-formatters lcov --coverage-formatters clover
 ```
 
-_See code: [src/commands/project/deploy/validate.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/deploy/validate.ts)_
+_See code: [src/commands/project/deploy/validate.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/deploy/validate.ts)_
 
 ## `sf project generate manifest`
 
@@ -1411,7 +1411,7 @@ EXAMPLES
     $ sf project generate manifest --from-org test@myorg.com --excluded-metadata StandardValueSet
 ```
 
-_See code: [src/commands/project/generate/manifest.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/generate/manifest.ts)_
+_See code: [src/commands/project/generate/manifest.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/generate/manifest.ts)_
 
 ## `sf project list ignored`
 
@@ -1453,7 +1453,7 @@ EXAMPLES
     $ sf project list ignored --source-dir package.xml
 ```
 
-_See code: [src/commands/project/list/ignored.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/list/ignored.ts)_
+_See code: [src/commands/project/list/ignored.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/list/ignored.ts)_
 
 ## `sf project reset tracking`
 
@@ -1502,7 +1502,7 @@ EXAMPLES
     $ sf project reset tracking --revision 30
 ```
 
-_See code: [src/commands/project/reset/tracking.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/reset/tracking.ts)_
+_See code: [src/commands/project/reset/tracking.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/reset/tracking.ts)_
 
 ## `sf project retrieve preview`
 
@@ -1556,7 +1556,7 @@ FLAG DESCRIPTIONS
     production orgs.
 ```
 
-_See code: [src/commands/project/retrieve/preview.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/retrieve/preview.ts)_
+_See code: [src/commands/project/retrieve/preview.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/retrieve/preview.ts)_
 
 ## `sf project retrieve start`
 
@@ -1729,6 +1729,6 @@ FLAG DESCRIPTIONS
     If you specify this flag, don’t specify --metadata or --source-dir.
 ```
 
-_See code: [src/commands/project/retrieve/start.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.26/src/commands/project/retrieve/start.ts)_
+_See code: [src/commands/project/retrieve/start.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.28/src/commands/project/retrieve/start.ts)_
 
 <!-- commandsstop -->

package/oclif.manifest.json

@@ -1902,18 +1902,20 @@
         "validate:deploy:project"
       ]
     },
-    "project:delete:source": {
+    "project:generate:manifest": {
       "aliases": [
-        "force:source:delete"
+        "force:source:manifest:create"
       ],
       "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": "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": [
-        "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"
+        "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": {
@@ -1952,150 +1954,137 @@
           "multiple": false,
           "type": "option"
         },
-        "target-org": {
+        "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": [
-            "targetusername",
-            "u"
+            "sourcepath"
           ],
-          "char": "o",
+          "char": "p",
           "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,
+          "name": "source-dir",
+          "summary": "Paths to the local source files to include in the manifest.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
           "type": "option"
         },
-        "check-only": {
+        "name": {
           "aliases": [
-            "checkonly"
+            "manifestname"
           ],
-          "char": "c",
+          "char": "n",
           "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.",
+          "exclusive": [
+            "type"
+          ],
+          "name": "name",
+          "summary": "Name of a custom manifest file to create.",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
           "type": "option"
         },
-        "test-level": {
+        "type": {
           "aliases": [
-            "testlevel"
+            "manifesttype"
           ],
-          "char": "l",
+          "char": "t",
           "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.",
+          "exclusive": [
+            "name"
+          ],
+          "name": "type",
+          "summary": "Type of manifest to create; the type determines the name of the created file.",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
-            "NoTestRun",
-            "RunSpecifiedTests",
-            "RunLocalTests",
-            "RunAllTestsInOrg",
-            "RunRelevantTests"
+            "pre",
+            "post",
+            "destroy",
+            "package"
           ],
           "type": "option"
         },
-        "no-prompt": {
+        "include-packages": {
           "aliases": [
-            "noprompt"
+            "includepackages"
+          ],
+          "char": "c",
+          "dependsOn": [
+            "from-org"
           ],
-          "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": "Metadata components to delete.",
+          "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"
         },
-        "source-dir": {
-          "aliases": [
-            "sourcepath"
+        "excluded-metadata": {
+          "name": "excluded-metadata",
+          "relationships": [
+            {
+              "type": "some",
+              "flags": [
+                "from-org",
+                "source-dir"
+              ]
+            }
           ],
-          "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.",
+          "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"
         },
-        "track-source": {
+        "from-org": {
           "aliases": [
-            "tracksource"
+            "fromorg"
           ],
-          "char": "t",
           "deprecateAliases": true,
           "exclusive": [
-            "check-only"
+            "source-dir"
           ],
-          "name": "track-source",
-          "summary": "If the delete succeeds, update the source tracking information.",
-          "allowNo": false,
-          "type": "boolean"
+          "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"
         },
-        "force-overwrite": {
+        "output-dir": {
           "aliases": [
-            "forceoverwrite"
-          ],
-          "char": "f",
-          "dependsOn": [
-            "track-source"
+            "outputdir",
+            "o"
           ],
+          "char": "d",
           "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": "output-dir",
+          "summary": "Directory to save the created manifest.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         }
       },
-      "hasDynamicHelp": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "project:delete:source",
+      "id": "project:generate:manifest",
       "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": "Create a project manifest that lists the metadata components you want to deploy or retrieve.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "isESM": true,
@@ -2103,35 +2092,55 @@
         "lib",
         "commands",
         "project",
-        "delete",
-        "source.js"
+        "generate",
+        "manifest.js"
       ],
       "aliasPermutations": [
-        "force:source:delete",
-        "source:force:delete",
-        "source:delete:force",
-        "force:delete:source",
-        "delete:force:source",
-        "delete:source:force"
+        "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:delete:source",
-        "delete:project:source",
-        "delete:source:project",
-        "project:source:delete",
-        "source:project:delete",
-        "source:delete:project"
+        "project:generate:manifest",
+        "generate:project:manifest",
+        "generate:manifest:project",
+        "project:manifest:generate",
+        "manifest:project:generate",
+        "manifest:generate:project"
       ]
     },
-    "project:delete:tracking": {
+    "project:list:ignored": {
       "aliases": [
-        "force:source:tracking:clear"
+        "force:source:ignored:list"
       ],
       "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": "When deploying or retrieving metadata between your local project and an org, you can specify the source files you want to exclude with a .forceignore file. The .forceignore file structure mimics the .gitignore structure. Each line in .forceignore specifies a pattern that corresponds to one or more files. The files typically represent metadata components, but can be any files you want to exclude, such as LWC configuration JSON files or tests.",
       "examples": [
-        "Delete local source tracking for the org with alias \"my-scratch\":\n$ <%= config.bin %> <%= command.id %> --target-org my-scratch"
+        "List all the files in all package directories that are ignored:\n<%= config.bin %> <%= command.id %>",
+        "List all the files in a specific directory that are ignored:\n<%= config.bin %> <%= command.id %> --source-dir force-app",
+        "Check if a particular file is ignored:\n<%= config.bin %> <%= command.id %> --source-dir package.xml"
       ],
       "flags": {
         "json": {
@@ -2149,62 +2158,27 @@
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
+        "source-dir": {
           "aliases": [
-            "apiversion"
+            "sourcepath"
           ],
+          "char": "p",
           "deprecateAliases": true,
-          "description": "Override the api version used for api requests made by this command",
-          "name": "api-version",
+          "name": "source-dir",
+          "summary": "File or directory of files that the command checks for foreceignored files.",
           "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.",
-          "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,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "project:delete:tracking",
+      "id": "project:list:ignored",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Delete all local source tracking information.",
+      "summary": "Check your local project package directories for forceignored files.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "isESM": true,
@@ -2212,58 +2186,56 @@
         "lib",
         "commands",
         "project",
-        "delete",
-        "tracking.js"
+        "list",
+        "ignored.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"
+        "force:source:ignored:list",
+        "source:force:ignored:list",
+        "source:ignored:force:list",
+        "source:ignored:list:force",
+        "force:ignored:source:list",
+        "ignored:force:source:list",
+        "ignored:source:force:list",
+        "ignored:source:list:force",
+        "force:ignored:list:source",
+        "ignored:force:list:source",
+        "ignored:list:force:source",
+        "ignored:list:source:force",
+        "force:source:list:ignored",
+        "source:force:list:ignored",
+        "source:list:force:ignored",
+        "source:list:ignored:force",
+        "force:list:source:ignored",
+        "list:force:source:ignored",
+        "list:source:force:ignored",
+        "list:source:ignored:force",
+        "force:list:ignored:source",
+        "list:force:ignored:source",
+        "list:ignored:force:source",
+        "list:ignored:source:force"
       ],
       "permutations": [
-        "project:delete:tracking",
-        "delete:project:tracking",
-        "delete:tracking:project",
-        "project:tracking:delete",
-        "tracking:project:delete",
-        "tracking:delete:project"
+        "project:list:ignored",
+        "list:project:ignored",
+        "list:ignored:project",
+        "project:ignored:list",
+        "ignored:project:list",
+        "ignored:list: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,137 +2274,150 @@
           "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": {
+        "target-org": {
           "aliases": [
-            "sourcepath"
+            "targetusername",
+            "u"
           ],
-          "char": "p",
+          "char": "o",
           "deprecateAliases": true,
-          "name": "source-dir",
-          "summary": "Paths to the local source files to include in the manifest.",
-          "delimiter": ",",
-          "hasDynamicHelp": false,
-          "multiple": 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"
         },
-        "name": {
+        "check-only": {
           "aliases": [
-            "manifestname"
+            "checkonly"
           ],
-          "char": "n",
+          "char": "c",
           "deprecateAliases": true,
-          "exclusive": [
-            "type"
-          ],
-          "name": "name",
-          "summary": "Name of a custom manifest file to create.",
-          "hasDynamicHelp": false,
+          "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"
         },
-        "type": {
+        "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": [
-            "manifesttype"
+            "testlevel"
           ],
-          "char": "t",
+          "char": "l",
           "deprecateAliases": true,
-          "exclusive": [
-            "name"
-          ],
-          "name": "type",
-          "summary": "Type of manifest to create; the type determines the name of the created file.",
+          "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": [
-            "pre",
-            "post",
-            "destroy",
-            "package"
+            "NoTestRun",
+            "RunSpecifiedTests",
+            "RunLocalTests",
+            "RunAllTestsInOrg",
+            "RunRelevantTests"
           ],
           "type": "option"
         },
-        "include-packages": {
+        "no-prompt": {
           "aliases": [
-            "includepackages"
-          ],
-          "char": "c",
-          "dependsOn": [
-            "from-org"
+            "noprompt"
           ],
+          "char": "r",
           "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.",
+          "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": "Metadata components to delete.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
-          "options": [
-            "managed",
-            "unlocked"
-          ],
           "type": "option"
         },
-        "excluded-metadata": {
-          "name": "excluded-metadata",
-          "relationships": [
-            {
-              "type": "some",
-              "flags": [
-                "from-org",
-                "source-dir"
-              ]
-            }
+        "source-dir": {
+          "aliases": [
+            "sourcepath"
           ],
-          "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.",
+          "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"
         },
-        "from-org": {
+        "track-source": {
           "aliases": [
-            "fromorg"
+            "tracksource"
           ],
+          "char": "t",
           "deprecateAliases": true,
           "exclusive": [
-            "source-dir"
+            "check-only"
           ],
-          "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"
+          "name": "track-source",
+          "summary": "If the delete succeeds, update the source tracking information.",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "output-dir": {
+        "force-overwrite": {
           "aliases": [
-            "outputdir",
-            "o"
+            "forceoverwrite"
+          ],
+          "char": "f",
+          "dependsOn": [
+            "track-source"
           ],
-          "char": "d",
           "deprecateAliases": true,
-          "name": "output-dir",
-          "summary": "Directory to save the created manifest.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+          "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": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:generate:manifest",
+      "id": "project:delete:source",
       "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 source from your project and from a non-source-tracked org.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "isESM": true,
@@ -2440,55 +2425,35 @@
         "lib",
         "commands",
         "project",
-        "generate",
-        "manifest.js"
+        "delete",
+        "source.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:delete",
+        "source:force:delete",
+        "source:delete:force",
+        "force:delete:source",
+        "delete:force:source",
+        "delete:source:force"
       ],
       "permutations": [
-        "project:generate:manifest",
-        "generate:project:manifest",
-        "generate:manifest:project",
-        "project:manifest:generate",
-        "manifest:project:generate",
-        "manifest:generate:project"
+        "project:delete:source",
+        "delete:project:source",
+        "delete:source:project",
+        "project:source:delete",
+        "source:project:delete",
+        "source:delete:project"
       ]
     },
-    "project:list:ignored": {
+    "project:delete:tracking": {
       "aliases": [
-        "force:source:ignored:list"
+        "force:source:tracking:clear"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "When deploying or retrieving metadata between your local project and an org, you can specify the source files you want to exclude with a .forceignore file. The .forceignore file structure mimics the .gitignore structure. Each line in .forceignore specifies a pattern that corresponds to one or more files. The files typically represent metadata components, but can be any files you want to exclude, such as LWC configuration JSON files or tests.",
+      "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": [
-        "List all the files in all package directories that are ignored:\n<%= config.bin %> <%= command.id %>",
-        "List all the files in a specific directory that are ignored:\n<%= config.bin %> <%= command.id %> --source-dir force-app",
-        "Check if a particular file is ignored:\n<%= config.bin %> <%= command.id %> --source-dir package.xml"
+        "Delete local source tracking for the org with alias \"my-scratch\":\n$ <%= config.bin %> <%= command.id %> --target-org my-scratch"
       ],
       "flags": {
         "json": {
@@ -2506,27 +2471,62 @@
           "multiple": false,
           "type": "option"
         },
-        "source-dir": {
+        "api-version": {
           "aliases": [
-            "sourcepath"
+            "apiversion"
           ],
-          "char": "p",
           "deprecateAliases": true,
-          "name": "source-dir",
-          "summary": "File or directory of files that the command checks for foreceignored files.",
+          "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.",
+          "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": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:list:ignored",
+      "id": "project:delete:tracking",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginType": "core",
       "strict": true,
-      "summary": "Check your local project package directories for forceignored files.",
+      "summary": "Delete all local source tracking information.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "isESM": true,
@@ -2534,42 +2534,42 @@
         "lib",
         "commands",
         "project",
-        "list",
-        "ignored.js"
+        "delete",
+        "tracking.js"
       ],
       "aliasPermutations": [
-        "force:source:ignored:list",
-        "source:force:ignored:list",
-        "source:ignored:force:list",
-        "source:ignored:list:force",
-        "force:ignored:source:list",
-        "ignored:force:source:list",
-        "ignored:source:force:list",
-        "ignored:source:list:force",
-        "force:ignored:list:source",
-        "ignored:force:list:source",
-        "ignored:list:force:source",
-        "ignored:list:source:force",
-        "force:source:list:ignored",
-        "source:force:list:ignored",
-        "source:list:force:ignored",
-        "source:list:ignored:force",
-        "force:list:source:ignored",
-        "list:force:source:ignored",
-        "list:source:force:ignored",
-        "list:source:ignored:force",
-        "force:list:ignored:source",
-        "list:force:ignored:source",
-        "list:ignored:force:source",
-        "list:ignored:source:force"
+        "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:list:ignored",
-        "list:project:ignored",
-        "list:ignored:project",
-        "project:ignored:list",
-        "ignored:project:list",
-        "ignored:list:project"
+        "project:delete:tracking",
+        "delete:project:tracking",
+        "delete:tracking:project",
+        "project:tracking:delete",
+        "tracking:project:delete",
+        "tracking:delete:project"
       ]
     },
     "project:reset:tracking": {
@@ -3054,5 +3054,5 @@
       ]
     }
   },
-  "version": "3.24.26"
+  "version": "3.24.28"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@salesforce/plugin-deploy-retrieve",
     "description": "deploy and retrieve commands for sf",
-    "version": "3.24.26",
+    "version": "3.24.28",
     "author": "Salesforce",
     "bugs": "https://github.com/forcedotcom/cli/issues",
     "enableO11y": true,
@@ -16,7 +16,7 @@
         "@salesforce/plugin-info": "^3.4.93",
         "@salesforce/sf-plugins-core": "^12.2.6",
         "@salesforce/source-deploy-retrieve": "^12.32.1",
-        "@salesforce/source-tracking": "^7.8.8",
+        "@salesforce/source-tracking": "^7.8.9",
         "@salesforce/ts-types": "^2.0.12",
         "ansis": "^3.17.0",
         "terminal-link": "^3.0.0"
@@ -27,7 +27,7 @@
         "@salesforce/dev-scripts": "^11.0.4",
         "@salesforce/plugin-command-reference": "^3.1.78",
         "@salesforce/schemas": "^1.9.0",
-        "@salesforce/source-testkit": "^2.2.179",
+        "@salesforce/source-testkit": "^2.2.182",
         "@salesforce/ts-sinon": "^1.4.33",
         "cross-env": "^7.0.3",
         "eslint-plugin-sf-plugin": "^1.20.32",
@@ -258,7 +258,7 @@
     "exports": "./lib/index.js",
     "type": "module",
     "sfdx": {
-        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/3.24.26.crt",
-        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/3.24.26.sig"
+        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/3.24.28.crt",
+        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/3.24.28.sig"
     }
 }