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

Minor Changes

• #695 d076982 - Extend the SCAPI MRT backend to mrt bundle list and the local-build push path of mrt bundle deploy. Both commands now honor --mrt-backend (auto | legacy | scapi): list fetches bundles from the SCAPI Storefront Deployments API, and deploy (without a bundle ID) uploads the local build — and optionally deploys it — over SCAPI. auto prefers SCAPI when short code, tenant ID, and client-credentials or JWT Bearer auth are configured, and falls back to legacy on safe pre-execution errors; scapi never silently falls back. The bundle format now maps to the endpoint: SCAPI always uploads the v2 format, while legacy defaults to v1. A new --v2 flag opts the legacy backend into the v2 endpoint (upload, plus a separate deploy when --environment is given). deploy also gains --root-dir, --config-path, and --match-mode to control the v2 archive layout; these apply to v2 uploads only and are ignored, with a warning, on a legacy v1 push. mrt bundle deploy --v2 performs the same v2 upload as mrt bundle upload-v2 and can build, upload, and deploy in one step. --json output stays backend-native. The SDK adds listMrtBundles, uploadBundleScapi, and pushMrtBundle operations. (Thanks @o-olaosebikan!)

Patch Changes

• #693 09e5a0a - MRT commands now reliably suppress human-readable progress and status logging when --json is set, so diagnostic text never mixes with the machine-readable output. This also fixes mrt env var push --json, which previously printed progress lines to stdout alongside the JSON result. (Thanks @kieran-sf!)

• Updated dependencies [09e5a0a, d076982]:

  • @salesforce/b2c-tooling-sdk@2.1.0

@salesforce/b2c-tooling-sdk@2.1.0

Minor Changes

• #695 d076982 - Extend the SCAPI MRT backend to mrt bundle list and the local-build push path of mrt bundle deploy. Both commands now honor --mrt-backend (auto | legacy | scapi): list fetches bundles from the SCAPI Storefront Deployments API, and deploy (without a bundle ID) uploads the local build — and optionally deploys it — over SCAPI. auto prefers SCAPI when short code, tenant ID, and client-credentials or JWT Bearer auth are configured, and falls back to legacy on safe pre-execution errors; scapi never silently falls back. The bundle format now maps to the endpoint: SCAPI always uploads the v2 format, while legacy defaults to v1. A new --v2 flag opts the legacy backend into the v2 endpoint (upload, plus a separate deploy when --environment is given). deploy also gains --root-dir, --config-path, and --match-mode to control the v2 archive layout; these apply to v2 uploads only and are ignored, with a warning, on a legacy v1 push. mrt bundle deploy --v2 performs the same v2 upload as mrt bundle upload-v2 and can build, upload, and deploy in one step. --json output stays backend-native. The SDK adds listMrtBundles, uploadBundleScapi, and pushMrtBundle operations. (Thanks @o-olaosebikan!)

Patch Changes

• #693 09e5a0a - MRT commands now reliably suppress human-readable progress and status logging when --json is set, so diagnostic text never mixes with the machine-readable output. This also fixes mrt env var push --json, which previously printed progress lines to stdout alongside the JSON result. (Thanks @kieran-sf!)

@salesforce/b2c-dx-mcp@3.0.2

Patch Changes

• Updated dependencies [09e5a0a, d076982]:
  • @salesforce/b2c-tooling-sdk@2.1.0

b2c-vs-extension@1.2.1

Patch Changes

• Updated dependencies [09e5a0a, d076982]:
  • @salesforce/b2c-tooling-sdk@2.1.0

@salesforce/b2c-dx-docs@0.4.1

Patch Changes

• eaf789a - Clarified project guidance for using MCP skills, runbooks, and documentation tools. (Thanks @clavery!)

[github-actions]

📘 Docs preview

Your documentation changes are published at:

https://d3uhw92m2zac57.cloudfront.net/pr-696/

Commit d2e58e4 · ✅ Published

_{This preview updates on every push and is removed when the PR is closed.}