@salesforce/plugin-deploy-retrieve 1.8.5-beta.7 → 1.8.5-beta.9

package/oclif.manifest.json

@@ -1,10 +1,10 @@
 {
-  "version": "1.8.5-beta.7",
+  "version": "1.8.5-beta.9",
   "commands": {
     "deploy": {
       "id": "deploy",
       "summary": "Deploy a project interactively to any Salesforce environment.",
-      "description": "This command must be run from within a project.\n\nThe command first analyzes your project, your active or logged-into environments, and local defaults to determine what to deploy and where to deploy it. The command then prompts you for information about this particular deployment and provides intelligent choices based on its analysis.\n\nFor example, if your local project contains a source directory with metadata files in source format, the command asks if you want to deploy that Salesforce app to an org. The command lists your connected orgs and asks which one you want to deploy to. The list of orgs starts with scratch orgs, ordered by expiration date with the most recently created one first, and then Dev Hub and production orgs ordered by name. If the command finds Apex tests, it asks if you want to run them and at which level.\n\nThe command stores your responses in the \"deploy-options.json\" file in your local project directory and uses them as defaults when you rerun the command. Specify --interactive to force the command to reprompt.\n\nUse this command for quick and simple deploys. For more complicated deployments, use the environment-specific commands, such as \"sf project deploy start\", that provide additional flags.",
+      "description": "This command must be run from within a project.\n\nThe command first analyzes your project, your active or logged-into environments, and local defaults to determine what to deploy and where to deploy it. The command then prompts you for information about this particular deployment and provides intelligent choices based on its analysis.\n\nFor example, if your local project contains a source directory with metadata files in source format, the command asks if you want to deploy that Salesforce app to an org. The command lists your connected orgs and asks which one you want to deploy to. The list of orgs starts with scratch orgs, ordered by expiration date with the most recently created one first, and then Dev Hub and production orgs ordered by name. If the command finds Apex tests, it asks if you want to run them and at which level.\n\nThe command stores your responses in the \"deploy-options.json\" file in your local project directory and uses them as defaults when you rerun the command. Specify --interactive to force the command to reprompt.\n\nUse this command for quick and simple deploys. For more complicated deployments, use the environment-specific commands, such as \"<%= config.bin %> project deploy start\", that provide additional flags.",
       "strict": true,
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
@@ -32,7 +32,7 @@
     "project:convert:mdapi": {
       "id": "project:convert:mdapi",
       "summary": "Convert metadata retrieved via Metadata API into the source format used in Salesforce DX projects.",
-      "description": "To use Salesforce CLI to work with components that you retrieved via Metadata API, first convert your files from the metadata format to the source format using this command.\n\nTo convert files from the source format back to the metadata format, run \"<%= config.bin %> project convert source\".",
+      "description": "To use Salesforce CLI to work with components that you retrieved via Metadata API, first convert your files from the metadata format to the source format using this command.\n\nTo convert files from the source format back to the metadata format, run \"<%= config.bin %> project convert source\".\n\nTo convert 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 --manifest and --source-dir.",
       "strict": true,
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
@@ -110,7 +110,7 @@
           "name": "metadata-dir",
           "type": "option",
           "char": "p",
-          "summary": "Comma-separated list of paths to the local metadata files to convert.",
+          "summary": "Root of directory or zip file of metadata formatted files to convert.",
           "description": "The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories).\n\nIf you specify this flag, don’t specify --manifest or --metadata. If the comma-separated list you’re supplying contains spaces, enclose the entire comma-separated list in one set of double quotes.",
           "multiple": true,
           "exclusive": [
@@ -127,7 +127,7 @@
           "name": "metadata",
           "type": "option",
           "char": "m",
-          "summary": "Comma-separated list of metadata component names to convert.",
+          "summary": "Metadata component names to convert.",
           "multiple": true,
           "exclusive": [
             "manifest",
@@ -143,7 +143,7 @@
     "project:convert:source": {
       "id": "project:convert:source",
       "summary": "Convert source-formatted files into metadata that you can deploy using Metadata API.",
-      "description": "To convert source-formatted files into the metadata format, so that you can deploy them using Metadata API, run this command. Then deploy the metadata using \"<%= config.bin %> project deploy\".\n\nTo convert Metadata API–formatted files into the source format, run \"<%= config.bin %> project convert mdapi\".\n\nTo specify a package name that includes spaces, enclose the name in single quotes.",
+      "description": "To convert source-formatted files into the metadata format, so that you can deploy them using Metadata API, run this command. Then deploy the metadata using \"<%= config.bin %> project deploy\".\n\nTo convert Metadata API–formatted files into the source format, run \"<%= config.bin %> project convert mdapi\".\n\nTo specify a package name that includes spaces, enclose the name in single quotes.\n\nTo convert multiple 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 --manifest and --source-dir.",
       "strict": true,
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
@@ -203,7 +203,7 @@
           "char": "d",
           "summary": "Output directory to store the Metadata API–formatted files in.",
           "multiple": false,
-          "default": "metadataPackage_1680031466306",
+          "default": "metadataPackage_1680099170456",
           "deprecateAliases": true,
           "aliases": [
             "outputdir"
@@ -233,7 +233,7 @@
           "name": "source-dir",
           "type": "option",
           "char": "p",
-          "summary": "Comma-separated list of paths to the local source files to convert.",
+          "summary": "Paths to the local source files to convert.",
           "description": "The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder (in which case the operation is applied to all metadata types in the directory and its sub-directories).\n\nIf you specify this parameter, don’t specify --manifest or --metadata.",
           "multiple": true,
           "exclusive": [
@@ -250,7 +250,7 @@
           "name": "metadata",
           "type": "option",
           "char": "m",
-          "summary": "Comma-separated list of metadata component names to convert.",
+          "summary": "Metadata component names to convert.",
           "multiple": true,
           "exclusive": [
             "manifest",
@@ -266,7 +266,7 @@
     "project:delete:source": {
       "id": "project:delete:source",
       "summary": "Delete source from your project and from a non-source-tracked org.",
-      "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, \"sf project deploy start\".\n\nWhen you run this command, both the local source file and the metadata component in the org are deleted.",
+      "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 --manifest and --source-dir.",
       "strict": true,
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
@@ -382,7 +382,7 @@
           "name": "metadata",
           "type": "option",
           "char": "m",
-          "summary": "Comma-separated list of names of metadata components to delete.",
+          "summary": "Metadata components to delete.",
           "description": "If you specify this parameter, don’t specify --source-dir.",
           "multiple": true,
           "deprecateAliases": true,
@@ -392,7 +392,7 @@
           "name": "source-dir",
           "type": "option",
           "char": "p",
-          "summary": "Comma-separated list of source file paths to delete.",
+          "summary": "Source file paths to delete.",
           "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 parameter, don’t specify --metadata.",
           "multiple": true,
           "deprecateAliases": true,
@@ -541,7 +541,7 @@
           "name": "async",
           "type": "boolean",
           "summary": "Run the command asynchronously.",
-          "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 \"sf project deploy resume\". To check the status of the cancellation, run \"<%= config.bin %> project deploy report\".",
+          "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\".",
           "allowNo": false,
           "exclusive": [
             "wait"
@@ -571,7 +571,7 @@
           "type": "option",
           "char": "w",
           "summary": "Number of minutes to wait for the command to complete and display results.",
-          "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 \"sf project deploy resume\". To check the status of the cancellation, run \"<%= config.bin %> project deploy report\".",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the cancellation, run \"<%= config.bin %> project deploy resume\". To check the status of the cancellation, run \"<%= config.bin %> project deploy report\".",
           "helpValue": "<minutes>",
           "multiple": false,
           "exclusive": [
@@ -596,8 +596,8 @@
       ],
       "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:\n<%= config.bin %> <%= command.id %>  --source-dir force-app",
-        "Preview the deployment of all Apex classes:\n<%= config.bin %> <%= command.id %> --metadata ApexClass",
+        "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"
       ],
@@ -615,7 +615,7 @@
           "name": "ignore-conflicts",
           "type": "boolean",
           "char": "c",
-          "summary": "Ignore conflicts and deploy local files, even if they overwrite changes in the org.",
+          "summary": "Don't display conflicts in preview of the deployment.",
           "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.",
           "allowNo": false,
           "deprecateAliases": true
@@ -866,8 +866,7 @@
         "coverage-formatters": {
           "name": "coverage-formatters",
           "type": "option",
-          "summary": "format of the code coverage results",
-          "helpValue": "clover,cobertura,html-spa,html,json,json-summary,lcovonly,none,teamcity,text,text-summary",
+          "summary": "Format of the code coverage results",
           "multiple": true,
           "options": [
             "clover",
@@ -887,14 +886,14 @@
         "junit": {
           "name": "junit",
           "type": "boolean",
-          "summary": "output JUnit test results",
+          "summary": "Output JUnit test results.",
           "allowNo": false,
           "deprecateAliases": true
         },
         "results-dir": {
           "name": "results-dir",
           "type": "option",
-          "summary": "output directory for code coverage and JUnit results; defaults to the deploy ID",
+          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
           "multiple": false,
           "dependsOn": [
             "junit",
@@ -982,8 +981,7 @@
         "coverage-formatters": {
           "name": "coverage-formatters",
           "type": "option",
-          "summary": "format of the code coverage results",
-          "helpValue": "clover,cobertura,html-spa,html,json,json-summary,lcovonly,none,teamcity,text,text-summary",
+          "summary": "Format of the code coverage results.",
           "multiple": true,
           "options": [
             "clover",
@@ -1003,14 +1001,14 @@
         "junit": {
           "name": "junit",
           "type": "boolean",
-          "summary": "output JUnit test results",
+          "summary": "Output JUnit test results.",
           "allowNo": false,
           "deprecateAliases": true
         },
         "results-dir": {
           "name": "results-dir",
           "type": "option",
-          "summary": "output directory for code coverage and JUnit results; defaults to the deploy ID",
+          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
           "multiple": false,
           "dependsOn": [
             "junit",
@@ -1109,7 +1107,7 @@
           "name": "async",
           "type": "boolean",
           "summary": "Run the command asynchronously.",
-          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run \"sf project deploy resume\". To check the status of the deployment, run \"sf project deploy report\".",
+          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run \"<%= config.bin %> project deploy resume\". To check the status of the deployment, run \"<%= config.bin %> project deploy report\".",
           "allowNo": false,
           "exclusive": [
             "wait"
@@ -1273,7 +1271,7 @@
           "type": "option",
           "char": "w",
           "summary": "Number of minutes to wait for command to complete and display results.",
-          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run \"sf project deploy resume\". To check the status of the deployment, run \"sf project deploy report\".",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run \"<%= config.bin %> project deploy resume\". To check the status of the deployment, run \"<%= config.bin %> project deploy report\".",
           "helpValue": "<minutes>",
           "multiple": false,
           "exclusive": [
@@ -1284,7 +1282,7 @@
         "purge-on-delete": {
           "name": "purge-on-delete",
           "type": "boolean",
-          "summary": "specify that deleted components in the destructive changes manifest file are immediately eligible for deletion rather than being stored in the Recycle Bin",
+          "summary": "Specify that deleted components in the destructive changes manifest file are immediately eligible for deletion rather than being stored in the Recycle Bin.",
           "allowNo": false,
           "dependsOn": [
             "manifest"
@@ -1303,7 +1301,7 @@
         "pre-destructive-changes": {
           "name": "pre-destructive-changes",
           "type": "option",
-          "summary": "file path for a manifest (destructiveChangesPre.xml) of components to delete before the deploy",
+          "summary": "File path for a manifest (destructiveChangesPre.xml) of components to delete before the deploy",
           "multiple": false,
           "dependsOn": [
             "manifest"
@@ -1313,7 +1311,7 @@
         "post-destructive-changes": {
           "name": "post-destructive-changes",
           "type": "option",
-          "summary": "file path for a manifest (destructiveChangesPost.xml) of components to delete after the deploy",
+          "summary": "File path for a manifest (destructiveChangesPost.xml) of components to delete after the deploy.",
           "multiple": false,
           "dependsOn": [
             "manifest"
@@ -1323,8 +1321,7 @@
         "coverage-formatters": {
           "name": "coverage-formatters",
           "type": "option",
-          "summary": "format of the code coverage results",
-          "helpValue": "clover,cobertura,html-spa,html,json,json-summary,lcovonly,none,teamcity,text,text-summary",
+          "summary": "Format of the code coverage results.",
           "multiple": true,
           "options": [
             "clover",
@@ -1344,7 +1341,7 @@
         "junit": {
           "name": "junit",
           "type": "boolean",
-          "summary": "output JUnit test results",
+          "summary": "Output JUnit test results.",
           "allowNo": false,
           "dependsOn": [
             "coverage-formatters"
@@ -1354,7 +1351,7 @@
         "results-dir": {
           "name": "results-dir",
           "type": "option",
-          "summary": "output directory for code coverage and JUnit results; defaults to the deploy ID",
+          "summary": "Output directory for code coverage and JUnit results; defaults to the deploy ID.",
           "multiple": false,
           "dependsOn": [
             "coverage-formatters"
@@ -1642,7 +1639,7 @@
     "project:generate:manifest": {
       "id": "project:generate:manifest",
       "summary": "Create a project manifest that lists the metadata components you want to deploy or retrieve.",
-      "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 parameters, 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 parameter, 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.",
+      "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 parameters, 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 parameter, 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.",
       "strict": true,
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
@@ -1651,7 +1648,7 @@
         "force:source:manifest:create"
       ],
       "examples": [
-        "Create a manifest for deploying or retrieving all Apex classes:\n$ <%= config.bin %> <%= command.id %> --metadata ApexClass",
+        "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"
@@ -1690,7 +1687,7 @@
           "name": "metadata",
           "type": "option",
           "char": "m",
-          "summary": "Comma-separated list of names of metadata components to include in the manifest.",
+          "summary": "Names of metadata components to include in the manifest.",
           "multiple": true,
           "deprecateAliases": true,
           "delimiter": ","
@@ -1699,7 +1696,7 @@
           "name": "source-dir",
           "type": "option",
           "char": "p",
-          "summary": "Comma-separated list of paths to the local source files to include in the manifest.",
+          "summary": "Paths to the local source files to include in the manifest.",
           "multiple": true,
           "deprecateAliases": true,
           "aliases": [
@@ -1745,7 +1742,7 @@
           "name": "include-packages",
           "type": "option",
           "char": "c",
-          "summary": "Comma-separated list of package types (managed, unlocked) whose metadata is included in the manifest; by default, metadata in packages is ignored.",
+          "summary": "Package types (managed, unlocked) whose metadata is included in the manifest; by default, metadata in packages is ignored.",
           "multiple": true,
           "options": [
             "managed",
@@ -1788,8 +1785,8 @@
     },
     "project:list:ignored": {
       "id": "project:list:ignored",
-      "summary": "check your local project package directories for forceignored files",
-      "description": "check your local project package directories for forceignored files",
+      "summary": "Check your local project package directories for forceignored files.",
+      "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.",
       "strict": true,
       "pluginName": "@salesforce/plugin-deploy-retrieve",
       "pluginAlias": "@salesforce/plugin-deploy-retrieve",
@@ -1798,8 +1795,9 @@
         "force:source:ignored:list"
       ],
       "examples": [
-        "$ <%= config.bin %> <%= command.id %>",
-        "$ <%= config.bin %> <%= command.id %> --source-dir force-app"
+        "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"
       ],
       "deprecateAliases": true,
       "flags": {
@@ -1815,7 +1813,7 @@
           "name": "source-dir",
           "type": "option",
           "char": "p",
-          "summary": "file or directory of files that the command checks for foreceignored files",
+          "summary": "File or directory of files that the command checks for foreceignored files.",
           "multiple": false,
           "deprecateAliases": true,
           "aliases": [
@@ -1917,8 +1915,8 @@
         "retrieve:metadata:preview"
       ],
       "examples": [
-        "Preview the retrieve of all changes from the org:\n<%= config.bin %> <%= command.id %>",
-        "Preview the retrieve when ignoring any conflicts:\n<%= config.bin %> <%= command.id %> --ignore-conflicts"
+        "Preview the retrieve of all changes from your default org:\n<%= config.bin %> <%= command.id %>",
+        "Preview the retrieve when ignoring any conflicts from an org with alias \"my-scratch\":\n<%= config.bin %> <%= command.id %> --ignore-conflicts --target-org my-scratch"
       ],
       "deprecateAliases": true,
       "flags": {
@@ -1934,7 +1932,7 @@
           "name": "ignore-conflicts",
           "type": "boolean",
           "char": "c",
-          "summary": "Ignore conflicts and preview the retrieve of remote components, even if they will overwrite local changes.",
+          "summary": "Don't display conflicts in the preview of the retrieval.",
           "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.",
           "allowNo": false,
           "deprecateAliases": true
@@ -1966,8 +1964,8 @@
         "retrieve:metadata"
       ],
       "examples": [
-        "Retrieve remote changes:\n<%= config.bin %> <%= command.id %>",
-        "Retrieve the source files in a directory:\n<%= config.bin %> <%= command.id %> --source-dir path/to/source",
+        "Retrieve remote changes from your default org:\n<%= config.bin %> <%= command.id %>",
+        "Retrieve the source files in a directory from an org with alias \"my-scratch\":\n<%= config.bin %> <%= command.id %> --source-dir path/to/source --target-org my-scratch",
         "Retrieve a specific Apex class and the objects whose source is in a directory (both examples are equivalent):\n<%= config.bin %> <%= command.id %> --source-dir path/to/apex/classes/MyClass.cls path/to/source/objects\n<%= config.bin %> <%= command.id %> --source-dir path/to/apex/classes/MyClass.cls --source-dir path/to/source/objects",
         "Retrieve all Apex classes:\n<%= config.bin %> <%= command.id %> --metadata ApexClass",
         "Retrieve a specific Apex class:\n<%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass",

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@salesforce/plugin-deploy-retrieve",
     "description": "deploy and retrieve commands for sf",
-    "version": "1.8.5-beta.7",
+    "version": "1.8.5-beta.9",
     "author": "Salesforce",
     "bugs": "https://github.com/forcedotcom/cli/issues",
     "dependencies": {
@@ -270,7 +270,7 @@
         }
     },
     "sfdx": {
-        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.5-beta.7.crt",
-        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.5-beta.7.sig"
+        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.5-beta.9.crt",
+        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.5-beta.9.sig"
     }
 }