Skip to content

W-21192584: sf RNs Feb 11, 2026 #3498

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jshackell-sfdc wants to merge 5 commits into
base: main
Choose a base branch
from
+53 −2
Open

W-21192584: sf RNs Feb 11, 2026 #3498

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3b4cdc7
Update release notes for version 2.123.6
jshackell-sfdc Feb 5, 2026
9616181
Revise release notes for clarity and updates
jshackell-sfdc Feb 11, 2026
519734b
Document new command for generating Experience Cloud site
jshackell-sfdc Feb 11, 2026
8215112
Document new 'metadata enrich' command in README
jshackell-sfdc Feb 11, 2026
bf93e93
Fix CLI performance and add skip retrieve feature
jshackell-sfdc Feb 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 53 additions & 2 deletions releasenotes/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,12 +25,63 @@ 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: (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. (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: 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:

```bash
Expand All @@ -45,7 +96,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:

Expand Down