Next Release: changelog and version packages

[github-actions]

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@1.18.0

Minor Changes

• #546 85e6ca1 - Add B2C Commerce Developer Center guides and tooling docs to b2c docs (CLI), the docs_* MCP tools, and the SDK docs module. Documentation search now spans Script API reference, standard job steps, Developer Center guides (Commerce API, PWA Kit, SFRA, Storefront Next, B2C Commerce), and this tooling's own guides, with content-aware ranking and workspace-aware results tuned to the detected project type. (Thanks @clavery!)

Patch Changes

• #550 04b02f3 - Clarified SFCC_SHORTCODE vs SFCC_SHORT_CODE env var usage (Thanks @patricksullivansf!)

• #525 3d0c4aa - Improve "configuration required" errors and error telemetry: (Thanks @clavery!)

  • When a command needs instance/auth configuration but no source is found at all (no flags, environment variables, or dw.json), the error now points to the configuration guide (https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/configuration.html) so first-time users know where to start. When a config source is present, the existing message (which lists the specific flag/env var to set) is unchanged.
  • Command-error telemetry now tags each error with a category (validation, guardrail, or runtime) so expected user/config errors and safety-guard blocks can be separated from genuine runtime failures when measuring reliability.
  • All telemetry events now include an isCI flag indicating whether they originated from a CI/automation environment, so automation traffic can be distinguished from interactive developer usage.

• #546 85e6ca1 - Documentation entries now expose both a human-facing url (the rendered .html page, for citing/opening in a browser) and a machine-readable sourceUrl (the raw .md). Content is always sourced from .md, and Script API reference entries gain durable developer.salesforce.com permalinks (previously only guides had URLs). Surface them in the CLI with --columns url,sourceUrl (or -x) and in the MCP docs_search verbose output. (Thanks @clavery!)

• #551 9418f08 - Fix OAuth client authentication failing for client secrets containing + (or other reserved characters). Per RFC 6749 §2.3.1, the client ID and secret are now form-url-encoded before being Base64-encoded into the HTTP Basic Authorization header, matching how they are already encoded when sent in the request body. Previously a raw + in a secret was decoded to a space by Account Manager, causing invalid_client errors on Basic auth even though the same credential worked via the request body. Affects the client-credentials/password grants (b2c auth client, token renewal) and SLAS private-client flows. (Thanks @j-256!)

• Updated dependencies [04b02f3, 3d0c4aa, 85e6ca1, 7055134, 85e6ca1, 9418f08, 85e6ca1, 31ec679, b62b00b, 31324e1, cab53af]:

  • @salesforce/b2c-tooling-sdk@1.18.0

@salesforce/b2c-dx-mcp@1.5.0

Minor Changes

• #546 85e6ca1 - Add B2C Commerce Developer Center guides and tooling docs to b2c docs (CLI), the docs_* MCP tools, and the SDK docs module. Documentation search now spans Script API reference, standard job steps, Developer Center guides (Commerce API, PWA Kit, SFRA, Storefront Next, B2C Commerce), and this tooling's own guides, with content-aware ranking and workspace-aware results tuned to the detected project type. (Thanks @clavery!)

Patch Changes

• #545 ed1e214 - Stop MCP debug tools from routinely suggesting the session cookie (dwsid). The cookie is only needed in the rare multi-app-server production instance group case where a breakpoint is never hit — it is now surfaced as a troubleshooting hint on breakpoint timeout instead of in the debug_start_session/debug_list_sessions descriptions. Also clarifies that the debugger needs standard Basic auth (account password or a WebDAV File Access and UX Studio access key) with no separate Business Manager enablement step. (Thanks @clavery!)

• #546 85e6ca1 - Documentation entries now expose both a human-facing url (the rendered .html page, for citing/opening in a browser) and a machine-readable sourceUrl (the raw .md). Content is always sourced from .md, and Script API reference entries gain durable developer.salesforce.com permalinks (previously only guides had URLs). Surface them in the CLI with --columns url,sourceUrl (or -x) and in the MCP docs_search verbose output. (Thanks @clavery!)

• #525 3d0c4aa - Telemetry for MCP tool failures and VS Code extension activation failures now records the underlying error message (and cause, when present), instead of an empty value. Previously these failure events carried no error detail, which made it impossible to diagnose why a tool call or activation failed. No new data beyond the error text is collected, matching what the CLI already reports for command errors. (Thanks @clavery!)

• Updated dependencies [04b02f3, 3d0c4aa, 85e6ca1, 7055134, 85e6ca1, 9418f08, 85e6ca1, 31ec679, b62b00b, 31324e1, cab53af]:

  • @salesforce/b2c-tooling-sdk@1.18.0

@salesforce/b2c-tooling-sdk@1.18.0

Minor Changes

• #546 85e6ca1 - Add B2C Commerce Developer Center guides and tooling docs to b2c docs (CLI), the docs_* MCP tools, and the SDK docs module. Documentation search now spans Script API reference, standard job steps, Developer Center guides (Commerce API, PWA Kit, SFRA, Storefront Next, B2C Commerce), and this tooling's own guides, with content-aware ranking and workspace-aware results tuned to the detected project type. (Thanks @clavery!)

• #542 b62b00b - Add optional preview property to the page-type JSON Schema to mirror ECOM W-23233931. (Thanks @favour-onukogu!)

Patch Changes

• #550 04b02f3 - Clarified SFCC_SHORTCODE vs SFCC_SHORT_CODE env var usage (Thanks @patricksullivansf!)

• #525 3d0c4aa - Improve "configuration required" errors and error telemetry: (Thanks @clavery!)

  • When a command needs instance/auth configuration but no source is found at all (no flags, environment variables, or dw.json), the error now points to the configuration guide (https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/configuration.html) so first-time users know where to start. When a config source is present, the existing message (which lists the specific flag/env var to set) is unchanged.
  • Command-error telemetry now tags each error with a category (validation, guardrail, or runtime) so expected user/config errors and safety-guard blocks can be separated from genuine runtime failures when measuring reliability.
  • All telemetry events now include an isCI flag indicating whether they originated from a CI/automation environment, so automation traffic can be distinguished from interactive developer usage.

• #554 7055134 - Bound the online documentation fetch (Developer Center guides read via docs_read) with a 10s timeout. Previously a stalled or unreachable connection would hang the read indefinitely; it now falls back to the indexed offline summary once the timeout elapses. (Thanks @clavery!)

• #546 85e6ca1 - Documentation entries now expose both a human-facing url (the rendered .html page, for citing/opening in a browser) and a machine-readable sourceUrl (the raw .md). Content is always sourced from .md, and Script API reference entries gain durable developer.salesforce.com permalinks (previously only guides had URLs). Surface them in the CLI with --columns url,sourceUrl (or -x) and in the MCP docs_search verbose output. (Thanks @clavery!)

• #551 9418f08 - Fix OAuth client authentication failing for client secrets containing + (or other reserved characters). Per RFC 6749 §2.3.1, the client ID and secret are now form-url-encoded before being Base64-encoded into the HTTP Basic Authorization header, matching how they are already encoded when sent in the request body. Previously a raw + in a secret was decoded to a space by Account Manager, causing invalid_client errors on Basic auth even though the same credential worked via the request body. Affects the client-credentials/password grants (b2c auth client, token renewal) and SLAS private-client flows. (Thanks @j-256!)

• #546 85e6ca1 - Fix Storefront Next workspace detection misclassifying PWA Kit projects. A PWA Kit app that depends on @salesforce/storefront-next-runtime (now common) was incorrectly detected as Storefront Next as well. Detection now keys on the @salesforce/storefront-next-dev toolchain dependency, and a positive PWA Kit signal rules out Storefront Next. (Thanks @clavery!)

• #553 31ec679 - Reworked the MCP Server documentation to be leaner and human-focused: trimmed internal implementation prose from the tool reference pages, reorganized the nav around toolsets and logical tool groups (combined the two log pages and the two SCAPI custom-API pages, with client-side redirects from the old URLs), corrected the project-type auto-detection table, and removed agent-directed prompting guidance. Renamed the homepage/header "Agent Skills" entry to "Agent Plugins" and grouped the MCP plugin with the core plugins in the install instructions. The b2c-docs skill now notes that the MCP docs_* tools offer the same coverage as the CLI. (Thanks @clavery!)

  The tooling documentation corpus (the CLI/MCP/SDK guides available via docs search/read) no longer bundles a copy of each page's markdown in the SDK — like the Developer Center guides, its content is now fetched online from the docs site at read time (with an offline fallback to the indexed summary). This shrinks the package and stops doc edits from duplicating content into the SDK.

• #543 31324e1 - Refresh bundled Script API docs, XSD schemas, Page Designer content schemas, and standard job-step data to platform version DWAPP 26.7. The content validate command now matches the current platform rules for Page Designer component types — component_id accepts the full platform character set and is only valid on embedded components (embedded: true). (Thanks @clavery!)

• #538 cab53af - Fix b2c slas token registered-customer login failing against a private SLAS client with HTTP 400 code_verifier is required. The registered login flow is always PKCE-protected, so the token exchange now always sends the code_verifier with the authorization_code_pkce grant — and, for private clients, additionally authenticates with the client secret via HTTP Basic. Registered login now works on both public and private clients; guest and client_credentials flows are unchanged. (Thanks @clavery!)

