Repository navigation
Next Release: changelog and version packages - #728
Merged
Merged
Conversation
github-actions
Bot
requested review from
clavery,
patricksullivansf,
wei-liu-sf and
yhsieh1
as code owners
October 1, 2026 15:01
clavery
force-pushed
the
changeset-release/main
branch
8 times, most recently
from
October 4, 2026 16:41
b66d9bb to
38402bd
Compare
Contributor
Author
📘 Docs preview🧹 The preview for this PR has been removed (PR closed). |
clavery
force-pushed
the
changeset-release/main
branch
from
October 5, 2026 13:41
090a49b to
f530cc8
Compare
clavery
force-pushed
the
changeset-release/main
branch
from
October 5, 2026 14:01
e0428f7 to
e5fd74b
Compare
clavery
approved these changes
Oct 5, 2026
vvemireddy-sf
added a commit
that referenced
this pull request
Oct 8, 2026
…onflicts (W-24461621) main reverted the SCAPI redirect + access-control work (#735) that this branch independently re-landed (#736). Resolution keeps the feature branch's re-landed versions for every file the revert touched (commands, SDK operations, specs, generated client, tests, docs, skills) — main contributed no other change to those files. The two re-land changesets (mrt-access-control-scapi, mrt-redirect-scapi) are restored; changesets consumed by main's release (#728) stay deleted. data/tooling/index.json was regenerated from the merged tree to retain main's entries alongside the re-landed MRT content. Verified: both packages typecheck clean; 388 SDK + 140 CLI MRT tests pass; lint clean (0 errors).
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@salesforce/b2c-cli@2.4.0
Minor Changes
#715
285bd55- Detect AI coding agents (Claude Code, Cursor, Codex, Gemini CLI, GitHub Copilot, OpenCode, and others). Under an agent,b2c --helpadds guidance for finding commands and docs, and interactive confirmations fail fast with a hint to pass--force/--yesinstead of waiting for input. The same fail-fast behavior applies whenever no interactive terminal is available, so confirmations can no longer be answered by piping input (use--force/--yes). SetSFCC_AGENT=0to opt out of detection, orSFCC_AGENT=1to opt in. (Thanks @clavery!)#715
285bd55- Addb2c commands search <query>to find the CLI command for a task by keyword (for exampleb2c commands search "reset sandbox" --json). It complementsb2c docs search, which searches documentation. The SDK exportsCommandSearchIndexfrom@salesforce/b2c-tooling-sdk/cli. (Thanks @clavery!)#715
285bd55- Addb2c docs skillto list, search, and read the agent skills bundled with the CLI, no plugin install required. Pass a skill, topic, or command (e.g.b2c docs skill code deploy); topic and command help now point to the covering skill. (Thanks @clavery!)#737
78df45a- Added--dotenv-file/SFCC_DOTENV_FILEto use another env file (such as.env.staging) instead of.env. An empty--dotenv-file ""or--config ""now means no env file or nodw.json. With--project-directory, the.envis now read from that directory instead of the current one. (Thanks @clavery!)#737
78df45a- Fixed an explicit--config/SFCC_CONFIGpath (or MCPconfigPath) also pulling in instances from the global defaultdw.json; the explicit file is now used on its own, and a missing file is reported. If you relied on instances from the global file, remove the explicit path or add those instances to the explicit file. (Thanks @clavery!)#734
bea5bdc- The default--mrt-backendis nowlegacy(the MRT Cloud API) instead ofauto. MRT commands no longer auto-detect and prefer the SCAPI backend unless you opt in. To restore the previous behavior — prefer SCAPI when short code, tenant ID, and client-credentials/JWT Bearer auth are configured, otherwise fall back to legacy — pass--mrt-backend auto(or setMRT_BACKEND=auto/mrtBackendindw.json). Use--mrt-backend scapito require SCAPI with no fallback. (Thanks @kieran-sf!)Patch Changes
#731
f692182- Documentation search now includes the B2C Commerce Solutions guides (bot management, caching strategies, flash-sale traffic, and industry solutions) in a newcommerce-solutionscategory. (Thanks @clavery!)#737
78df45a- Storefront Next variables (PUBLIC__app__*,COMMERCE_API_SLAS_SECRET) now only fill settings missing from the selecteddw.jsoninstance, so-i <instance>keeps that instance's tenant, short code, site, and SLAS client. A higher-priority source (such as an env fileSFCC_SERVERor a config plugin) with a different hostname now skips lower-priority sources instead of mixing settings from both. SDK users reading Storefront Next variables throughEnvSourceshould addStorefrontNextEnvSourceafterdw.json. (Thanks @clavery!)Updated dependencies [
285bd55,285bd55,285bd55,f692182,285bd55,78df45a,285bd55,78df45a,f692182,5220490,bea5bdc,78df45a,9cca45e,78df45a]:@salesforce/b2c-dx-mcp@3.3.0
Minor Changes
#737
78df45a- Added--dotenv-file/SFCC_DOTENV_FILEto use another env file (such as.env.staging) instead of.env. An empty--dotenv-file ""or--config ""now means no env file or nodw.json. With--project-directory, the.envis now read from that directory instead of the current one. (Thanks @clavery!)#737
78df45a- Fixed an explicit--config/SFCC_CONFIGpath (or MCPconfigPath) also pulling in instances from the global defaultdw.json; the explicit file is now used on its own, and a missing file is reported. If you relied on instances from the global file, remove the explicit path or add those instances to the explicit file. (Thanks @clavery!)#733
5220490- Add--scapi-schemas(SFCC_SCAPI_SCHEMAS) so SCAPI code mode can use local OpenAPI contracts for beta and pre-release APIs. A local contract replaces the bundled or live contract for the same API, or adds a new one. (Thanks @clavery!)#731
f692182- Assistants that support the MCP Skills extension can now list and load the server's skills directly. MCP skills are renamed with ab2c-mcp-prefix (for exampleskill://mcp/b2c-mcp-scapi/SKILL.md), and the server skill now opens with an index of which skill covers each task. (Thanks @clavery!)Patch Changes
#731
f692182- Documentation search now includes the B2C Commerce Solutions guides (bot management, caching strategies, flash-sale traffic, and industry solutions) in a newcommerce-solutionscategory. (Thanks @clavery!)#730
9cca45e- Agents asking what's needed before a first cartridge deploy are now pointed to the configuration and authentication guidance, instead of answering from general knowledge. (Thanks @clavery!)#730
9cca45e- Agents now read the SCAPI and CIP skills before callingscapi_search,scapi_executeorcip_query, instead of being rejected and retrying.skillReadis now a required argument, and the SCAPI tool descriptions are shorter, with code-mode details moved into the SCAPI skill. (Thanks @clavery!)Updated dependencies [
285bd55,285bd55,78df45a,86d42bc,285bd55,f692182,285bd55,78df45a,285bd55,78df45a,f692182,5220490,bea5bdc,78df45a,9cca45e,f692182,78df45a,1c73738]:@salesforce/b2c-tooling-sdk@2.4.0
Minor Changes
#715
285bd55- Detect AI coding agents (Claude Code, Cursor, Codex, Gemini CLI, GitHub Copilot, OpenCode, and others). Under an agent,b2c --helpadds guidance for finding commands and docs, and interactive confirmations fail fast with a hint to pass--force/--yesinstead of waiting for input. The same fail-fast behavior applies whenever no interactive terminal is available, so confirmations can no longer be answered by piping input (use--force/--yes). SetSFCC_AGENT=0to opt out of detection, orSFCC_AGENT=1to opt in. (Thanks @clavery!)#715
285bd55- Anonymous usage telemetry and the HTTP User-Agent now identify the detected AI agent, so agent-driven usage can be measured. Agent session IDs are never sent; only a one-way hash groups commands from the same session. (Thanks @clavery!)#715
285bd55- Addb2c commands search <query>to find the CLI command for a task by keyword (for exampleb2c commands search "reset sandbox" --json). It complementsb2c docs search, which searches documentation. The SDK exportsCommandSearchIndexfrom@salesforce/b2c-tooling-sdk/cli. (Thanks @clavery!)#731
f692182- Documentation search now includes the B2C Commerce Solutions guides (bot management, caching strategies, flash-sale traffic, and industry solutions) in a newcommerce-solutionscategory. (Thanks @clavery!)#715
285bd55- Addb2c docs skillto list, search, and read the agent skills bundled with the CLI, no plugin install required. Pass a skill, topic, or command (e.g.b2c docs skill code deploy); topic and command help now point to the covering skill. (Thanks @clavery!)#737
78df45a- Added--dotenv-file/SFCC_DOTENV_FILEto use another env file (such as.env.staging) instead of.env. An empty--dotenv-file ""or--config ""now means no env file or nodw.json. With--project-directory, the.envis now read from that directory instead of the current one. (Thanks @clavery!)#715
285bd55- Publish a JSON Schema fordw.json, which gives editors completion, hover descriptions, and validation. The VS Code extension applies it to everydw.json. In other editors, referencehttps://salesforcecommercecloud.github.io/b2c-developer-tooling/schemas/dw.schema.jsonas"$schema". The schema also ships with the SDK as@salesforce/b2c-tooling-sdk/schemas/dw.schema.json. (Thanks @clavery!)#737
78df45a- Fixed an explicit--config/SFCC_CONFIGpath (or MCPconfigPath) also pulling in instances from the global defaultdw.json; the explicit file is now used on its own, and a missing file is reported. If you relied on instances from the global file, remove the explicit path or add those instances to the explicit file. (Thanks @clavery!)#731
f692182- The guidance catalog exposes skill metadata (verbatim frontmatter and per-file digests) through newskills()andskill(uri)methods. (Thanks @clavery!)#733
5220490- Add--scapi-schemas(SFCC_SCAPI_SCHEMAS) so SCAPI code mode can use local OpenAPI contracts for beta and pre-release APIs. A local contract replaces the bundled or live contract for the same API, or adds a new one. (Thanks @clavery!)#734
bea5bdc- The default--mrt-backendis nowlegacy(the MRT Cloud API) instead ofauto. MRT commands no longer auto-detect and prefer the SCAPI backend unless you opt in. To restore the previous behavior — prefer SCAPI when short code, tenant ID, and client-credentials/JWT Bearer auth are configured, otherwise fall back to legacy — pass--mrt-backend auto(or setMRT_BACKEND=auto/mrtBackendindw.json). Use--mrt-backend scapito require SCAPI with no fallback. (Thanks @kieran-sf!)Patch Changes
#737
78df45a- Tenant/organization IDs are now automatically derived from sandbox patterns (abcd-001.dx.commercecloud.salesforce.com→abcd_001) when not configured, with a warning when a configured tenant ID doesn't match. Conversely, a sandbox tenant ID with no hostname now derives the hostname, so a Storefront Next project targeting a sandbox works withoutSFCC_SERVER. Sandboxes configured with only a short code can now use SCAPI whenapiBackendisauto.normalizeTenantId()now only extracts tenants from sandbox hostnames and returns other dotted values unchanged. (Thanks @clavery!)#730
9cca45e- SCAPI code mode now accepts code that ends with a semicolon or a trailing line comment, instead of failing with a syntax error. (Thanks @clavery!)#737
78df45a- Storefront Next variables (PUBLIC__app__*,COMMERCE_API_SLAS_SECRET) now only fill settings missing from the selecteddw.jsoninstance, so-i <instance>keeps that instance's tenant, short code, site, and SLAS client. A higher-priority source (such as an env fileSFCC_SERVERor a config plugin) with a different hostname now skips lower-priority sources instead of mixing settings from both. SDK users reading Storefront Next variables throughEnvSourceshould addStorefrontNextEnvSourceafterdw.json. (Thanks @clavery!)b2c-vs-extension@1.4.0
Minor Changes
#715
285bd55- Publish a JSON Schema fordw.json, which gives editors completion, hover descriptions, and validation. The VS Code extension applies it to everydw.json. In other editors, referencehttps://salesforcecommercecloud.github.io/b2c-developer-tooling/schemas/dw.schema.jsonas"$schema". The schema also ships with the SDK as@salesforce/b2c-tooling-sdk/schemas/dw.schema.json. (Thanks @clavery!)#737
78df45a- The status bar now shows the instance actually in use and warns when env variables override it. The instance picker adds None, unnameddw.jsonentries, an Env File section for choosing.envor a.env.*file, and Inspect Resolved Config at the top. A workspace instance selected from a file that is no longer the global default is now dropped, and the workspace follows the default again. (Thanks @clavery!)#737
78df45a- B2C DX: Inspect Resolved Config now shows the extension's own resolved configuration, including the selected instance and env file, where each value comes from, and which values were not used and why. It no longer requires the CLI or the onboarding feature flag. (Thanks @clavery!)Patch Changes
#737
78df45a- Storefront Next variables (PUBLIC__app__*,COMMERCE_API_SLAS_SECRET) now only fill settings missing from the selecteddw.jsoninstance, so-i <instance>keeps that instance's tenant, short code, site, and SLAS client. A higher-priority source (such as an env fileSFCC_SERVERor a config plugin) with a different hostname now skips lower-priority sources instead of mixing settings from both. SDK users reading Storefront Next variables throughEnvSourceshould addStorefrontNextEnvSourceafterdw.json. (Thanks @clavery!)#737
78df45a- Code Sync no longer retries failed uploads every 5 seconds forever. Authentication failures (401/403) pause sync with a single warning until the next save or Retry, other failures back off up to 5 minutes, and failed deletes are no longer dropped. After a configuration change (such as fixing credentials in.env), changes that failed are retried with the new configuration. (Thanks @clavery!)Updated dependencies [
285bd55,285bd55,285bd55,f692182,285bd55,78df45a,285bd55,78df45a,f692182,5220490,bea5bdc,78df45a,9cca45e,78df45a]:@salesforce/b2c-agent-plugins@1.11.0
Minor Changes
1c73738- Thestorefront-nextandfigma-to-sfnext-pagedesignerskills are updated for the October 2026 Storefront Next template. Code examples, commands, and project paths are corrected, and new skills cover security, SEO, analytics and consent, accessibility, quality gates, revalidation, and commerce features (24 skills). Skills were renamed or merged:sfnext-create-vertical→sfnext-theming,sfnext-create-component→sfnext-components, andsfnext-scapi-management+sfnext-custom-apis→sfnext-scapi. (Thanks @clavery!)Patch Changes
#737
78df45a- Updated theb2c-configskill for env file selection and Storefront Next fallback precedence. (Thanks @clavery!)#739
86d42bc- Theb2c-contentskill now points tob2c-cli:b2c-configfor authentication setup instead of a skill that doesn't exist. (Thanks @clavery!)#731
f692182- Documentation search now includes the B2C Commerce Solutions guides (bot management, caching strategies, flash-sale traffic, and industry solutions) in a newcommerce-solutionscategory. (Thanks @clavery!)#715
285bd55- Addb2c docs skillto list, search, and read the agent skills bundled with the CLI, no plugin install required. Pass a skill, topic, or command (e.g.b2c docs skill code deploy); topic and command help now point to the covering skill. (Thanks @clavery!)#734
bea5bdc- The default--mrt-backendis nowlegacy(the MRT Cloud API) instead ofauto. MRT commands no longer auto-detect and prefer the SCAPI backend unless you opt in. To restore the previous behavior — prefer SCAPI when short code, tenant ID, and client-credentials/JWT Bearer auth are configured, otherwise fall back to legacy — pass--mrt-backend auto(or setMRT_BACKEND=auto/mrtBackendindw.json). Use--mrt-backend scapito require SCAPI with no fallback. (Thanks @kieran-sf!)#731
f692182- Skills now refer to each other by name instead of relative paths, so links work wherever a skill is installed. Documentation links point to Markdown pages and include theb2c docs readID for offline reading. (Thanks @clavery!)@salesforce/b2c-dx-docs@0.4.5
Patch Changes
#715
285bd55- Publish a JSON Schema fordw.json, which gives editors completion, hover descriptions, and validation. The VS Code extension applies it to everydw.json. In other editors, referencehttps://salesforcecommercecloud.github.io/b2c-developer-tooling/schemas/dw.schema.jsonas"$schema". The schema also ships with the SDK as@salesforce/b2c-tooling-sdk/schemas/dw.schema.json. (Thanks @clavery!)#738
1c73738- Thestorefront-nextandfigma-to-sfnext-pagedesignerskills are updated for the October 2026 Storefront Next template. Code examples, commands, and project paths are corrected, and new skills cover security, SEO, analytics and consent, accessibility, quality gates, revalidation, and commerce features (24 skills). Skills were renamed or merged:sfnext-create-vertical→sfnext-theming,sfnext-create-component→sfnext-components, andsfnext-scapi-management+sfnext-custom-apis→sfnext-scapi. (Thanks @clavery!)