chore(release): bump to 2.62.5

README.md

@@ -24,7 +24,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (--version|-v)
-@salesforce/cli/2.62.4 linux-x64 node-v20.17.0
+@salesforce/cli/2.62.5 linux-x64 node-v20.17.0
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND
@@ -903,16 +903,16 @@ EXAMPLES
     $ sf api request graphql --body example.txt --stream-to-file output.txt --include
 ```
 
-_See code: [@salesforce/plugin-api](https://github.com/salesforcecli/plugin-api/blob/1.3.0/src/commands/api/request/graphql.ts)_
+_See code: [@salesforce/plugin-api](https://github.com/salesforcecli/plugin-api/blob/1.3.1/src/commands/api/request/graphql.ts)_
 
 ## `sf api request rest [URL]`
 
 Make an authenticated HTTP request using the Salesforce REST API.
 
 ```
 USAGE
-  $ sf api request rest [URL] -o <value> [--flags-dir <value>] [--api-version <value>] [-i | -S Example: report.xlsx]
-    [-X GET|POST|PUT|PATCH|HEAD|DELETE|OPTIONS|TRACE] [-H key:value...] [-f file] [-b file]
+  $ sf api request rest [URL] -o <value> [--flags-dir <value>] [-i | -S Example: report.xlsx] [-X
+    GET|POST|PUT|PATCH|HEAD|DELETE|OPTIONS|TRACE] [-H key:value...] [-f file | -b file]
 
 ARGUMENTS
   URL  Salesforce API endpoint
@@ -923,13 +923,13 @@ FLAGS
   -X, --method=<option>                      HTTP method for the request.
                                              <options: GET|POST|PUT|PATCH|HEAD|DELETE|OPTIONS|TRACE>
   -b, --body=file                            File or content for the body of the HTTP request. Specify "-" to read from
-                                             standard input or "" for an empty body.
+                                             standard input or "" for an empty body. If passing a file, prefix the
+                                             filename with '@'.
   -f, --file=file                            JSON file that contains values for the request header, body, method, and
                                              URL.
   -i, --include                              Include the HTTP response status and headers in the output.
   -o, --target-org=<value>                   (required) Username or alias of the target org. Not required if the
                                              `target-org` configuration variable is already set.
-      --api-version=<value>                  Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -946,30 +946,30 @@ DESCRIPTION
 EXAMPLES
   List information about limits in the org with alias "my-org":
 
-    $ sf api request rest 'limits' --target-org my-org
+    $ sf api request rest 'services/data/v56.0/limits' --target-org my-org
 
   List all endpoints in your default org; write the output to a file called "output.txt" and include the HTTP response
   status and headers:
 
-    $ sf api request rest '/' --stream-to-file output.txt --include
+    $ sf api request rest '/services/data/v56.0/' --stream-to-file output.txt --include
 
   Get the response in XML format by specifying the "Accept" HTTP header:
 
-    $ sf api request rest 'limits' --header 'Accept: application/xml'
+    $ sf api request rest '/services/data/v56.0/limits' --header 'Accept: application/xml'
 
   Create an account record using the POST method; specify the request details directly in the "--body" flag:
 
-    $ sf api request rest sobjects/account --body "{\"Name\" : \"Account from REST API\",\"ShippingCity\" : \
-      \"Boise\"}" --method POST
+    $ sf api request rest /services/data/v56.0/sobjects/account --body "{\"Name\" : \"Account from REST \
+      API\",\"ShippingCity\" : \"Boise\"}" --method POST
 
-  Create an account record using the information in a file called "info.json":
+  Create an account record using the information in a file called "info.json" (note the @ prefixing the file name):
 
-    $ sf api request rest 'sobjects/account' --body info.json --method POST
+    $ sf api request rest '/services/data/v56.0/sobjects/account' --body @info.json --method POST
 
   Update an account record using the PATCH method:
 
-    $ sf api request rest 'sobjects/account/<Account ID>' --body "{\"BillingCity\": \"San Francisco\"}" --method \
-      PATCH
+    $ sf api request rest '/services/data/v56.0/sobjects/account/<Account ID>' --body "{\"BillingCity\": \"San \
+      Francisco\"}" --method PATCH
 
   Store the values for the request header, body, and so on, in a file, which you then specify with the --file flag;
   see the description of --file for more information:
@@ -1012,7 +1012,7 @@ FLAG DESCRIPTIONS
     https://github.com/salesforcecli/plugin-api/tree/main/test/test-files/data-project.
 ```
 
-_See code: [@salesforce/plugin-api](https://github.com/salesforcecli/plugin-api/blob/1.3.0/src/commands/api/request/rest.ts)_
+_See code: [@salesforce/plugin-api](https://github.com/salesforcecli/plugin-api/blob/1.3.1/src/commands/api/request/rest.ts)_
 
 ## `sf autocomplete [SHELL]`
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "2.62.4",
+  "version": "2.62.5",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run.js",
@@ -154,7 +154,7 @@
     "@salesforce/core": "^8.2.3",
     "@salesforce/kit": "^3.1.6",
     "@salesforce/plugin-apex": "3.5.1",
-    "@salesforce/plugin-api": "1.3.0",
+    "@salesforce/plugin-api": "1.3.1",
     "@salesforce/plugin-auth": "3.6.65",
     "@salesforce/plugin-data": "3.6.9",
     "@salesforce/plugin-deploy-retrieve": "3.12.17",

yarn.lock

@@ -604,22 +604,14 @@
     "@smithy/types" "^3.5.0"
     tslib "^2.6.2"
 
-"@aws-sdk/[email protected]":
+"@aws-sdk/[email protected]", "@aws-sdk/types@^3.222.0":
   version "3.664.0"
   resolved "https://registry.yarnpkg.com/@aws-sdk/types/-/types-3.664.0.tgz#e6de1c0a2cdfe4f1e43271223dc0b55e613ced58"
   integrity sha512-+GtXktvVgpreM2b+NJL9OqZGsOzHwlCUrO8jgQUvH/yA6Kd8QO2YFhQCp0C9sSzTteZJVqGBu8E0CQurxJHPbw==
   dependencies:
     "@smithy/types" "^3.5.0"
     tslib "^2.6.2"
 
-"@aws-sdk/types@^3.222.0":
-  version "3.649.0"
-  resolved "https://registry.yarnpkg.com/@aws-sdk/types/-/types-3.649.0.tgz#a6828e6338dc755e0c30b5f77321e63425a88aed"
-  integrity sha512-PuPw8RysbhJNlaD2d/PzOTf8sbf4Dsn2b7hwyGh7YVG3S75yTpxSAZxrnhKsz9fStgqFmnw/jUfV/G+uQAeTVw==
-  dependencies:
-    "@smithy/types" "^3.4.0"
-    tslib "^2.6.2"
-
 "@aws-sdk/[email protected]":
   version "3.568.0"
   resolved "https://registry.yarnpkg.com/@aws-sdk/util-arn-parser/-/util-arn-parser-3.568.0.tgz#6a19a8c6bbaa520b6be1c278b2b8c17875b91527"
@@ -2018,10 +2010,10 @@
     "@salesforce/sf-plugins-core" "^11.3.7"
     ansis "^3.3.1"
 
-"@salesforce/[email protected].0":
-  version "1.3.0"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-api/-/plugin-api-1.3.0.tgz#491f526afd3f2330eabfe4ea65dfb71de0d5626c"
-  integrity sha512-DtCgRjlTUbxQAuCSo4g4xhbOotQcWY3dCOz3es7ihTtpevGj09vczs5acE7u8If25+XCnIdstOO1IyNoJIAzXg==
+"@salesforce/[email protected].1":
+  version "1.3.1"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-api/-/plugin-api-1.3.1.tgz#64bf8420e76e48ed2e2d05d1b5fd25a0b239cd46"
+  integrity sha512-1QCtXPjvL3ZpyYGMdapPFyYOmD+s5ZmfmYKKJZafLjRA1ta6nMhwe29W+sVUd5BYu/WMYMkNFeb/hFO7iB+cew==
   dependencies:
     "@oclif/core" "^4"
     "@salesforce/core" "^8.4.0"
@@ -2860,13 +2852,6 @@
     "@smithy/util-stream" "^3.1.9"
     tslib "^2.6.2"
 
-"@smithy/types@^3.4.0":
-  version "3.4.2"
-  resolved "https://registry.yarnpkg.com/@smithy/types/-/types-3.4.2.tgz#aa2d087922d57205dbad68df8a45c848699c551e"
-  integrity sha512-tHiFcfcVedVBHpmHUEUHOCCih8iZbIAYn9NvPsNzaPm/237I3imdDdZoOC8c87H5HBAVEa06tTgb+OcSWV9g5w==
-  dependencies:
-    tslib "^2.6.2"
-
 "@smithy/types@^3.5.0":
   version "3.5.0"
   resolved "https://registry.yarnpkg.com/@smithy/types/-/types-3.5.0.tgz#9589e154c50d9c5d00feb7d818112ef8fc285d6e"