Skip to content

Next Release: changelog and version packages#490

Merged
clavery merged 2 commits into
mainfrom
changeset-release/main
Jun 11, 2026
Merged

Next Release: changelog and version packages#490
clavery merged 2 commits into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 10, 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-cli@1.15.0

Minor Changes

  • 19f059e - Add storefront-next-figma as a skill set for b2c setup skills. You can now install the Figma design-kit skills with b2c setup skills storefront-next-figma (or select it interactively) for any supported IDE. These skills require the Figma MCP server to be configured in your AI tool. (Thanks @clavery!)

Patch Changes

  • Updated dependencies [19f059e]:
    • @salesforce/b2c-tooling-sdk@1.13.0

@salesforce/b2c-tooling-sdk@1.13.0

Minor Changes

  • 19f059e - Add storefront-next-figma as a skill set for b2c setup skills. You can now install the Figma design-kit skills with b2c setup skills storefront-next-figma (or select it interactively) for any supported IDE. These skills require the Figma MCP server to be configured in your AI tool. (Thanks @clavery!)

@salesforce/b2c-dx-mcp@1.2.1

Patch Changes

  • Updated dependencies [19f059e]:
    • @salesforce/b2c-tooling-sdk@1.13.0

b2c-vs-extension@0.9.1

Patch Changes

  • Updated dependencies [19f059e]:
    • @salesforce/b2c-tooling-sdk@1.13.0

@salesforce/b2c-agent-plugins@1.4.0

Minor Changes

  • #489 0b19efe - Add Storefront Next design-system skills and a new storefront-next-figma plugin. (Thanks @pav-ui!)

    • New sfnext-create-vertical skill (storefront-next): create a brand theme / storefront variant through the brand token layer, with typography, dark-mode contrast checks, fixture-based local development, and the extension-vs-base decision.
    • New sfnext-create-component skill (storefront-next): design-system component authoring — layer model, extend-before-create gate, CVA variants bound to semantic tokens, data-slot, accessibility, and Storybook coverage (complements sfnext-components).
    • Enhanced sfnext-extensions skill with a base-audit decision gate (deciding whether to extend at all vs a token/variant override or a base slot) plus a BASE-AUDIT.md reference.
    • New storefront-next-figma plugin with the sfnext-create-figma-kit skill: duplicate the Figma kit for a vertical, sync Brand variables from brand.css, edit components at the correct layer, and publish Code Connect. Requires the Figma MCP server.

    Together these add the design-system / theming / Figma layer that the existing storefront-next plugin did not cover.

Patch Changes

  • 0c9eeab - Release packaging now reads the list of agent plugins from skills/plugins.json. To publish a new plugin, add its skills/<name>/ directory and list its name in that manifest — no changes to the publish workflow are required. (Thanks @clavery!)

  • aa48c8e - Fix the Business Manager extensions skill (b2c-business-manager-extensions) to match the authoritative bmext.xsd schema. The previous guidance used the wrong namespace and element shapes (resource-key name/icon attributes, xp-ref, a bm_extensions.properties bundle) that would not load on a real instance. The skill now documents the bmmodules/2007-12-11 schema with inline localized name/description elements, correct dialogaction/formextension structures, the NoPermissionCheck idiom for permission-free endpoints, ascending position ordering, and the core BM menu-id table for attaching to existing menus. All XML examples validate against the schema. (Thanks @clavery!)

  • #493 e803346 - Skills now consistently document that the CLI auto-discovers configuration (instance, credentials, tenantId, etc.) from dw.json, SFCC_* env vars, ~/.mobify, and package.json — flags like --server, --client-id, and --client-secret are usually unnecessary. Each instance-touching skill points agents at b2c setup inspect for resolved values and sources, and back to b2c-config for setup troubleshooting. (Thanks @clavery!)

    The b2c-config skill has been broadened to be the fallback whenever CLI setup or authentication is unclear, with general configuration guidance (including the fact that dw.json keys accept both camelCase and kebab-case) and a richer troubleshooting section.

    The b2c-custom-api-development skill now describes Custom API cartridge-path lookup correctly: storefront siteId resolves through that site's cartridge path, while siteId=Sites-Site (the system-defined BM/organization site identifier) and an omitted siteId resolve through the Business Manager cartridge path. The skill shows how to manage paths with b2c sites cartridges and clarifies when b2c code deploy --reload is required (registration, contract, or cartridge-path changes) versus when a plain redeploy suffices (implementation-only edits to an already-registered endpoint).

@salesforce/b2c-dx-docs@0.3.6

Patch Changes

  • #492 5af7cae - Removed pilot note for Storefront Next (Thanks @knhage!)

  • 19f059e - Document the new storefront-next-figma plugin in the Agent Skills guide, the install snippets (homepage, setup), and the Figma tools setup page. The plugin requires the Figma MCP server and can be installed from the plugin marketplace or with b2c setup skills storefront-next-figma. (Thanks @clavery!)

@github-actions github-actions Bot requested a review from a team June 10, 2026 01:25
@github-actions github-actions Bot requested a review from clavery as a code owner June 10, 2026 01:25
@github-actions github-actions Bot added the release Automated release PR label Jun 10, 2026
@clavery clavery force-pushed the changeset-release/main branch 4 times, most recently from 111d7bb to ab90b43 Compare June 11, 2026 15:20
@clavery clavery force-pushed the changeset-release/main branch from 2722ae8 to fbeed10 Compare June 11, 2026 16:02
@clavery clavery merged commit 9c8c448 into main Jun 11, 2026
7 checks passed
@clavery clavery deleted the changeset-release/main branch June 11, 2026 16:08
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.

1 participant