From 3b4cdc7e2a3e5a2f5f932c3b9e81ada6065c477b Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Thu, 5 Feb 2026 15:38:54 -0800 Subject: [PATCH 01/11] Update release notes for version 2.123.6 Updated release notes for version 2.123.6, including new features and fixes. --- releasenotes/README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/releasenotes/README.md b/releasenotes/README.md index de38b6bac..cf05db708 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -25,12 +25,16 @@ Additional documentation: * [Salesforce CLI Plugin Developer Guide](https://github.com/salesforcecli/cli/wiki/Quick-Introduction-to-Developing-sf-Plugins) * [Salesforce CLI Setup Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm) -## 2.122.6 (Feb 11, 2026) [stable-rc] +## 2.123.6 (Feb 18, 2026) [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: (needs better desc and an example) Generate a package ZIP file that you can use for debugging or to examine the package contents when you run `package version create` with the new `--generate-pkg-zip` flag. (plugin-packaging PR [#1117](https://github.com/salesforcecli/plugin-packaging/pull/1117)) + +## 2.122.6 (Feb 11, 2026) [stable] + * NEW: Skip retrieving new or changed metadata from your org when you publish an agent's authoring bundle with the new `--skip-retrieve` flag of `agent publish authoring-bundle`. This feature is useful when you publish the authoring bundle in a CI job and don't need to retrieve the metadata back to your DX project because it already has it; skipping the retrieve can save time. This example shows how to publish an authoring bundle with API name `MyAuthoringBundle` to the org with alias `my-dev-org`, but not retrieve any of the metadata: ```bash @@ -45,7 +49,7 @@ These changes are in the Salesforce CLI release candidate. We plan to include th * FIX: The `project deploy start` command now correctly handles an empty `deploy-cache.json` file (an internal file that the CLI uses to manage deployments) rather than throwing a confusing error. (GitHub Issue [#3387](https://github.com/forcedotcom/cli/issues/3387), sfdx-core PR [#1260](https://github.com/forcedotcom/sfdx-core/pull/1260)) -## 2.121.7 (Feb 4, 2026) [stable] +## 2.121.7 (Feb 4, 2026) * NEW: Open your org right in Agentforce Studio, specifically in the list view that displays all your agents, with the new `org open authoring-bundle` command. This example opens Agentforce Studio in an org with alias `my-org`; the command opens the browser in incognito mode: From 9616181f7302c14ee0a14fddbf9a639879cf3cc5 Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Tue, 10 Feb 2026 17:01:28 -0800 Subject: [PATCH 02/11] Revise release notes for clarity and updates Updated release notes to clarify new features and command changes, including the addition of a package ZIP file generation and reorganization of commands under 'template generate'. --- releasenotes/README.md | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/releasenotes/README.md b/releasenotes/README.md index cf05db708..ba3013377 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -31,7 +31,28 @@ These changes are in the Salesforce CLI release candidate. We plan to include th ------------ -* NEW: (needs better desc and an example) Generate a package ZIP file that you can use for debugging or to examine the package contents when you run `package version create` with the new `--generate-pkg-zip` flag. (plugin-packaging PR [#1117](https://github.com/salesforcecli/plugin-packaging/pull/1117)) +* NEW: Generate a package ZIP file that you can use for debugging or to examine the package contents when you run `package version create` with the new `--generate-pkg-zip` flag. (plugin-packaging PR [#1117](https://github.com/salesforcecli/plugin-packaging/pull/1117)) + +* CHANGE: We reorganized all the commands in [plugin-templates](https://github.com/salesforcecli/plugin-templates) under a top-level topic called `template generate`. As a result, you can now take advantage of autocomplete to list all the available templates to generate things, such as DX projects or Apex classes. + + But don't worry, we also added aliases to the moved commands, so that the old command names will still work. But they display a deprecation warning that the command name has changed. + + Here are all the affected commands. (plugin-templates PR [#840](https://github.com/salesforcecli/plugin-templates/pull/840), + + | Old command | New command | + | ----------- | ----------- | + | apex generate class | template generate apex class | + | apex generate trigger | template generate apex trigger | + | analytics generate template | template generate analytics template | + | lightning generate app | template generate lightning app | + | lightning generate component | template generate lightning component | + | lightning generate event | template generate lightning event | + | lightning generate interface | template generate lightning interface | + | lightning generate test | template generate lightning test | + | project generate | template generate project | + | static-resource generate | template generate static-resource | + | visualforce generate component | template generate visualforce component | + | visualforce generate page | template generate visualforce page | ## 2.122.6 (Feb 11, 2026) [stable] From 519734b79f1f8fed2691a77601562308b76e6ff6 Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Tue, 10 Feb 2026 17:12:05 -0800 Subject: [PATCH 03/11] Document new command for generating Experience Cloud site Added details about the new command to generate an Experience Cloud site, including usage instructions and a link to additional resources. --- releasenotes/README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/releasenotes/README.md b/releasenotes/README.md index ba3013377..8e54b230b 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -31,6 +31,18 @@ These changes are in the Salesforce CLI release candidate. We plan to include th ------------ +* NEW: Generate an Experience Cloud site in your DX project with the new `template generate digital-experience site` command. After you pass the command the name of a template (currently only `BuildYourOwnLWR`), the new site name, and an URL path prefix, all the required metadata files are created locally. The metadata files correspond to metadata components such as DigitalExperienceConfig, DigitalExperienceBundle, Network, and CustomSite. + + The `BuildYourOwnLWR` template creates suepr fast digital experiences, such as websites, microsites, and portals, using the Lightning Web Components programming model. Powered by Lightning Web Runtime (LWR), this customizable template delivers unparalleled site performance. For additional details, see this Salesforce Help topic: https://help.salesforce.com/s/articleView?id=experience.rss_build_your_own_lwr.htm. + + Here's an example that generates the metadata files in the `force-app/main/default` directory: + + ```bash + sf template generate digital-experience site --template BuildYourOwnLWR --name mysite --url-path-prefix mysite --output-dir force-app/main/default + ``` + + (plugin-templates PR [#829](https://github.com/salesforcecli/plugin-templates/pull/829)) + * NEW: Generate a package ZIP file that you can use for debugging or to examine the package contents when you run `package version create` with the new `--generate-pkg-zip` flag. (plugin-packaging PR [#1117](https://github.com/salesforcecli/plugin-packaging/pull/1117)) * CHANGE: We reorganized all the commands in [plugin-templates](https://github.com/salesforcecli/plugin-templates) under a top-level topic called `template generate`. As a result, you can now take advantage of autocomplete to list all the available templates to generate things, such as DX projects or Apex classes. From 82151125c0cf6fc7620a9d06e0e632df690df96b Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Tue, 10 Feb 2026 17:32:28 -0800 Subject: [PATCH 04/11] Document new 'metadata enrich' command in README Added details about the new 'metadata enrich' command for AI-generated descriptions in metadata source files, including usage examples and requirements. --- releasenotes/README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/releasenotes/README.md b/releasenotes/README.md index 8e54b230b..2b7a06ff8 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -31,6 +31,18 @@ These changes are in the Salesforce CLI release candidate. We plan to include th ------------ +* NEW: (Developer Preview) Add AI-generated descriptions in the metadata source files in your local DX project with the new `metadata enrich` command. These enriched descriptions succinctly outline the metadata component’s purpose and capabilities, which in turn provide context when vibe coding with an AI tool, such as Agentforce Vibes. + + Currently, this command supports enriching only Lightning Web Components, represented by the LightningComponentBundle metadata type. Even though the command updates only local files in your DX project, you're still required to authorize and specify an org, which is how the command accesses a large language model (LLM). Your org must be eligible for metadata enrichment; contact your Salesforce admin. + + This example shows how to enrich the local metadata files corresonding to the `HelloWorld` LightningComponentBundle component; it uses the org with alias `my-org`: + + ``` + sf metadata enrich --metadata LightningComponentBundle:HelloWorld --target-org my-org + ``` + + This command lives in the new [plugin-metadata-enrichment](https://github.com/salesforcecli/plugin-metadata-enrichment) plugin. + * NEW: Generate an Experience Cloud site in your DX project with the new `template generate digital-experience site` command. After you pass the command the name of a template (currently only `BuildYourOwnLWR`), the new site name, and an URL path prefix, all the required metadata files are created locally. The metadata files correspond to metadata components such as DigitalExperienceConfig, DigitalExperienceBundle, Network, and CustomSite. The `BuildYourOwnLWR` template creates suepr fast digital experiences, such as websites, microsites, and portals, using the Lightning Web Components programming model. Powered by Lightning Web Runtime (LWR), this customizable template delivers unparalleled site performance. For additional details, see this Salesforce Help topic: https://help.salesforce.com/s/articleView?id=experience.rss_build_your_own_lwr.htm. From bf93e93923d87312169b43ba0a612650595b6484 Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Tue, 10 Feb 2026 17:45:32 -0800 Subject: [PATCH 05/11] Fix CLI performance and add skip retrieve feature Fix slow CLI command execution in expired scratch org directories and add new feature to skip metadata retrieval during agent bundle publishing. --- releasenotes/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/releasenotes/README.md b/releasenotes/README.md index 2b7a06ff8..8467c8746 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -78,6 +78,8 @@ These changes are in the Salesforce CLI release candidate. We plan to include th | visualforce generate component | template generate visualforce component | | visualforce generate page | template generate visualforce page | +* FIX: CLI commands that don't require an org no longer run really slowly in directories in which the `target-org` config variable points to a long-expired scratch org. (GitHub Issue [#3425](https://github.com/forcedotcom/cli/issues/3425), jsforce PR [#1772](https://github.com/jsforce/jsforce/pull/1772)) + ## 2.122.6 (Feb 11, 2026) [stable] * NEW: Skip retrieving new or changed metadata from your org when you publish an agent's authoring bundle with the new `--skip-retrieve` flag of `agent publish authoring-bundle`. This feature is useful when you publish the authoring bundle in a CI job and don't need to retrieve the metadata back to your DX project because it already has it; skipping the retrieve can save time. This example shows how to publish an authoring bundle with API name `MyAuthoringBundle` to the org with alias `my-dev-org`, but not retrieve any of the metadata: From 436b35fdce1eee4ef131090a5ad92e35c860c66d Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Wed, 11 Feb 2026 09:33:54 -0800 Subject: [PATCH 06/11] Update release notes for fixes in metadata retrieval and CLI Fixed issues with retrieving DigitalExperienceBundle metadata and improved CLI performance in expired scratch orgs. --- releasenotes/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/releasenotes/README.md b/releasenotes/README.md index 8467c8746..ede7c167b 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -78,6 +78,8 @@ These changes are in the Salesforce CLI release candidate. We plan to include th | visualforce generate component | template generate visualforce component | | visualforce generate page | template generate visualforce page | +* FIX: Retrieving DigitalExperienceBundle metadata components now works correctly after you update the Digital Experience site in the org. Specifically, let's say you created a page in the Digital Experience site using the in-org builder, and then retrieved it to your DX projec with the `project retrieve start` CLI command. You then you changed the mobile layout in the org, and retrieved the metadata again. Before this fix, the `mobile.json` file was incorrectly created at the top-level for the page; now it's corrected nested in `mobile/mobile.json`. (source-deploy-retrieve PR [#1680](https://github.com/forcedotcom/source-deploy-retrieve/pull/1680)) + * FIX: CLI commands that don't require an org no longer run really slowly in directories in which the `target-org` config variable points to a long-expired scratch org. (GitHub Issue [#3425](https://github.com/forcedotcom/cli/issues/3425), jsforce PR [#1772](https://github.com/jsforce/jsforce/pull/1772)) ## 2.122.6 (Feb 11, 2026) [stable] From b45a3d21678e429d7dcc418c840639aba74afc25 Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Wed, 11 Feb 2026 09:35:47 -0800 Subject: [PATCH 07/11] Fix wording in DigitalExperienceBundle retrieval note Corrected the description of the fix regarding the retrieval of DigitalExperienceBundle metadata components for clarity and accuracy. --- releasenotes/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/releasenotes/README.md b/releasenotes/README.md index ede7c167b..694a053b3 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -78,7 +78,7 @@ These changes are in the Salesforce CLI release candidate. We plan to include th | visualforce generate component | template generate visualforce component | | visualforce generate page | template generate visualforce page | -* FIX: Retrieving DigitalExperienceBundle metadata components now works correctly after you update the Digital Experience site in the org. Specifically, let's say you created a page in the Digital Experience site using the in-org builder, and then retrieved it to your DX projec with the `project retrieve start` CLI command. You then you changed the mobile layout in the org, and retrieved the metadata again. Before this fix, the `mobile.json` file was incorrectly created at the top-level for the page; now it's corrected nested in `mobile/mobile.json`. (source-deploy-retrieve PR [#1680](https://github.com/forcedotcom/source-deploy-retrieve/pull/1680)) +* FIX: Retrieving DigitalExperienceBundle metadata components now works correctly after you update the Digital Experience site in the org. Specifically, let's say you created a page in the Digital Experience site using the in-org builder, and then retrieved it to your DX projec with the `project retrieve start` CLI command. You then change the mobile layout in the org, and retrieve the metadata again. Before this fix, the `mobile.json` file was incorrectly created at the top-level of the page; now it's corrected nested in `mobile/mobile.json`. (source-deploy-retrieve PR [#1680](https://github.com/forcedotcom/source-deploy-retrieve/pull/1680)) * FIX: CLI commands that don't require an org no longer run really slowly in directories in which the `target-org` config variable points to a long-expired scratch org. (GitHub Issue [#3425](https://github.com/forcedotcom/cli/issues/3425), jsforce PR [#1772](https://github.com/jsforce/jsforce/pull/1772)) From dbf3149b5797a9e77d6aaa738807c0ce92a4df6b Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Wed, 11 Feb 2026 11:18:03 -0800 Subject: [PATCH 08/11] Update README with package ZIP generation example Added an example for generating a package ZIP file using the new flag. --- releasenotes/README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/releasenotes/README.md b/releasenotes/README.md index 694a053b3..c2a96a31c 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -55,7 +55,14 @@ These changes are in the Salesforce CLI release candidate. We plan to include th (plugin-templates PR [#829](https://github.com/salesforcecli/plugin-templates/pull/829)) -* NEW: Generate a package ZIP file that you can use for debugging or to examine the package contents when you run `package version create` with the new `--generate-pkg-zip` flag. (plugin-packaging PR [#1117](https://github.com/salesforcecli/plugin-packaging/pull/1117)) +* NEW: Generate a package ZIP file that you can use for debugging or to examine the package contents when you run `package version create` with the new `--generate-pkg-zip` flag. + + This example creates a package version from the contents of the `common` directory and gives it an installation key of `password123` and generates a package ZIP file: + + ``` + $ sf package version create --path common --installation-key password123 --generate-pkg-zip --target-dev-hub my-dev-hub + ``` + (plugin-packaging PR [#1117](https://github.com/salesforcecli/plugin-packaging/pull/1117)) * CHANGE: We reorganized all the commands in [plugin-templates](https://github.com/salesforcecli/plugin-templates) under a top-level topic called `template generate`. As a result, you can now take advantage of autocomplete to list all the available templates to generate things, such as DX projects or Apex classes. From 17574d800353a7707ad7c6483b6b133a0865c285 Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Wed, 11 Feb 2026 11:56:08 -0800 Subject: [PATCH 09/11] NOTE TO JULIET: this commit contains the deleted RNs that might show up in a later release. Removed outdated AI-generated descriptions and command examples from the release notes. Updated the fix for retrieving DigitalExperienceBundle metadata components. --- releasenotes/README.md | 47 ++---------------------------------------- 1 file changed, 2 insertions(+), 45 deletions(-) diff --git a/releasenotes/README.md b/releasenotes/README.md index c2a96a31c..b8343f368 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -31,30 +31,6 @@ These changes are in the Salesforce CLI release candidate. We plan to include th ------------ -* NEW: (Developer Preview) Add AI-generated descriptions in the metadata source files in your local DX project with the new `metadata enrich` command. These enriched descriptions succinctly outline the metadata component’s purpose and capabilities, which in turn provide context when vibe coding with an AI tool, such as Agentforce Vibes. - - Currently, this command supports enriching only Lightning Web Components, represented by the LightningComponentBundle metadata type. Even though the command updates only local files in your DX project, you're still required to authorize and specify an org, which is how the command accesses a large language model (LLM). Your org must be eligible for metadata enrichment; contact your Salesforce admin. - - This example shows how to enrich the local metadata files corresonding to the `HelloWorld` LightningComponentBundle component; it uses the org with alias `my-org`: - - ``` - sf metadata enrich --metadata LightningComponentBundle:HelloWorld --target-org my-org - ``` - - This command lives in the new [plugin-metadata-enrichment](https://github.com/salesforcecli/plugin-metadata-enrichment) plugin. - -* NEW: Generate an Experience Cloud site in your DX project with the new `template generate digital-experience site` command. After you pass the command the name of a template (currently only `BuildYourOwnLWR`), the new site name, and an URL path prefix, all the required metadata files are created locally. The metadata files correspond to metadata components such as DigitalExperienceConfig, DigitalExperienceBundle, Network, and CustomSite. - - The `BuildYourOwnLWR` template creates suepr fast digital experiences, such as websites, microsites, and portals, using the Lightning Web Components programming model. Powered by Lightning Web Runtime (LWR), this customizable template delivers unparalleled site performance. For additional details, see this Salesforce Help topic: https://help.salesforce.com/s/articleView?id=experience.rss_build_your_own_lwr.htm. - - Here's an example that generates the metadata files in the `force-app/main/default` directory: - - ```bash - sf template generate digital-experience site --template BuildYourOwnLWR --name mysite --url-path-prefix mysite --output-dir force-app/main/default - ``` - - (plugin-templates PR [#829](https://github.com/salesforcecli/plugin-templates/pull/829)) - * NEW: Generate a package ZIP file that you can use for debugging or to examine the package contents when you run `package version create` with the new `--generate-pkg-zip` flag. This example creates a package version from the contents of the `common` directory and gives it an installation key of `password123` and generates a package ZIP file: @@ -64,28 +40,9 @@ These changes are in the Salesforce CLI release candidate. We plan to include th ``` (plugin-packaging PR [#1117](https://github.com/salesforcecli/plugin-packaging/pull/1117)) -* CHANGE: We reorganized all the commands in [plugin-templates](https://github.com/salesforcecli/plugin-templates) under a top-level topic called `template generate`. As a result, you can now take advantage of autocomplete to list all the available templates to generate things, such as DX projects or Apex classes. - - But don't worry, we also added aliases to the moved commands, so that the old command names will still work. But they display a deprecation warning that the command name has changed. - - Here are all the affected commands. (plugin-templates PR [#840](https://github.com/salesforcecli/plugin-templates/pull/840), - - | Old command | New command | - | ----------- | ----------- | - | apex generate class | template generate apex class | - | apex generate trigger | template generate apex trigger | - | analytics generate template | template generate analytics template | - | lightning generate app | template generate lightning app | - | lightning generate component | template generate lightning component | - | lightning generate event | template generate lightning event | - | lightning generate interface | template generate lightning interface | - | lightning generate test | template generate lightning test | - | project generate | template generate project | - | static-resource generate | template generate static-resource | - | visualforce generate component | template generate visualforce component | - | visualforce generate page | template generate visualforce page | +* FIX: Retrieving DigitalExperienceBundle metadata components now works correctly after you update the Digital Experience site in the org. -* FIX: Retrieving DigitalExperienceBundle metadata components now works correctly after you update the Digital Experience site in the org. Specifically, let's say you created a page in the Digital Experience site using the in-org builder, and then retrieved it to your DX projec with the `project retrieve start` CLI command. You then change the mobile layout in the org, and retrieve the metadata again. Before this fix, the `mobile.json` file was incorrectly created at the top-level of the page; now it's corrected nested in `mobile/mobile.json`. (source-deploy-retrieve PR [#1680](https://github.com/forcedotcom/source-deploy-retrieve/pull/1680)) + Specifically, let's say you created a page in the Digital Experience site using the in-org builder, and then retrieved it to your DX projec with the `project retrieve start` CLI command. You then change the mobile layout in the org, and retrieve the metadata again. Before this fix, the `mobile.json` file was incorrectly created at the top-level of the page; now it's corrected nested in `mobile/mobile.json`. (source-deploy-retrieve PR [#1680](https://github.com/forcedotcom/source-deploy-retrieve/pull/1680)) * FIX: CLI commands that don't require an org no longer run really slowly in directories in which the `target-org` config variable points to a long-expired scratch org. (GitHub Issue [#3425](https://github.com/forcedotcom/cli/issues/3425), jsforce PR [#1772](https://github.com/jsforce/jsforce/pull/1772)) From 4a839122cb0adc181bd326999c50e4e2101ee219 Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Wed, 11 Feb 2026 11:58:19 -0800 Subject: [PATCH 10/11] Change version number in release notes Updated version number from 2.123.6 to 2.123.1 in release notes. --- releasenotes/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/releasenotes/README.md b/releasenotes/README.md index b8343f368..aec569ae3 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -25,7 +25,7 @@ Additional documentation: * [Salesforce CLI Plugin Developer Guide](https://github.com/salesforcecli/cli/wiki/Quick-Introduction-to-Developing-sf-Plugins) * [Salesforce CLI Setup Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm) -## 2.123.6 (Feb 18, 2026) [stable-rc] +## 2.123.1 (Feb 18, 2026) [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. From 382e454774dea2472ea21290c03efea07f0f5989 Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Wed, 11 Feb 2026 12:50:39 -0800 Subject: [PATCH 11/11] Apply suggestion from @iowillhoit Co-authored-by: Willhoit --- releasenotes/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/releasenotes/README.md b/releasenotes/README.md index aec569ae3..462a64cb6 100644 --- a/releasenotes/README.md +++ b/releasenotes/README.md @@ -42,7 +42,7 @@ These changes are in the Salesforce CLI release candidate. We plan to include th * FIX: Retrieving DigitalExperienceBundle metadata components now works correctly after you update the Digital Experience site in the org. - Specifically, let's say you created a page in the Digital Experience site using the in-org builder, and then retrieved it to your DX projec with the `project retrieve start` CLI command. You then change the mobile layout in the org, and retrieve the metadata again. Before this fix, the `mobile.json` file was incorrectly created at the top-level of the page; now it's corrected nested in `mobile/mobile.json`. (source-deploy-retrieve PR [#1680](https://github.com/forcedotcom/source-deploy-retrieve/pull/1680)) + Specifically, let's say you created a page in the Digital Experience site using the in-org builder, and then retrieved it to your DX project with the `project retrieve start` CLI command. You then change the mobile layout in the org, and retrieve the metadata again. Before this fix, the `mobile.json` file was incorrectly created at the top-level of the page; now it's correctly nested in `mobile/mobile.json`. (source-deploy-retrieve PR [#1680](https://github.com/forcedotcom/source-deploy-retrieve/pull/1680)) * FIX: CLI commands that don't require an org no longer run really slowly in directories in which the `target-org` config variable points to a long-expired scratch org. (GitHub Issue [#3425](https://github.com/forcedotcom/cli/issues/3425), jsforce PR [#1772](https://github.com/jsforce/jsforce/pull/1772))