b2c-vs-extension@0.10.2

Patch Changes

• #517 6882d5d - Improve the B2C Logs view when tailing. Log entries are now color-coded by level (error, warn, info, debug) with a built-in level filter, each entry is tagged with its source log prefix (e.g. [error], [customerror]), and multi-line stack traces are indented so each entry reads as a single block. Uses the same "B2C Logs" output channel — no new panel or command. (Thanks @charithaT07!)

• #525 3d0c4aa - Telemetry for MCP tool failures and VS Code extension activation failures now records the underlying error message (and cause, when present), instead of an empty value. Previously these failure events carried no error detail, which made it impossible to diagnose why a tool call or activation failed. No new data beyond the error text is collected, matching what the CLI already reports for command errors. (Thanks @clavery!)

• Updated dependencies [04b02f3, 3d0c4aa, 85e6ca1, 7055134, 85e6ca1, 9418f08, 85e6ca1, 31ec679, b62b00b, 31324e1, cab53af]:

  • @salesforce/b2c-tooling-sdk@1.18.0

@salesforce/b2c-dx-docs@0.3.10

Patch Changes

• #545 ed1e214 - Stop MCP debug tools from routinely suggesting the session cookie (dwsid). The cookie is only needed in the rare multi-app-server production instance group case where a breakpoint is never hit — it is now surfaced as a troubleshooting hint on breakpoint timeout instead of in the debug_start_session/debug_list_sessions descriptions. Also clarifies that the debugger needs standard Basic auth (account password or a WebDAV File Access and UX Studio access key) with no separate Business Manager enablement step. (Thanks @clavery!)

• #553 31ec679 - Reworked the MCP Server documentation to be leaner and human-focused: trimmed internal implementation prose from the tool reference pages, reorganized the nav around toolsets and logical tool groups (combined the two log pages and the two SCAPI custom-API pages, with client-side redirects from the old URLs), corrected the project-type auto-detection table, and removed agent-directed prompting guidance. Renamed the homepage/header "Agent Skills" entry to "Agent Plugins" and grouped the MCP plugin with the core plugins in the install instructions. The b2c-docs skill now notes that the MCP docs_* tools offer the same coverage as the CLI. (Thanks @clavery!)

  The tooling documentation corpus (the CLI/MCP/SDK guides available via docs search/read) no longer bundles a copy of each page's markdown in the SDK — like the Developer Center guides, its content is now fetched online from the docs site at read time (with an offline fallback to the indexed summary). This shrinks the package and stops doc edits from duplicating content into the SDK.

@salesforce/b2c-agent-plugins@1.4.5

Patch Changes

• #545 ed1e214 - Stop MCP debug tools from routinely suggesting the session cookie (dwsid). The cookie is only needed in the rare multi-app-server production instance group case where a breakpoint is never hit — it is now surfaced as a troubleshooting hint on breakpoint timeout instead of in the debug_start_session/debug_list_sessions descriptions. Also clarifies that the debugger needs standard Basic auth (account password or a WebDAV File Access and UX Studio access key) with no separate Business Manager enablement step. (Thanks @clavery!)

• #546 85e6ca1 - Add B2C Commerce Developer Center guides and tooling docs to b2c docs (CLI), the docs_* MCP tools, and the SDK docs module. Documentation search now spans Script API reference, standard job steps, Developer Center guides (Commerce API, PWA Kit, SFRA, Storefront Next, B2C Commerce), and this tooling's own guides, with content-aware ranking and workspace-aware results tuned to the detected project type. (Thanks @clavery!)

• #553 31ec679 - Reworked the MCP Server documentation to be leaner and human-focused: trimmed internal implementation prose from the tool reference pages, reorganized the nav around toolsets and logical tool groups (combined the two log pages and the two SCAPI custom-API pages, with client-side redirects from the old URLs), corrected the project-type auto-detection table, and removed agent-directed prompting guidance. Renamed the homepage/header "Agent Skills" entry to "Agent Plugins" and grouped the MCP plugin with the core plugins in the install instructions. The b2c-docs skill now notes that the MCP docs_* tools offer the same coverage as the CLI. (Thanks @clavery!)

  The tooling documentation corpus (the CLI/MCP/SDK guides available via docs search/read) no longer bundles a copy of each page's markdown in the SDK — like the Developer Center guides, its content is now fetched online from the docs site at read time (with an offline fallback to the indexed summary). This shrinks the package and stops doc edits from duplicating content into the SDK.