@salesforce/b2c-dx-mcp 3.5.1 → 3.5.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.
@@ -48,6 +48,7 @@ b2c job import ./archive --show-log
48
48
  b2c job import ./storefront-export.zip --wait-for-storefront
49
49
  b2c job export --site MySite --site-data campaigns_and_promotions --output ./export
50
50
  b2c job export --storefront my-storefront --output ./export
51
+ b2c job export --all --output ./full-export
51
52
  ```
52
53
 
53
54
  Import/export wait by default and transfer files over WebDAV. Jobs prefer SCAPI
@@ -27,6 +27,13 @@ import, the same approach reports execution status without `localPath`.
27
27
  The `job export` command exports data from a B2C Commerce instance as a site archive. You must specify at least one data unit to export.
28
28
 
29
29
  ```bash
30
+ # export everything (global data, sites, catalogs, libraries, static resources,
31
+ # inventory lists, price books, customer lists)
32
+ b2c job export --all --output ./full-export
33
+
34
+ # export every object of a type with the special ID "all"
35
+ b2c job export --site all --catalog all --library all
36
+
30
37
  # export global metadata
31
38
  b2c job export --global-data meta_data
32
39
 
@@ -96,17 +103,18 @@ Do not require a temporary directory and copy step for export-based migrations.
96
103
 
97
104
  #### Available Data Units
98
105
 
99
- **Top-level categories** (each takes one or more IDs via flags):
106
+ **Top-level categories** (each takes one or more IDs, or the special ID `all` for every object of that type):
100
107
 
101
- | Flag | Description |
102
- | ------------------ | ------------------------------------------------------------------------------ |
103
- | `--site` | Site IDs to export (use `--site-data` to pick specific units, defaults to all) |
104
- | `--storefront` | One composable storefront name |
105
- | `--catalog` | Catalog IDs |
106
- | `--library` | Library IDs |
107
- | `--inventory-list` | Inventory list IDs |
108
- | `--price-book` | Price book IDs |
109
- | `--global-data` | Global data units (comma-separated names from the list below) |
108
+ | Flag | Description |
109
+ | ------------------ | --------------------------------------------------------------------------------------------------- |
110
+ | `--site` | Site IDs to export (use `--site-data` to pick specific units, defaults to all) |
111
+ | `--storefront` | One composable storefront name |
112
+ | `--catalog` | Catalog IDs |
113
+ | `--library` | Library IDs |
114
+ | `--inventory-list` | Inventory list IDs |
115
+ | `--price-book` | Price book IDs |
116
+ | `--global-data` | Global data units (comma-separated names from the list below) |
117
+ | `--all` | Everything above plus static resources and customer lists; exclusive with all except `--storefront` |
110
118
 
111
119
  **Site data units** (use with `--site-data`):
112
120
 
@@ -116,6 +124,6 @@ Do not require a temporary directory and copy step for export-based migrations.
116
124
 
117
125
  `access_roles`, `all`, `csc_settings`, `csrf_whitelists`, `custom_preference_groups`, `custom_quota_settings`, `custom_types`, `event_routing`, `geolocations`, `global_custom_objects`, `job_schedules`, `job_schedules_deprecated`, `locales`, `meta_data`, `oauth_providers`, `ocapi_settings`, `page_meta_tags`, `preferences`, `price_adjustment_limits`, `services`, `sorting_rules`, `static_resources`, `system_type_definitions`, `users`, `webdav_client_permissions`
118
126
 
119
- For full control over the export configuration (including `assignments`, `catalog_static_resources`, `library_static_resources`, and `customer_lists`), use `--data-units` with a JSON string matching the `ExportDataUnitsConfiguration` shape. The `storefronts` object is keyed by storefront name and may select only one storefront.
127
+ Prefer `--all` or `all` IDs over hand-written JSON. `--all` already includes `catalog_static_resources`, `library_static_resources`, and `customer_lists`. For anything else the flags cannot express (such as `assignments`, or specific static resource or customer list IDs), use `--data-units` with a JSON string matching the `ExportDataUnitsConfiguration` shape. The `storefronts` object is keyed by storefront name and may select only one storefront.
120
128
 
121
129
  The `storefronts` export data unit requires B2C Commerce 26.10 or later. Failed storefront exports include a version note alongside the original error; check the instance version when the server rejects this data unit.
@@ -39,6 +39,8 @@ b2c job export --site MySite --site-data campaigns_and_promotions --output ./ver
39
39
  ```
40
40
 
41
41
  `--site` alone exports all site data; specify `--site-data` for focused work.
42
+ For a full instance export use `--all`; `--site all`, `--catalog all`, etc. select
43
+ every object of one type. Prefer these flags over hand-written `--data-units` JSON.
42
44
  Directory output retains the platform's generated `*_export` root. Do not overwrite
43
45
  an existing/applied migration. Exports may contain secrets or unrelated defaults;
44
46
  review and trim before committing, preserving XSD-required fields.
@@ -295,8 +295,8 @@
295
295
  "files": [
296
296
  {
297
297
  "path": "references/EXPORT.md",
298
- "bytes": 6540,
299
- "digest": "sha256:301408dcb37fa2d6fb7da5bfaed2d420148887d2c90ccf3fa5dc6396f66a6120"
298
+ "bytes": 7306,
299
+ "digest": "sha256:bd62c1e6d78a4690fe0aaaf886f9ea6017562647461b7d1ad40a58799f6374c4"
300
300
  },
301
301
  {
302
302
  "path": "references/IMPORT.md",
@@ -310,8 +310,8 @@
310
310
  },
311
311
  {
312
312
  "path": "SKILL.md",
313
- "bytes": 3017,
314
- "digest": "sha256:f012045ffe8356ec9b7276a63b25f3954e85307af5f0afc4f009bf80b3e57d4c"
313
+ "bytes": 3061,
314
+ "digest": "sha256:ba61fedcbd471a79d43d1ad767ab2337b0dae6432b672937fae05fcd18ea2099"
315
315
  }
316
316
  ]
317
317
  },
@@ -485,8 +485,8 @@
485
485
  },
486
486
  {
487
487
  "path": "SKILL.md",
488
- "bytes": 2952,
489
- "digest": "sha256:774643b9a77c8cb389f6f9ddf54043b8c2a2ded12e25ed5312ea8b26d8643a5c"
488
+ "bytes": 3119,
489
+ "digest": "sha256:a8d27be0083ba0e773bdd5837ef1451ed1ce6685978cd37f0acf9bcc19b0f532"
490
490
  }
491
491
  ]
492
492
  },
@@ -1,5 +1,11 @@
1
1
  # @salesforce/b2c-agent-plugins
2
2
 
3
+ ## 1.12.1
4
+
5
+ ### Patch Changes
6
+
7
+ - [#759](https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/pull/759) [`3b4534b`](https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/commit/3b4534b29225c5eba8627b5b0a90233785051c96) - Document `b2c job export --all` and the `all` ID for `--site`, `--catalog`, `--library`, `--inventory-list`, and `--price-book`, so agents choose these flags over hand-written data-units JSON. (Thanks [@clavery](https://github.com/clavery)!)
8
+
3
9
  ## 1.12.0
4
10
 
5
11
  ### Minor Changes
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "b2c",
3
- "version": "1.12.0",
3
+ "version": "1.12.1",
4
4
  "description": "B2C Commerce development skills including Custom API development guides.",
5
5
  "author": {
6
6
  "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": "b2c",
4
- "version": "1.12.0",
4
+ "version": "1.12.1",
5
5
  "description": "B2C Commerce development skills including Custom API development guides.",
6
6
  "author": {
7
7
  "name": "Salesforce"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "b2c-cli",
3
- "version": "1.12.0",
3
+ "version": "1.12.1",
4
4
  "description": "B2C CLI Skills for Salesforce Commerce Cloud development.",
5
5
  "author": {
6
6
  "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": "b2c-cli",
4
- "version": "1.12.0",
4
+ "version": "1.12.1",
5
5
  "description": "B2C CLI Skills for Salesforce Commerce Cloud development.",
6
6
  "author": {
7
7
  "name": "Salesforce"
@@ -48,6 +48,7 @@ b2c job import ./archive --show-log
48
48
  b2c job import ./storefront-export.zip --wait-for-storefront
49
49
  b2c job export --site MySite --site-data campaigns_and_promotions --output ./export
50
50
  b2c job export --storefront my-storefront --output ./export
51
+ b2c job export --all --output ./full-export
51
52
  ```
52
53
 
53
54
  Import/export wait by default and transfer files over WebDAV. Jobs prefer SCAPI
@@ -27,6 +27,13 @@ import, the same approach reports execution status without `localPath`.
27
27
  The `job export` command exports data from a B2C Commerce instance as a site archive. You must specify at least one data unit to export.
28
28
 
29
29
  ```bash
30
+ # export everything (global data, sites, catalogs, libraries, static resources,
31
+ # inventory lists, price books, customer lists)
32
+ b2c job export --all --output ./full-export
33
+
34
+ # export every object of a type with the special ID "all"
35
+ b2c job export --site all --catalog all --library all
36
+
30
37
  # export global metadata
31
38
  b2c job export --global-data meta_data
32
39
 
@@ -96,17 +103,18 @@ Do not require a temporary directory and copy step for export-based migrations.
96
103
 
97
104
  #### Available Data Units
98
105
 
99
- **Top-level categories** (each takes one or more IDs via flags):
106
+ **Top-level categories** (each takes one or more IDs, or the special ID `all` for every object of that type):
100
107
 
101
- | Flag | Description |
102
- | ------------------ | ------------------------------------------------------------------------------ |
103
- | `--site` | Site IDs to export (use `--site-data` to pick specific units, defaults to all) |
104
- | `--storefront` | One composable storefront name |
105
- | `--catalog` | Catalog IDs |
106
- | `--library` | Library IDs |
107
- | `--inventory-list` | Inventory list IDs |
108
- | `--price-book` | Price book IDs |
109
- | `--global-data` | Global data units (comma-separated names from the list below) |
108
+ | Flag | Description |
109
+ | ------------------ | --------------------------------------------------------------------------------------------------- |
110
+ | `--site` | Site IDs to export (use `--site-data` to pick specific units, defaults to all) |
111
+ | `--storefront` | One composable storefront name |
112
+ | `--catalog` | Catalog IDs |
113
+ | `--library` | Library IDs |
114
+ | `--inventory-list` | Inventory list IDs |
115
+ | `--price-book` | Price book IDs |
116
+ | `--global-data` | Global data units (comma-separated names from the list below) |
117
+ | `--all` | Everything above plus static resources and customer lists; exclusive with all except `--storefront` |
110
118
 
111
119
  **Site data units** (use with `--site-data`):
112
120
 
@@ -116,6 +124,6 @@ Do not require a temporary directory and copy step for export-based migrations.
116
124
 
117
125
  `access_roles`, `all`, `csc_settings`, `csrf_whitelists`, `custom_preference_groups`, `custom_quota_settings`, `custom_types`, `event_routing`, `geolocations`, `global_custom_objects`, `job_schedules`, `job_schedules_deprecated`, `locales`, `meta_data`, `oauth_providers`, `ocapi_settings`, `page_meta_tags`, `preferences`, `price_adjustment_limits`, `services`, `sorting_rules`, `static_resources`, `system_type_definitions`, `users`, `webdav_client_permissions`
118
126
 
119
- For full control over the export configuration (including `assignments`, `catalog_static_resources`, `library_static_resources`, and `customer_lists`), use `--data-units` with a JSON string matching the `ExportDataUnitsConfiguration` shape. The `storefronts` object is keyed by storefront name and may select only one storefront.
127
+ Prefer `--all` or `all` IDs over hand-written JSON. `--all` already includes `catalog_static_resources`, `library_static_resources`, and `customer_lists`. For anything else the flags cannot express (such as `assignments`, or specific static resource or customer list IDs), use `--data-units` with a JSON string matching the `ExportDataUnitsConfiguration` shape. The `storefronts` object is keyed by storefront name and may select only one storefront.
120
128
 
121
129
  The `storefronts` export data unit requires B2C Commerce 26.10 or later. Failed storefront exports include a version note alongside the original error; check the instance version when the server rejects this data unit.
@@ -39,6 +39,8 @@ b2c job export --site MySite --site-data campaigns_and_promotions --output ./ver
39
39
  ```
40
40
 
41
41
  `--site` alone exports all site data; specify `--site-data` for focused work.
42
+ For a full instance export use `--all`; `--site all`, `--catalog all`, etc. select
43
+ every object of one type. Prefer these flags over hand-written `--data-units` JSON.
42
44
  Directory output retains the platform's generated `*_export` root. Do not overwrite
43
45
  an existing/applied migration. Exports may contain secrets or unrelated defaults;
44
46
  review and trim before committing, preserving XSD-required fields.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "b2c-ops",
3
- "version": "1.12.0",
3
+ "version": "1.12.1",
4
4
  "description": "B2C Commerce operator and administrator runbooks for job health, checkout and failed orders, edge traffic and bots, and incident triage.",
5
5
  "author": {
6
6
  "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": "b2c-ops",
4
- "version": "1.12.0",
4
+ "version": "1.12.1",
5
5
  "description": "B2C Commerce operator and administrator runbooks for job health, checkout and failed orders, edge traffic and bots, and incident triage.",
6
6
  "author": {
7
7
  "name": "Salesforce"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@salesforce/b2c-agent-plugins",
3
- "version": "1.12.0",
3
+ "version": "1.12.1",
4
4
  "description": "B2C Commerce agent skills plugins for development and operations. Private — distributed via GitHub release zips.",
5
5
  "private": true
6
6
  }
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "storefront-next",
3
- "version": "1.12.0",
3
+ "version": "1.12.1",
4
4
  "description": "Storefront Next development skills for building React 19 storefronts on Salesforce B2C Commerce.",
5
5
  "author": {
6
6
  "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.12.0",
4
+ "version": "1.12.1",
5
5
  "description": "Storefront Next development skills for building React 19 storefronts on Salesforce B2C Commerce.",
6
6
  "author": {
7
7
  "name": "Salesforce"
@@ -491,5 +491,5 @@
491
491
  "enableJsonFlag": false
492
492
  }
493
493
  },
494
- "version": "3.5.1"
494
+ "version": "3.5.2"
495
495
  }
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.5.1",
4
+ "version": "3.5.2",
5
5
  "author": "Salesforce",
6
6
  "license": "Apache-2.0",
7
7
  "repository": "SalesforceCommerceCloud/b2c-developer-tooling",
@@ -80,8 +80,8 @@
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.12.0",
84
- "@salesforce/b2c-tooling-sdk": "2.6.1"
83
+ "@salesforce/b2c-agent-plugins": "1.12.1",
84
+ "@salesforce/b2c-tooling-sdk": "2.6.2"
85
85
  },
86
86
  "bundledDependencies": [
87
87
  "@modelcontextprotocol/server",