@salesforce/b2c-dx-mcp 3.1.1 → 3.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/content/guidance/b2c-cli/b2c-ecdn/references/ADVANCED.md +8 -8
- package/content/guidance/index.json +1 -1
- package/node_modules/@salesforce/b2c-agent-plugins/CHANGELOG.md +6 -0
- package/node_modules/@salesforce/b2c-agent-plugins/b2c/.codex-plugin/plugin.json +1 -1
- package/node_modules/@salesforce/b2c-agent-plugins/b2c/plugin.json +1 -1
- package/node_modules/@salesforce/b2c-agent-plugins/b2c-cli/.codex-plugin/plugin.json +1 -1
- package/node_modules/@salesforce/b2c-agent-plugins/b2c-cli/plugin.json +1 -1
- package/node_modules/@salesforce/b2c-agent-plugins/b2c-cli/skills/b2c-ecdn/references/ADVANCED.md +8 -8
- package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/.codex-plugin/plugin.json +1 -1
- package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/plugin.json +1 -1
- package/node_modules/@salesforce/b2c-agent-plugins/package.json +1 -1
- package/node_modules/@salesforce/b2c-agent-plugins/storefront-next/.codex-plugin/plugin.json +1 -1
- package/node_modules/@salesforce/b2c-agent-plugins/storefront-next/plugin.json +1 -1
- package/oclif.manifest.json +1 -1
- package/package.json +2 -2
|
@@ -41,22 +41,22 @@ b2c ecdn mrt-rules delete --zone my-zone
|
|
|
41
41
|
|
|
42
42
|
## mTLS Certificates
|
|
43
43
|
|
|
44
|
-
Code upload certificates enable two-factor (mTLS) code upload to staging instances (`_stg` tenants only).
|
|
44
|
+
Code upload certificates enable two-factor (mTLS) code upload to staging instances (`_stg` tenants only). There are two kinds: CAs registered with eCDN for the tenant (typically one, but several can be active, e.g. during renewal), which only sign certificates; and client certificates (`.p12`) signed by a CA (typically one per CI pipeline or developer, any number allowed), which the CLI sends on code upload. CI pipelines are the primary use case. Use `create --generate --name <ca-label> --client-name <pipeline>` once to create + register the CA and issue the first (CI) client cert, then `issue` for each additional pipeline/developer. `setup` is a guided, interactive version of `create --generate` with defaults and an optional dw.json update. `create` with `--certificate-file`/`--private-key-file` registers a bring-your-own CA. The code upload hostname is provisioned by Salesforce and linked automatically; users don't configure it. The CA private key must be kept secret (treat like a password); the CA certificate bundle must have a maximum validity of 1 year and be renewed before expiry. On Hyperforce, use the `staging-<realm>-<customer>.demandware.net` code upload hostname (not legacy `cert.staging.*`).
|
|
45
45
|
|
|
46
|
-
For the complete workflow, security guidance, and renewal instructions, see [Deploying to Hyperforce: Code Upload
|
|
46
|
+
For the complete workflow, security guidance, and renewal instructions, see [Deploying to Hyperforce: Set Up Two-Factor Code Upload](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/hyperforce#set-up-two-factor-code-upload).
|
|
47
47
|
|
|
48
48
|
```bash
|
|
49
|
-
#
|
|
50
|
-
b2c ecdn mtls
|
|
49
|
+
# typically once per tenant: generate + register CA, issue first client cert (e.g. for CI)
|
|
50
|
+
b2c ecdn mtls create --name code-upload --generate --client-name github-actions
|
|
51
|
+
b2c ecdn mtls create --name code-upload --generate --out-dir ./certs --client-name github-actions
|
|
51
52
|
|
|
52
|
-
#
|
|
53
|
-
b2c ecdn mtls
|
|
54
|
-
b2c ecdn mtls create --name code-upload --generate --out-dir ./certs --client-name jsmith
|
|
53
|
+
# guided/interactive version of create --generate (prompts, defaults, optional dw.json update)
|
|
54
|
+
b2c ecdn mtls setup
|
|
55
55
|
|
|
56
56
|
# upload an existing CA
|
|
57
57
|
b2c ecdn mtls create --name code-upload --certificate-file ./ca.pem --private-key-file ./ca.key
|
|
58
58
|
|
|
59
|
-
# issue
|
|
59
|
+
# issue a client certificate per CI pipeline / developer (local-only, no API call)
|
|
60
60
|
b2c ecdn mtls issue --ca-cert-file ./certs/ca.pem --ca-key-file ./certs/ca.key --name jane.doe
|
|
61
61
|
b2c ecdn mtls issue --ca-cert-file ca.pem --ca-key-file ca.key --name ci --output ci.p12 --days 90
|
|
62
62
|
|
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# @salesforce/b2c-agent-plugins
|
|
2
2
|
|
|
3
|
+
## 1.10.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- [#717](https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/pull/717) [`443fa0b`](https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/commit/443fa0b9bd0abdd360077c51b692784eaa1827dd) - Clearer Hyperforce two-factor code upload guidance: a step-by-step setup that starts with CI pipelines, plus clearer `b2c ecdn mtls` prompts that separate the CA from the client certificate used for upload (Thanks [@clavery](https://github.com/clavery)!)
|
|
8
|
+
|
|
3
9
|
## 1.10.1
|
|
4
10
|
|
|
5
11
|
### Patch Changes
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
|
|
3
3
|
"name": "b2c",
|
|
4
|
-
"version": "1.10.
|
|
4
|
+
"version": "1.10.2",
|
|
5
5
|
"description": "B2C Commerce development skills including Custom API development guides.",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Salesforce"
|
package/node_modules/@salesforce/b2c-agent-plugins/b2c-cli/skills/b2c-ecdn/references/ADVANCED.md
CHANGED
|
@@ -41,22 +41,22 @@ b2c ecdn mrt-rules delete --zone my-zone
|
|
|
41
41
|
|
|
42
42
|
## mTLS Certificates
|
|
43
43
|
|
|
44
|
-
Code upload certificates enable two-factor (mTLS) code upload to staging instances (`_stg` tenants only).
|
|
44
|
+
Code upload certificates enable two-factor (mTLS) code upload to staging instances (`_stg` tenants only). There are two kinds: CAs registered with eCDN for the tenant (typically one, but several can be active, e.g. during renewal), which only sign certificates; and client certificates (`.p12`) signed by a CA (typically one per CI pipeline or developer, any number allowed), which the CLI sends on code upload. CI pipelines are the primary use case. Use `create --generate --name <ca-label> --client-name <pipeline>` once to create + register the CA and issue the first (CI) client cert, then `issue` for each additional pipeline/developer. `setup` is a guided, interactive version of `create --generate` with defaults and an optional dw.json update. `create` with `--certificate-file`/`--private-key-file` registers a bring-your-own CA. The code upload hostname is provisioned by Salesforce and linked automatically; users don't configure it. The CA private key must be kept secret (treat like a password); the CA certificate bundle must have a maximum validity of 1 year and be renewed before expiry. On Hyperforce, use the `staging-<realm>-<customer>.demandware.net` code upload hostname (not legacy `cert.staging.*`).
|
|
45
45
|
|
|
46
|
-
For the complete workflow, security guidance, and renewal instructions, see [Deploying to Hyperforce: Code Upload
|
|
46
|
+
For the complete workflow, security guidance, and renewal instructions, see [Deploying to Hyperforce: Set Up Two-Factor Code Upload](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/hyperforce#set-up-two-factor-code-upload).
|
|
47
47
|
|
|
48
48
|
```bash
|
|
49
|
-
#
|
|
50
|
-
b2c ecdn mtls
|
|
49
|
+
# typically once per tenant: generate + register CA, issue first client cert (e.g. for CI)
|
|
50
|
+
b2c ecdn mtls create --name code-upload --generate --client-name github-actions
|
|
51
|
+
b2c ecdn mtls create --name code-upload --generate --out-dir ./certs --client-name github-actions
|
|
51
52
|
|
|
52
|
-
#
|
|
53
|
-
b2c ecdn mtls
|
|
54
|
-
b2c ecdn mtls create --name code-upload --generate --out-dir ./certs --client-name jsmith
|
|
53
|
+
# guided/interactive version of create --generate (prompts, defaults, optional dw.json update)
|
|
54
|
+
b2c ecdn mtls setup
|
|
55
55
|
|
|
56
56
|
# upload an existing CA
|
|
57
57
|
b2c ecdn mtls create --name code-upload --certificate-file ./ca.pem --private-key-file ./ca.key
|
|
58
58
|
|
|
59
|
-
# issue
|
|
59
|
+
# issue a client certificate per CI pipeline / developer (local-only, no API call)
|
|
60
60
|
b2c ecdn mtls issue --ca-cert-file ./certs/ca.pem --ca-key-file ./certs/ca.key --name jane.doe
|
|
61
61
|
b2c ecdn mtls issue --ca-cert-file ca.pem --ca-key-file ca.key --name ci --output ci.p12 --days 90
|
|
62
62
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
|
|
3
3
|
"name": "b2c-ops",
|
|
4
|
-
"version": "1.10.
|
|
4
|
+
"version": "1.10.2",
|
|
5
5
|
"description": "B2C Commerce operator and administrator runbooks for job health, checkout and failed orders, and incident triage.",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Salesforce"
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
|
|
3
3
|
"name": "storefront-next",
|
|
4
|
-
"version": "1.10.
|
|
4
|
+
"version": "1.10.2",
|
|
5
5
|
"description": "Storefront Next development skills for building React 19 storefronts on Salesforce B2C Commerce.",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Salesforce"
|
package/oclif.manifest.json
CHANGED
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@salesforce/b2c-dx-mcp",
|
|
3
3
|
"description": "MCP server for B2C Commerce developer experience tools",
|
|
4
|
-
"version": "3.1.
|
|
4
|
+
"version": "3.1.2",
|
|
5
5
|
"author": "Salesforce",
|
|
6
6
|
"license": "Apache-2.0",
|
|
7
7
|
"repository": "SalesforceCommerceCloud/b2c-developer-tooling",
|
|
@@ -80,7 +80,7 @@
|
|
|
80
80
|
"ts-morph": "27.0.2",
|
|
81
81
|
"yaml": "2.9.0",
|
|
82
82
|
"zod": "4.5.4",
|
|
83
|
-
"@salesforce/b2c-agent-plugins": "1.10.
|
|
83
|
+
"@salesforce/b2c-agent-plugins": "1.10.2",
|
|
84
84
|
"@salesforce/b2c-tooling-sdk": "2.2.0"
|
|
85
85
|
},
|
|
86
86
|
"bundledDependencies": [
|