sf RNs Nov 8 (#2558)

* sf RNs Nov 8 * Update README.md * Update README.md * Update README.md * Update README.md * Update README.md * Update README.md
forcedotcom · Nov 8, 2023 · 9d36080 · 9d36080
1 parent 22192b0
commit 9d36080
Showing 1 changed file with 42 additions and 6 deletions.
diff --git a/releasenotes/README.md b/releasenotes/README.md
@@ -26,12 +26,52 @@ Additional documentation:
 * [Salesforce CLI Setup Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm)
 
 
-## 2.16.7 (Nov 8, 2023) [stable-rc]
+## 2.17.8 (Nov 15, 2023) [stable-rc]
 
 These changes are in the Salesforce CLI release candidate. We plan to include these changes in next week's official release. This list isn't final and is subject to change.
 
 ------------
 
+* NEW: Easily uninstall all user-installed and linked plugins, including JIT plugins, with the new `plugins reset` command.
+
+    ```bash
+    sf plugins reset
+    ```
+
+    After you run the command, you're left with only the core Salesforce CLI plugins, as if you had just installed the CLI from scratch. (oclif plugin-plugins PR [#701](https://github.com/oclif/plugin-plugins/pull/701))
+
+* CHANGE: We've changed the official names of these commands that display org limits and counts. Both the new and old names work, but the [CLI Reference](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_unified.htm) will soon list only the new name. (plugin-limits PR [#673](https://github.com/salesforcecli/plugin-limits/pull/673))
+
+    |New Name|Old Name|Description|
+    |---|---|---|
+    |`org list limits`|`limits api display`|Display information about limits in your org.|
+    |`org list sobject record-counts`|`limits recordcounts display`|Display record counts for the specified standard or custom objects.|
+
+* FIX: Salesforce CLI now handles the `SF_CONTAINER_MODE` and `SF_DOMAIN_RETRY` environment variables; previously it handled only the old `SFDX_` equivalents (`SFDX_CONTAINER_MODE` and `SFDX_DOMAIN_RETRY`). And `SF_CONTAINER_MODE` [isn't documented](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_env_variables.htm) -- oopsie!  We're in the process of fixing that doc bug too.   (GitHub issue [#2554](https://github.com/forcedotcom/cli/issues/2554), plugin-org PR [#857](https://github.com/salesforcecli/plugin-org/pull/857))
+
+* FIX: We've improved how `sf plugins install https://github.com/foo/bar` works, which sometimes returned an error. (oclif plugin-plugins PR [#702](https://github.com/oclif/plugin-plugins/pull/702))
+
+* FIX: Salesforce DX projects now support these metadata types. (GitHub issue [#2527](https://github.com/forcedotcom/cli/issues/2527))
+
+    * CareBenefitVerifySettings
+    * CareProviderAfflRoleConfig
+    * ContextDefinition
+    * DiscoveryStory
+    * DocumentCategory
+    * DocumentCategoryDocumentType
+    * ExpressionSetMessageToken
+    * ExternalAIModel
+    * ManagedEventSubscription
+    * RecordAggregationDefinition
+    * RegisteredExternalService
+    * WebStoreBundle
+
+## 2.16.7 (Nov 8, 2023) [stable]
+
+ANNOUNCEMENT: If you install Salesforce CLI using `npm`, be aware that Node.js 14 and 16 are both officially [end-of-life](https://github.com/forcedotcom/cli/issues/1985). 
+
+-------------
+
 * NEW: Use the new `scopeProfiles` option of the `sfdx-project.json` file to control which profile settings are included in a new package version when you run the `package create version` command. If you set `scopeProfiles` to `true` for a package directory, profile settings from only the package directory being packaged are included, and profile settings outside of that package directory are ignored. When you set `scopeProfiles` to `false` (the default value), the new package version includes relevant pieces of profile settings in any package directory defined in `sfdx-project.json`.
 
     The `scopeProfiles` option is a child of `packageDirectory`, as shown in this example. 
@@ -68,11 +108,7 @@ These changes are in the Salesforce CLI release candidate. We plan to include th
 
 * FIX: You can now use the `--dev-debug` flag on its own to get debug log files from oclif and Salesforce CLI when you run a command; previously you also had to set the SF_LOG_LEVEL environment variable.  If the environment variable isn't set, then the default log level is `trace`.  (salesforcecli PR [#1246](https://github.com/salesforcecli/cli/pull/1246))
 
-## 2.15.9 (Nov 1, 2023) [stable]
-
-ANNOUNCEMENT: If you install Salesforce CLI using `npm`, be aware that Node.js 14 and 16 are both officially [end-of-life](https://github.com/forcedotcom/cli/issues/1985). 
-
--------------
+## 2.15.9 (Nov 1, 2023)
 
 * NEW: The `dev convert script` command for migrating your CI scripts to use the `sf`-style commands now handles `sfdx` commands that span multiple lines.  For example, the command converts this: