From 4f4bfdf4b5a5bfccb556aff5f20ec1dfc137c662 Mon Sep 17 00:00:00 2001 From: AndrewStopchenko-SO <63401193+AndrewStopchenko-SO@users.noreply.github.com> Date: Thu, 10 Oct 2024 16:33:58 +0200 Subject: [PATCH] Update README.md (#3049) Fix typo in the "Salesforce" word for the CLI v2.61.8 release. --- releasenotes/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/releasenotes/README.md b/releasenotes/README.md index 19876f3f0..2e9f3ca75 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -76,7 +76,7 @@ These changes are in the Salesforce CLI release candidate. We plan to include th * NEW: Download and install Salesforce CLI on Windows ARM64 computers with our new `sf-arm64.exe` installer. We're in the process of updating the [download page](https://developer.salesforce.com/tools/salesforcecli) with this new option, but in the meantime you can download the `stable` executable [here](https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-arm64.exe). (oclif PR [#1559](https://github.com/oclif/oclif/pull/1559)) -* NEW: When you create a sandbox with the `org create sandbox` command, you can now specify the public group of Salesforce users that can access the sandbox by including either the `activationUserGroupId` or `activationUserGroupName` option (but not both) in the sandbox definition file. This example specifies that the Salesforc public user group with name `ExpertUsers` can access the sandbox after it's created: +* NEW: When you create a sandbox with the `org create sandbox` command, you can now specify the public group of Salesforce users that can access the sandbox by including either the `activationUserGroupId` or `activationUserGroupName` option (but not both) in the sandbox definition file. This example specifies that the Salesforce public user group with name `ExpertUsers` can access the sandbox after it's created: ``` {