Next Release: changelog and version packages#527
Open
github-actions[bot] wants to merge 2 commits into
Open
Conversation
b807000 to
591967d
Compare
474dbd3 to
bb5c0c5
Compare
305930c to
ebdcadc
Compare
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-tooling-sdk@1.17.0
Minor Changes
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 throughb2c docs search/b2c docs read(and thedocs_search/docs_readMCP tools) with no new commands. Read the catalog withb2c docs read job-stepsor a specific step withb2c 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
6cfb9bd- Update the bundled Script API documentation and XSD schemas to version 26.7. (Thanks @clavery!)@salesforce/b2c-cli@1.17.3
Patch Changes
6cfb9bd,6cfb9bd]:@salesforce/b2c-dx-mcp@1.4.1
Patch Changes
6cfb9bd,6cfb9bd]:b2c-vs-extension@0.10.1
Patch Changes
6cfb9bd,6cfb9bd]:@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 tosetup—account-manager-host,short-code,tenant-id,certificate,certificate-passphrase,selfsigned, andwebdav-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 separatesetupstep. Also bumped the bundledsetup-node/checkoutreferences to Node 24-capable majors to clear the Node 20 deprecation warning. (Thanks @clavery!)#532
76643fa- Fix thesetupGitHub Action silently corrupting any credential that contains a$(for example an auto-generated WebDAV access key likeabc$FOO123). The action wrote credentials to the job environment with an inline-interpolatedecho, so bash re-expanded$WORDsequences and stripped them — the altered credential then failed downstream WebDAV auth with an unexplained 401. Credentials are now passed through the step'senvblock 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 throughb2c docs search/b2c docs read(and thedocs_search/docs_readMCP tools) with no new commands. Read the catalog withb2c docs read job-stepsor a specific step withb2c 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 scopeSALESFORCE_COMMERCE_API:<tenant_id>and the API-specific scopes, thatb2c auth tokenaccepts multiple--auth-scopevalues, and that — unlike the SCAPI subcommands —b2c auth tokendoes not auto-inject the tenant scope. Also fixes a broken admin token curl example and an invalid--scopeflag reference in the testing docs. (Thanks @clavery!)#528
4efd453- Document headless order-failure essentials in theb2cagent skills. Theb2c-hooksskill now explains thedw.ocapi.shop.order.afterPOSThook in depth — it runs inside a platform transaction (so wrappingOrderMgr.placeOrder/failOrderin your ownTransaction.wraprolls the change back and surfaces an opaqueHTTP 400: An error occurred in ExtensionPoint…), it owns theCREATED → NEW/FAILEDtransition for SCAPI orders, and it must log its own decline reason — plus a canonical example that authorizes payment instruments viaapp.payment.processor.*Authorize hooks, fails the order on decline, and places it when fully paid.b2c-custom-job-stepsgains ajobs.xmlreference covering how to author and import (b2c job import) a job definition (job/flow/step structure, thetypevs@type-iddistinction, 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 throughb2c docs search/b2c docs read(and thedocs_search/docs_readMCP tools) with no new commands. Read the catalog withb2c docs read job-stepsor a specific step withb2c 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!)