Skip to content

Agent Plugins 1.14.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 00:08
· 38 commits to main since this release
801fe30

Agent skills plugin artifacts for b2c-agent-plugins v1.14.0. Download the *-skills.zip files below.

See the Agent Skills & Plugins guide for installation and usage.

Changelog

Minor Changes

  • #835 46495bb - New b2c-setup skill guides your assistant through setting up a sandbox or realm: sample storefront datasets, search indexes, Storefront Next storefronts and project code, and replication to production, with confirmation before changes to shared instances. The MCP server features it in its skill listing. (Thanks @clavery!)

Patch Changes

  • #835 46495bb - b2c am clients create now shows the new client's details and asks for confirmation before creating it. Pass --force to skip the prompt; scripts and --json runs must add --force. New clients now default to client_secret_basic, so they work with their secret; previously Account Manager made them private_key_jwt and the secret was rejected. The b2c-am skill now walks your assistant through creating an API client when you don't have one, after you approve every detail. (Thanks @clavery!)

  • #840 4ba58fb - The b2c-cap skill now points MCP users to the bundled cap-dev authoring skills. (Thanks @clavery!)

  • #839 84cd0da - The b2c-sites skill now explains that Business Manager cartridge path updates use the SCAPI Sites API. (Thanks @clavery!)

  • #838 779ae04 - Add --default-client (or SFCC_DEFAULT_CLIENT=true) to sign in with the CLI's built-in client when another client or access key is configured, so WebDAV, code upload, logs, sandbox and Account Manager commands work with your Account Manager account without changing your config (Thanks @clavery!)

  • #835 46495bb - Job and replication skills now warn that a scheduled job trigger without weekdays never runs, and show how to end a job early when there's no input file. Realm setup guidance now covers what replication leaves for each target (job definitions, inventory, SLAS clients, site status), cartridge paths, and per-environment import sets. (Thanks @clavery!)

  • #835 46495bb - Setup and code skills, and the Realm Setup guide, now explain that staging code upload normally requires a client certificate (a Salesforce Support CA bundle on legacy realms, or a self-registered eCDN CA on Hyperforce). They also cover the feature switch that Commerce API hooks need and how to reload when an instance has only one code version. (Thanks @clavery!)