@doswiftly/storefront-sdk 7.1.0 → 9.1.0

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.
Files changed (2) hide show
  1. package/CHANGELOG.md +37 -0
  2. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,42 @@
1
1
  # Changelog
2
2
 
3
+ ## 9.1.0
4
+
5
+ ### Minor Changes
6
+
7
+ - f2ad734: **Version-sync release**: align `@doswiftly/storefront-operations` and `@doswiftly/storefront-sdk` back to the same version (`9.1.0`) as required by their linked package contract.
8
+
9
+ ### Why this release
10
+
11
+ A prior release sequence left the two linked packages on different majors (`@doswiftly/storefront-operations@8.0.0` + `@doswiftly/storefront-sdk@9.0.0`). The linked contract guarantees consumers a "matching set of operation names ↔ SDK runtime" — desynced majors break that guarantee and confuse downstream codegen consumers.
12
+
13
+ This release re-aligns both to `9.1.0`. **No API surface change**, no operation rename, no SDK behavior change. Pure version-sync.
14
+
15
+ ### Migration
16
+
17
+ None. If you have either package on `^8.x` or `^9.x`, upgrade both to `9.1.0` to stay on a supported linked pair. Subsequent releases ship from this aligned baseline.
18
+
19
+ ### Reference
20
+
21
+ Linked semantics in `.changeset/config.json`: changesets calculates `max(versions across linked pair) + bump-type` and applies it to every member. With `operations@8.0.0` and `sdk@9.0.0` already published, `max = 9.0.0`; a minor bump on both yields `9.1.0` for both. Future major releases (real BREAKING changes) jump from this aligned baseline organically.
22
+
23
+ ## 9.0.0
24
+
25
+ ### Major Changes
26
+
27
+ - 5c4e080: **BREAKING (version-only)**: Bump `@doswiftly/storefront-sdk` to 8.0.0 to stay in lockstep with `@doswiftly/storefront-operations@8.0.0` (linked package contract — same major between them).
28
+
29
+ ### Why this release
30
+
31
+ The SDK code itself is unchanged. This is a version-sync release that matches the BREAKING operations rename shipped in `@doswiftly/storefront-operations@8.0.0` (26 operations renamed to verb-first to match the GraphQL schema field names — see operations 8.0.0 CHANGELOG for the full migration table).
32
+
33
+ ### Migration
34
+
35
+ If you upgrade `@doswiftly/storefront-sdk` from `7.x` → `8.x`, you MUST also upgrade `@doswiftly/storefront-operations` to `8.x` (they are linked). After upgrading:
36
+ 1. Regenerate codegen against the new operations package.
37
+ 2. Update operation imports per the migration table in `@doswiftly/storefront-operations@8.0.0` CHANGELOG (e.g. `CheckoutDiscountCodeApply` → `CheckoutApplyDiscountCode`, `$checkoutId` → `$id`).
38
+ 3. No SDK API surface change beyond the operation name re-exports — runtime client behavior is identical.
39
+
3
40
  ## 7.1.0
4
41
 
5
42
  ### Minor Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@doswiftly/storefront-sdk",
3
- "version": "7.1.0",
3
+ "version": "9.1.0",
4
4
  "description": "Storefront runtime SDK for DoSwiftly Commerce — layered transport, middleware pipeline, React providers, Zustand stores, cache strategies. 0 runtime dependencies in core.",
5
5
  "type": "module",
6
6
  "files": [