Skip to content

Next Release: changelog and version packages#527

Open
github-actions[bot] wants to merge 2 commits into
mainfrom
changeset-release/main
Open

Next Release: changelog and version packages#527
github-actions[bot] wants to merge 2 commits into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

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-tooling-sdk@1.17.0

Minor Changes

  • #530 6cfb9bd - Document the standard (system) job steps that B2C Commerce ships for Business Manager job flows. The bundled docs corpus now includes the full catalog of standard job step type IDs (e.g. ImportCatalog, ExportCatalog, ExecutePreconfiguredDataReplicationProcess, SearchReindex) with each step's purpose, scope, and configuration parameters — sourced from the public B2C Commerce Job Step API documentation and searchable through b2c docs search/b2c docs read (and the docs_search/docs_read MCP tools) with no new commands. Read the catalog with b2c docs read job-steps or a specific step with b2c docs read <TypeID>. The job and custom-job-step skills now cover referencing an IMPEX-staged file from a prior step, chaining custom and standard steps in one flow, and choosing an in-flow system step vs. the CLI equivalent (e.g. a standard catalog import vs. b2c job import). (Thanks @clavery!)

Patch Changes

  • #530 6cfb9bd - Update the bundled Script API documentation and XSD schemas to version 26.7. (Thanks @clavery!)

@salesforce/b2c-cli@1.17.3

Patch Changes

  • Updated dependencies [6cfb9bd, 6cfb9bd]:
    • @salesforce/b2c-tooling-sdk@1.17.0

@salesforce/b2c-dx-mcp@1.4.1

Patch Changes

  • Updated dependencies [6cfb9bd, 6cfb9bd]:
    • @salesforce/b2c-tooling-sdk@1.17.0

b2c-vs-extension@0.10.1

Patch Changes

  • Updated dependencies [6cfb9bd, 6cfb9bd]:
    • @salesforce/b2c-tooling-sdk@1.17.0

@salesforce/b2c-dx-docs@0.3.9

Patch Changes

  • #533 f3d2d9e - GitHub Actions: the high-level actions (code-deploy, data-import, job-run, webdav-upload) and the root action now forward the full set of auth/config inputs to setupaccount-manager-host, short-code, tenant-id, certificate, certificate-passphrase, selfsigned, and webdav-server (where applicable). Previously these were silently dropped with an "Unexpected input(s)" warning, so a non-default Account Manager host or staging mTLS credentials had to be set via env vars or a separate setup step. Also bumped the bundled setup-node/checkout references to Node 24-capable majors to clear the Node 20 deprecation warning. (Thanks @clavery!)

  • #532 76643fa - Fix the setup GitHub Action silently corrupting any credential that contains a $ (for example an auto-generated WebDAV access key like abc$FOO123). The action wrote credentials to the job environment with an inline-interpolated echo, so bash re-expanded $WORD sequences and stripped them — the altered credential then failed downstream WebDAV auth with an unexplained 401. Credentials are now passed through the step's env block and written with GitHub's heredoc env syntax, so values containing $, quotes, backticks, $(...), =, or even newlines reach the CLI byte-for-byte. No workflow changes are required; re-run with the fixed action version. (Thanks @clavery!)

  • #530 6cfb9bd - Document the standard (system) job steps that B2C Commerce ships for Business Manager job flows. The bundled docs corpus now includes the full catalog of standard job step type IDs (e.g. ImportCatalog, ExportCatalog, ExecutePreconfiguredDataReplicationProcess, SearchReindex) with each step's purpose, scope, and configuration parameters — sourced from the public B2C Commerce Job Step API documentation and searchable through b2c docs search/b2c docs read (and the docs_search/docs_read MCP tools) with no new commands. Read the catalog with b2c docs read job-steps or a specific step with b2c docs read <TypeID>. The job and custom-job-step skills now cover referencing an IMPEX-staged file from a prior step, chaining custom and standard steps in one flow, and choosing an in-flow system step vs. the CLI equivalent (e.g. a standard catalog import vs. b2c job import). (Thanks @clavery!)

  • #526 fb9fbf9 - Trim the Script Debugger guide to remove implementation detail (internal API name, client_id, transport plumbing, roadmap note) and a duplicated interface list, keeping it focused on what users need to debug. (Thanks @clavery!)

  • b6d2879 - Clarify WebDAV authentication guidance: Basic Auth is for interactive user-based access while OAuth is for API clients and CI/CD, rather than labeling Basic Auth as generally "recommended". (Thanks @clavery!)

@salesforce/b2c-agent-plugins@1.4.4

Patch Changes

  • #524 2ecbad7 - Clarify SCAPI Admin OAuth scopes in the custom API and Account Manager skills. The custom-api-development, scapi-admin, scapi-custom, and config skills now consistently document that Admin API tokens (system and custom) require both the tenant scope SALESFORCE_COMMERCE_API:<tenant_id> and the API-specific scopes, that b2c auth token accepts multiple --auth-scope values, and that — unlike the SCAPI subcommands — b2c auth token does not auto-inject the tenant scope. Also fixes a broken admin token curl example and an invalid --scope flag reference in the testing docs. (Thanks @clavery!)

  • #528 4efd453 - Document headless order-failure essentials in the b2c agent skills. The b2c-hooks skill now explains the dw.ocapi.shop.order.afterPOST hook in depth — it runs inside a platform transaction (so wrapping OrderMgr.placeOrder/failOrder in your own Transaction.wrap rolls the change back and surfaces an opaque HTTP 400: An error occurred in ExtensionPoint…), it owns the CREATED → NEW/FAILED transition for SCAPI orders, and it must log its own decline reason — plus a canonical example that authorizes payment instruments via app.payment.processor.* Authorize hooks, fails the order on decline, and places it when fully paid. b2c-custom-job-steps gains a jobs.xml reference covering how to author and import (b2c job import) a job definition (job/flow/step structure, the type vs @type-id distinction, and the required <triggers> element). (Thanks @clavery!)

  • #530 6cfb9bd - Document the standard (system) job steps that B2C Commerce ships for Business Manager job flows. The bundled docs corpus now includes the full catalog of standard job step type IDs (e.g. ImportCatalog, ExportCatalog, ExecutePreconfiguredDataReplicationProcess, SearchReindex) with each step's purpose, scope, and configuration parameters — sourced from the public B2C Commerce Job Step API documentation and searchable through b2c docs search/b2c docs read (and the docs_search/docs_read MCP tools) with no new commands. Read the catalog with b2c docs read job-steps or a specific step with b2c docs read <TypeID>. The job and custom-job-step skills now cover referencing an IMPEX-staged file from a prior step, chaining custom and standard steps in one flow, and choosing an in-flow system step vs. the CLI equivalent (e.g. a standard catalog import vs. b2c job import). (Thanks @clavery!)

@github-actions github-actions Bot requested a review from a team June 23, 2026 18:51
@github-actions github-actions Bot requested a review from clavery as a code owner June 23, 2026 18:51
@github-actions github-actions Bot added the release Automated release PR label Jun 23, 2026
@clavery clavery force-pushed the changeset-release/main branch 2 times, most recently from b807000 to 591967d Compare June 23, 2026 23:24
@clavery clavery force-pushed the changeset-release/main branch 3 times, most recently from 474dbd3 to bb5c0c5 Compare June 29, 2026 18:52
@clavery clavery force-pushed the changeset-release/main branch from 305930c to ebdcadc Compare June 29, 2026 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release Automated release PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants