@salesforce/cli 2.42.0 → 2.42.1

package/README.md

@@ -24,7 +24,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (--version|-v)
-@salesforce/cli/2.42.0 linux-x64 node-v20.12.2
+@salesforce/cli/2.42.1 linux-x64 node-v20.12.2
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@salesforce/cli",
-  "version": "2.42.0",
+  "version": "2.42.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@salesforce/cli",
-      "version": "2.42.0",
+      "version": "2.42.1",
       "hasInstallScript": true,
       "license": "BSD-3-Clause",
       "dependencies": {

package/oclif.manifest.json

@@ -1814,7 +1814,7 @@
     "project:deploy:pipeline:quick": {
       "aliases": [],
       "args": {},
-      "description": "Before you run this command, first create a validated deployment with the \"sf project deploy pipeline validate\" command, which returns a job ID. Validated deployments haven't been deployed to the org yet; you deploy them with this command. Either pass the job ID to this command or use the --use-most-recent flag to use the job ID of the most recently validated deployment. For the quick deploy to succeed, the associated validated deployment must also have succeeded.\n\nExecuting this quick deploy command takes less time than a standard deploy because it skips running Apex tests. These tests were previously run as part of the validation. Validating first and then running a quick deploy is useful if the deployment to your production org take several hours and you don’t want to risk a failed deploy.\n\nThis command doesn't support source-tracking. The source you deploy overwrites the corresponding metadata in your org. This command doesn’t attempt to merge your source with the versions in your org.",
+      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nBefore you run this command, create a validated deployment with the \"project deploy pipeline validate\" command, which returns a job ID. Validated deployments haven't been deployed to the org yet; you deploy them with this command. Either pass the job ID to this command or use the --use-most-recent flag to use the job ID of the most recently validated deployment. For the quick deploy to succeed, the associated validated deployment must also have succeeded.\n\nExecuting this quick deploy command takes less time than a standard deploy because it skips running Apex tests. These tests were previously run as part of the validation. Validating first and then running a quick deploy is useful if the deployment to your production org take several hours and you don’t want to risk a failed deploy.\n\nThis command doesn't support source-tracking. The source you deploy overwrites the corresponding metadata in your org. This command doesn’t attempt to merge your source with the versions in your org.",
       "examples": [
         "Run a quick deploy using your default Devops Center org and a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
         "Asynchronously run a quick deploy of the most recently validated deployment using an org with alias \"my-prod-org\":\n<%= config.bin %> <%= command.id %> --async --use-most-recent --devops-center-username my-prod-org"
@@ -1857,11 +1857,8 @@
           ],
           "name": "wait",
           "summary": "Number of minutes to wait for command to complete and display results.",
-          "default": {
-            "quantity": 33,
-            "unit": 0
-          },
-          "hasDynamicHelp": false,
+          "default": "33 minutes",
+          "hasDynamicHelp": true,
           "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
@@ -1917,7 +1914,7 @@
     "project:deploy:pipeline:report": {
       "aliases": [],
       "args": {},
-      "description": "Run this command by either indicating a job ID or specifying the —use-most-recent flag to use the job ID of the most recent deploy operation.",
+      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nRun this command by either indicating a job ID or specifying the —use-most-recent flag to use the job ID of the most recent deploy operation.",
       "examples": [
         "Check the status using a job ID:\n<%= config.bin %> <%= command.id %> --devops-center-username MyStagingSandbox --job-id 0Af0x000017yLUFCA2",
         "Check the status of the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --devops-center-username MyStagingSandbox --use-most-recent"
@@ -1981,7 +1978,7 @@
     "project:deploy:pipeline:resume": {
       "aliases": [],
       "args": {},
-      "description": "Use this command to resume watching a pipeline deploy operation if the original command times out or you specified the --async flag.\n\nRun this command by either indicating a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.",
+      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command. \n\nUse this command to resume watching a pipeline deploy operation if the original command times out or you specified the --async flag.\n\nRun this command by either indicating a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.",
       "examples": [
         "Resume watching a deploy operation using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
         "Resume watching the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --use-most-recent"
@@ -2043,11 +2040,8 @@
           ],
           "name": "wait",
           "summary": "Number of minutes to wait for command to complete and display results.",
-          "default": {
-            "quantity": 33,
-            "unit": 0
-          },
-          "hasDynamicHelp": false,
+          "default": "33 minutes",
+          "hasDynamicHelp": true,
           "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
@@ -2077,7 +2071,7 @@
     "project:deploy:pipeline:start": {
       "aliases": [],
       "args": {},
-      "description": "Before you run this command, changes in the pipeline stage's branch must be merged in the source control repository.",
+      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nBefore you run this command, changes in the pipeline stage's branch must be merged in the source control repository.",
       "examples": [
         "Deploy changes in the Staging branch to the Staging environment (sandbox), if the previous stage is the bundling stage:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name staging --devops-center-username MyStagingSandbox --bundle-version-name 1.0",
         "Deploy all changes in the main branch to the release environment:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name main --devops-center-username MyReleaseOrg --deploy-all"
@@ -2173,11 +2167,8 @@
           ],
           "name": "wait",
           "summary": "Number of minutes to wait for command to complete and display results.",
-          "default": {
-            "quantity": 33,
-            "unit": 0
-          },
-          "hasDynamicHelp": false,
+          "default": "33 minutes",
+          "hasDynamicHelp": true,
           "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
@@ -2222,7 +2213,7 @@
     "project:deploy:pipeline:validate": {
       "aliases": [],
       "args": {},
-      "description": "A validation runs Apex tests to verify whether a deployment will succeed without actually deploying the metadata to your environment, so you can then quickly deploy the changes later without re-running the tests.",
+      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nA validation runs Apex tests to verify whether a deployment will succeed without actually deploying the metadata to your environment, so you can then quickly deploy the changes later without re-running the tests.",
       "examples": [
         "Perform a validate-only deployment from the Staging branch to the Staging environment (sandbox):\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name staging --devops-center-username MyStagingSandbox",
         "Perform a validate-only deployment of all changes from the main branch to the release environment:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name main --devops-center-username MyReleaseOrg --deploy-all"
@@ -2318,11 +2309,8 @@
           ],
           "name": "wait",
           "summary": "Number of minutes to wait for command to complete and display results.",
-          "default": {
-            "quantity": 33,
-            "unit": 0
-          },
-          "hasDynamicHelp": false,
+          "default": "33 minutes",
+          "hasDynamicHelp": true,
           "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
@@ -5391,5 +5379,5 @@
       ]
     }
   },
-  "version": "2.42.0"
+  "version": "2.42.1"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "2.42.0",
+  "version": "2.42.1",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run.js",
@@ -78,7 +78,7 @@
       "@salesforce/plugin-custom-metadata": "3.3.6",
       "@salesforce/plugin-community": "3.2.8",
       "@salesforce/plugin-dev": "2.3.1",
-      "@salesforce/plugin-devops-center": "1.2.9",
+      "@salesforce/plugin-devops-center": "1.2.10",
       "@salesforce/plugin-env": "3.0.29",
       "@salesforce/plugin-functions": "1.23.0",
       "@salesforce/plugin-signups": "2.3.1",