@v-office/website-sdk 2.18.0 → 2.18.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.
@@ -1,32 +1,31 @@
1
1
  # Changelog
2
2
 
3
- This file is the versioned changelog index for the website SDK instructions.
3
+ <!-- generated by `node .github/release/cli.mts index`; do not edit by hand -->
4
4
 
5
- ## Versions
5
+ Release notes of `@v-office/website-sdk`, newest first. Each version has its own directory.
6
6
 
7
- - `versions/2.18.0/CHANGELOG.md`: `@v-office/website-sdk` 2.18.0 release notes.
8
- - `versions/2.17.1/CHANGELOG.md`: `@v-office/website-sdk` 2.17.1 release notes.
9
- - `versions/2.17.0/CHANGELOG.md`: `@v-office/website-sdk` 2.17.0 release notes.
10
- - `versions/2.16.3/CHANGELOG.md`: `@v-office/website-sdk` 2.16.3 release notes.
11
- - `versions/2.16.2/CHANGELOG.md`: `@v-office/website-sdk` 2.16.2 documentation release notes.
12
- - `versions/2.16.1/CHANGELOG.md`: `@v-office/website-sdk` 2.16.1 release notes.
13
- - `versions/2.16.0/CHANGELOG.md`: `@v-office/website-sdk` 2.16.0 release notes.
14
- - `versions/2.15.0/CHANGELOG.md`: `@v-office/website-sdk` 2.15.0 release notes.
15
- - `versions/2.14.0/CHANGELOG.md`: `@v-office/website-sdk` 2.14.0 release notes.
16
- - `versions/2.13.0/CHANGELOG.md`: `@v-office/website-sdk` 2.13.0 release notes.
17
- - `versions/2.12.0/CHANGELOG.md`: `@v-office/website-sdk` 2.12.0 release notes.
18
- - `versions/2.11.0/CHANGELOG.md`: `@v-office/website-sdk` 2.11.0 release notes.
19
- - `versions/2.10.0/CHANGELOG.md`: `@v-office/website-sdk` 2.10.0 release notes.
20
- - `versions/2.9.0/CHANGELOG.md`: `@v-office/website-sdk` 2.9.0 release notes.
21
- - `versions/2.8.0/CHANGELOG.md`: `@v-office/website-sdk` 2.8.0 release notes.
22
- - `versions/2.7.0/CHANGELOG.md`: `@v-office/website-sdk` 2.7.0 release notes.
23
- - `versions/2.6.0/CHANGELOG.md`: compatibility note for an unreleased version label.
24
- - `versions/2.5.0/CHANGELOG.md`: `@v-office/website-sdk` 2.5.0 release notes.
25
- - `versions/2.4.3/CHANGELOG.md`: `@v-office/website-sdk` 2.4.3 documentation release notes.
26
- - `versions/2.4.2/CHANGELOG.md`: `@v-office/website-sdk` 2.4.2 release notes.
27
- - `versions/2.4.0/CHANGELOG.md`: `@v-office/website-sdk` 2.4.0 release notes.
28
- - `versions/2.3.0/CHANGELOG.md`: `@v-office/website-sdk` 2.3.0 release notes.
29
- - `versions/2.1.0/CHANGELOG.md`: `@v-office/website-sdk` 2.1.0 release notes.
30
- - `versions/2.0.0/CHANGELOG.md`: `@v-office/website-sdk` 2.0.0 release notes.
31
-
32
- Keep each future release in its own version directory so consumers can see which package version introduced each change.
7
+ - `versions/2.18.2/CHANGELOG.md`: release notes for 2.18.2
8
+ - `versions/2.18.1/CHANGELOG.md`: release notes for 2.18.1
9
+ - `versions/2.18.0/CHANGELOG.md`: release notes for 2.18.0
10
+ - `versions/2.17.1/CHANGELOG.md`: release notes for 2.17.1
11
+ - `versions/2.17.0/CHANGELOG.md`: release notes for 2.17.0
12
+ - `versions/2.16.3/CHANGELOG.md`: release notes for 2.16.3
13
+ - `versions/2.16.2/CHANGELOG.md`: release notes for 2.16.2
14
+ - `versions/2.16.1/CHANGELOG.md`: release notes for 2.16.1
15
+ - `versions/2.16.0/CHANGELOG.md`: release notes for 2.16.0
16
+ - `versions/2.15.0/CHANGELOG.md`: release notes for 2.15.0
17
+ - `versions/2.14.0/CHANGELOG.md`: release notes for 2.14.0
18
+ - `versions/2.13.0/CHANGELOG.md`: release notes for 2.13.0
19
+ - `versions/2.12.0/CHANGELOG.md`: release notes for 2.12.0
20
+ - `versions/2.11.0/CHANGELOG.md`: release notes for 2.11.0
21
+ - `versions/2.10.0/CHANGELOG.md`: release notes for 2.10.0
22
+ - `versions/2.9.0/CHANGELOG.md`: release notes for 2.9.0
23
+ - `versions/2.8.0/CHANGELOG.md`: release notes for 2.8.0
24
+ - `versions/2.7.0/CHANGELOG.md`: release notes for 2.7.0
25
+ - `versions/2.5.0/CHANGELOG.md`: release notes for 2.5.0
26
+ - `versions/2.4.3/CHANGELOG.md`: release notes for 2.4.3
27
+ - `versions/2.4.2/CHANGELOG.md`: release notes for 2.4.2
28
+ - `versions/2.4.0/CHANGELOG.md`: release notes for 2.4.0
29
+ - `versions/2.3.0/CHANGELOG.md`: release notes for 2.3.0
30
+ - `versions/2.1.0/CHANGELOG.md`: release notes for 2.1.0
31
+ - `versions/2.0.0/CHANGELOG.md`: release notes for 2.0.0
@@ -1,32 +1,31 @@
1
1
  # Migration
2
2
 
3
- This file is the versioned migration index for the website SDK instructions.
3
+ <!-- generated by `node .github/release/cli.mts index`; do not edit by hand -->
4
4
 
5
- ## Available Guides
5
+ Migration guides of `@v-office/website-sdk`, newest first. Apply them in order when skipping versions.
6
6
 
7
- - `versions/2.18.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.17.1 to 2.18.0.
8
- - `versions/2.17.1/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.17.0 to 2.17.1.
9
- - `versions/2.17.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.3 to 2.17.0.
10
- - `versions/2.16.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.2 to 2.16.3.
11
- - `versions/2.16.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.1 to 2.16.2.
12
- - `versions/2.16.1/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.0 to 2.16.1.
13
- - `versions/2.16.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.15.0 to 2.16.0.
14
- - `versions/2.15.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.14.0 to 2.15.0.
15
- - `versions/2.14.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.13.0 to 2.14.0.
16
- - `versions/2.13.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.12.0 to 2.13.0.
17
- - `versions/2.12.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.11.0 to 2.12.0.
18
- - `versions/2.11.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.10.0 to 2.11.0.
19
- - `versions/2.10.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.9.0 to 2.10.0.
20
- - `versions/2.9.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.8.0 to 2.9.0.
21
- - `versions/2.8.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.7.0 to 2.8.0.
22
- - `versions/2.7.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.5.x to 2.7.0.
23
- - `versions/2.6.0/MIGRATION.md`: compatibility note for an unreleased version label.
24
- - `versions/2.5.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.3 to 2.5.0.
25
- - `versions/2.4.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.2 to 2.4.3.
26
- - `versions/2.4.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.1 to 2.4.2.
27
- - `versions/2.4.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.3.x to 2.4.0.
28
- - `versions/2.3.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.1.0 to 2.3.0.
29
- - `versions/2.1.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.0.0 to 2.1.0.
30
- - `versions/2.0.0/MIGRATION.md`: migrate from the legacy 1.x CMS-style website SDK API to `@v-office/website-sdk` 2.0.0.
31
-
32
- Keep each future migration in its own version directory so consumers can clearly see the source and target versions for every upgrade path.
7
+ - `versions/2.18.2/MIGRATION.md`: Migration: 2.18.1 to 2.18.2
8
+ - `versions/2.18.1/MIGRATION.md`: Migration: 2.18.0 to 2.18.1
9
+ - `versions/2.18.0/MIGRATION.md`: Migration: 2.17.1 to 2.18.0
10
+ - `versions/2.17.1/MIGRATION.md`: Migration: 2.17.0 to 2.17.1
11
+ - `versions/2.17.0/MIGRATION.md`: Migration: 2.16.3 to 2.17.0
12
+ - `versions/2.16.3/MIGRATION.md`: Migration: 2.16.2 to 2.16.3
13
+ - `versions/2.16.2/MIGRATION.md`: Migration: 2.16.1 to 2.16.2
14
+ - `versions/2.16.1/MIGRATION.md`: Migration: 2.16.0 to 2.16.1
15
+ - `versions/2.16.0/MIGRATION.md`: Migration: 2.15.0 to 2.16.0
16
+ - `versions/2.15.0/MIGRATION.md`: Migration: 2.14.0 to 2.15.0
17
+ - `versions/2.14.0/MIGRATION.md`: Migration: 2.13.0 to 2.14.0
18
+ - `versions/2.13.0/MIGRATION.md`: Migration: 2.12.0 to 2.13.0
19
+ - `versions/2.12.0/MIGRATION.md`: Migration: 2.11.0 to 2.12.0
20
+ - `versions/2.11.0/MIGRATION.md`: Migration: 2.10.0 to 2.11.0
21
+ - `versions/2.10.0/MIGRATION.md`: Migration: 2.9.0 to 2.10.0
22
+ - `versions/2.9.0/MIGRATION.md`: Migration: 2.8.0 to 2.9.0
23
+ - `versions/2.8.0/MIGRATION.md`: Migration: 2.7.0 to 2.8.0
24
+ - `versions/2.7.0/MIGRATION.md`: Migration: 2.5.x to 2.7.0
25
+ - `versions/2.5.0/MIGRATION.md`: Migration: 2.4.3 to 2.5.0
26
+ - `versions/2.4.3/MIGRATION.md`: Migration: 2.4.2 to 2.4.3
27
+ - `versions/2.4.2/MIGRATION.md`: Migration: 2.4.1 to 2.4.2
28
+ - `versions/2.4.0/MIGRATION.md`: Migration: 2.3.x to 2.4.0
29
+ - `versions/2.3.0/MIGRATION.md`: Migration: 2.1.0 to 2.3.0
30
+ - `versions/2.1.0/MIGRATION.md`: Migration: 2.0.0 to 2.1.0
31
+ - `versions/2.0.0/MIGRATION.md`: Migration: Legacy 1.x API to 2.0.0
@@ -0,0 +1,16 @@
1
+ # Changelog: 2.18.1
2
+
3
+ Maintenance release. `@v-office/website-sdk` now pins `@v-office/sdk-core`
4
+ exactly, so one website SDK version always resolves one core version. There
5
+ are no functional changes.
6
+
7
+ ## Changed
8
+
9
+ - `@v-office/sdk-core` is pinned to exactly `1.20.0` instead of the caret
10
+ range `^1.19.0`. Installs that had already resolved 1.20.0 through the
11
+ range see no change; consumers whose lockfile still held 1.19.x move to
12
+ 1.20.0 with this release.
13
+
14
+ ## Unchanged
15
+
16
+ - Every public API, type and behavior of 2.18.0.
@@ -0,0 +1,12 @@
1
+ # Migration: 2.18.0 to 2.18.1
2
+
3
+ No changes required.
4
+
5
+ ## 1. Upgrade
6
+
7
+ ```sh
8
+ pnpm add @v-office/website-sdk@2.18.1
9
+ ```
10
+
11
+ Future core updates arrive through a new website SDK version; the lockfile
12
+ no longer needs a separate refresh to pick up a coordinated core release.
@@ -0,0 +1,16 @@
1
+ # Changelog: 2.18.2
2
+
3
+ Maintenance release that repairs the command line entry point. There are no
4
+ functional changes to the SDK.
5
+
6
+ ## Fixed
7
+
8
+ - The `website-sdk` binary and the `./cli` export pointed at `dist/cli.mts`,
9
+ a file the build never produced; the bundle is `dist/cli.mjs`. Package
10
+ managers logged a missing-bin warning on every install and the `website-sdk`
11
+ command did not exist. Both now point at `dist/cli.mjs`, so `website-sdk`
12
+ is available after installing the package.
13
+
14
+ ## Unchanged
15
+
16
+ - Every public API, type and behavior of 2.18.1.
@@ -0,0 +1,12 @@
1
+ # Migration: 2.18.1 to 2.18.2
2
+
3
+ No changes required.
4
+
5
+ ## 1. Upgrade
6
+
7
+ ```sh
8
+ pnpm add @v-office/website-sdk@2.18.2
9
+ ```
10
+
11
+ If you worked around the missing binary by running `dist/cli.mjs` directly,
12
+ the `website-sdk` command works again and the workaround can go.
@@ -1,32 +1,31 @@
1
1
  # Changelog
2
2
 
3
- This file is the versioned changelog index for the website SDK instructions.
3
+ <!-- generated by `node .github/release/cli.mts index`; do not edit by hand -->
4
4
 
5
- ## Versions
5
+ Release notes of `@v-office/website-sdk`, newest first. Each version has its own directory.
6
6
 
7
- - `versions/2.18.0/CHANGELOG.md`: `@v-office/website-sdk` 2.18.0 release notes.
8
- - `versions/2.17.1/CHANGELOG.md`: `@v-office/website-sdk` 2.17.1 release notes.
9
- - `versions/2.17.0/CHANGELOG.md`: `@v-office/website-sdk` 2.17.0 release notes.
10
- - `versions/2.16.3/CHANGELOG.md`: `@v-office/website-sdk` 2.16.3 release notes.
11
- - `versions/2.16.2/CHANGELOG.md`: `@v-office/website-sdk` 2.16.2 documentation release notes.
12
- - `versions/2.16.1/CHANGELOG.md`: `@v-office/website-sdk` 2.16.1 release notes.
13
- - `versions/2.16.0/CHANGELOG.md`: `@v-office/website-sdk` 2.16.0 release notes.
14
- - `versions/2.15.0/CHANGELOG.md`: `@v-office/website-sdk` 2.15.0 release notes.
15
- - `versions/2.14.0/CHANGELOG.md`: `@v-office/website-sdk` 2.14.0 release notes.
16
- - `versions/2.13.0/CHANGELOG.md`: `@v-office/website-sdk` 2.13.0 release notes.
17
- - `versions/2.12.0/CHANGELOG.md`: `@v-office/website-sdk` 2.12.0 release notes.
18
- - `versions/2.11.0/CHANGELOG.md`: `@v-office/website-sdk` 2.11.0 release notes.
19
- - `versions/2.10.0/CHANGELOG.md`: `@v-office/website-sdk` 2.10.0 release notes.
20
- - `versions/2.9.0/CHANGELOG.md`: `@v-office/website-sdk` 2.9.0 release notes.
21
- - `versions/2.8.0/CHANGELOG.md`: `@v-office/website-sdk` 2.8.0 release notes.
22
- - `versions/2.7.0/CHANGELOG.md`: `@v-office/website-sdk` 2.7.0 release notes.
23
- - `versions/2.6.0/CHANGELOG.md`: compatibility note for an unreleased version label.
24
- - `versions/2.5.0/CHANGELOG.md`: `@v-office/website-sdk` 2.5.0 release notes.
25
- - `versions/2.4.3/CHANGELOG.md`: `@v-office/website-sdk` 2.4.3 documentation release notes.
26
- - `versions/2.4.2/CHANGELOG.md`: `@v-office/website-sdk` 2.4.2 release notes.
27
- - `versions/2.4.0/CHANGELOG.md`: `@v-office/website-sdk` 2.4.0 release notes.
28
- - `versions/2.3.0/CHANGELOG.md`: `@v-office/website-sdk` 2.3.0 release notes.
29
- - `versions/2.1.0/CHANGELOG.md`: `@v-office/website-sdk` 2.1.0 release notes.
30
- - `versions/2.0.0/CHANGELOG.md`: `@v-office/website-sdk` 2.0.0 release notes.
31
-
32
- Keep each future release in its own version directory so consumers can see which package version introduced each change.
7
+ - `versions/2.18.2/CHANGELOG.md`: release notes for 2.18.2
8
+ - `versions/2.18.1/CHANGELOG.md`: release notes for 2.18.1
9
+ - `versions/2.18.0/CHANGELOG.md`: release notes for 2.18.0
10
+ - `versions/2.17.1/CHANGELOG.md`: release notes for 2.17.1
11
+ - `versions/2.17.0/CHANGELOG.md`: release notes for 2.17.0
12
+ - `versions/2.16.3/CHANGELOG.md`: release notes for 2.16.3
13
+ - `versions/2.16.2/CHANGELOG.md`: release notes for 2.16.2
14
+ - `versions/2.16.1/CHANGELOG.md`: release notes for 2.16.1
15
+ - `versions/2.16.0/CHANGELOG.md`: release notes for 2.16.0
16
+ - `versions/2.15.0/CHANGELOG.md`: release notes for 2.15.0
17
+ - `versions/2.14.0/CHANGELOG.md`: release notes for 2.14.0
18
+ - `versions/2.13.0/CHANGELOG.md`: release notes for 2.13.0
19
+ - `versions/2.12.0/CHANGELOG.md`: release notes for 2.12.0
20
+ - `versions/2.11.0/CHANGELOG.md`: release notes for 2.11.0
21
+ - `versions/2.10.0/CHANGELOG.md`: release notes for 2.10.0
22
+ - `versions/2.9.0/CHANGELOG.md`: release notes for 2.9.0
23
+ - `versions/2.8.0/CHANGELOG.md`: release notes for 2.8.0
24
+ - `versions/2.7.0/CHANGELOG.md`: release notes for 2.7.0
25
+ - `versions/2.5.0/CHANGELOG.md`: release notes for 2.5.0
26
+ - `versions/2.4.3/CHANGELOG.md`: release notes for 2.4.3
27
+ - `versions/2.4.2/CHANGELOG.md`: release notes for 2.4.2
28
+ - `versions/2.4.0/CHANGELOG.md`: release notes for 2.4.0
29
+ - `versions/2.3.0/CHANGELOG.md`: release notes for 2.3.0
30
+ - `versions/2.1.0/CHANGELOG.md`: release notes for 2.1.0
31
+ - `versions/2.0.0/CHANGELOG.md`: release notes for 2.0.0
@@ -1,32 +1,31 @@
1
1
  # Migration
2
2
 
3
- This file is the versioned migration index for the website SDK instructions.
3
+ <!-- generated by `node .github/release/cli.mts index`; do not edit by hand -->
4
4
 
5
- ## Available Guides
5
+ Migration guides of `@v-office/website-sdk`, newest first. Apply them in order when skipping versions.
6
6
 
7
- - `versions/2.18.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.17.1 to 2.18.0.
8
- - `versions/2.17.1/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.17.0 to 2.17.1.
9
- - `versions/2.17.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.3 to 2.17.0.
10
- - `versions/2.16.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.2 to 2.16.3.
11
- - `versions/2.16.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.1 to 2.16.2.
12
- - `versions/2.16.1/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.0 to 2.16.1.
13
- - `versions/2.16.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.15.0 to 2.16.0.
14
- - `versions/2.15.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.14.0 to 2.15.0.
15
- - `versions/2.14.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.13.0 to 2.14.0.
16
- - `versions/2.13.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.12.0 to 2.13.0.
17
- - `versions/2.12.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.11.0 to 2.12.0.
18
- - `versions/2.11.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.10.0 to 2.11.0.
19
- - `versions/2.10.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.9.0 to 2.10.0.
20
- - `versions/2.9.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.8.0 to 2.9.0.
21
- - `versions/2.8.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.7.0 to 2.8.0.
22
- - `versions/2.7.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.5.x to 2.7.0.
23
- - `versions/2.6.0/MIGRATION.md`: compatibility note for an unreleased version label.
24
- - `versions/2.5.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.3 to 2.5.0.
25
- - `versions/2.4.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.2 to 2.4.3.
26
- - `versions/2.4.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.4.1 to 2.4.2.
27
- - `versions/2.4.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.3.x to 2.4.0.
28
- - `versions/2.3.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.1.0 to 2.3.0.
29
- - `versions/2.1.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.0.0 to 2.1.0.
30
- - `versions/2.0.0/MIGRATION.md`: migrate from the legacy 1.x CMS-style website SDK API to `@v-office/website-sdk` 2.0.0.
31
-
32
- Keep each future migration in its own version directory so consumers can clearly see the source and target versions for every upgrade path.
7
+ - `versions/2.18.2/MIGRATION.md`: Migration: 2.18.1 to 2.18.2
8
+ - `versions/2.18.1/MIGRATION.md`: Migration: 2.18.0 to 2.18.1
9
+ - `versions/2.18.0/MIGRATION.md`: Migration: 2.17.1 to 2.18.0
10
+ - `versions/2.17.1/MIGRATION.md`: Migration: 2.17.0 to 2.17.1
11
+ - `versions/2.17.0/MIGRATION.md`: Migration: 2.16.3 to 2.17.0
12
+ - `versions/2.16.3/MIGRATION.md`: Migration: 2.16.2 to 2.16.3
13
+ - `versions/2.16.2/MIGRATION.md`: Migration: 2.16.1 to 2.16.2
14
+ - `versions/2.16.1/MIGRATION.md`: Migration: 2.16.0 to 2.16.1
15
+ - `versions/2.16.0/MIGRATION.md`: Migration: 2.15.0 to 2.16.0
16
+ - `versions/2.15.0/MIGRATION.md`: Migration: 2.14.0 to 2.15.0
17
+ - `versions/2.14.0/MIGRATION.md`: Migration: 2.13.0 to 2.14.0
18
+ - `versions/2.13.0/MIGRATION.md`: Migration: 2.12.0 to 2.13.0
19
+ - `versions/2.12.0/MIGRATION.md`: Migration: 2.11.0 to 2.12.0
20
+ - `versions/2.11.0/MIGRATION.md`: Migration: 2.10.0 to 2.11.0
21
+ - `versions/2.10.0/MIGRATION.md`: Migration: 2.9.0 to 2.10.0
22
+ - `versions/2.9.0/MIGRATION.md`: Migration: 2.8.0 to 2.9.0
23
+ - `versions/2.8.0/MIGRATION.md`: Migration: 2.7.0 to 2.8.0
24
+ - `versions/2.7.0/MIGRATION.md`: Migration: 2.5.x to 2.7.0
25
+ - `versions/2.5.0/MIGRATION.md`: Migration: 2.4.3 to 2.5.0
26
+ - `versions/2.4.3/MIGRATION.md`: Migration: 2.4.2 to 2.4.3
27
+ - `versions/2.4.2/MIGRATION.md`: Migration: 2.4.1 to 2.4.2
28
+ - `versions/2.4.0/MIGRATION.md`: Migration: 2.3.x to 2.4.0
29
+ - `versions/2.3.0/MIGRATION.md`: Migration: 2.1.0 to 2.3.0
30
+ - `versions/2.1.0/MIGRATION.md`: Migration: 2.0.0 to 2.1.0
31
+ - `versions/2.0.0/MIGRATION.md`: Migration: Legacy 1.x API to 2.0.0
@@ -0,0 +1,3 @@
1
+ {
2
+ "componentsAffectedByHeadlessChange": ["quote"]
3
+ }
@@ -0,0 +1,16 @@
1
+ # Changelog: 2.18.1
2
+
3
+ Maintenance release. `@v-office/website-sdk` now pins `@v-office/sdk-core`
4
+ exactly, so one website SDK version always resolves one core version. There
5
+ are no functional changes.
6
+
7
+ ## Changed
8
+
9
+ - `@v-office/sdk-core` is pinned to exactly `1.20.0` instead of the caret
10
+ range `^1.19.0`. Installs that had already resolved 1.20.0 through the
11
+ range see no change; consumers whose lockfile still held 1.19.x move to
12
+ 1.20.0 with this release.
13
+
14
+ ## Unchanged
15
+
16
+ - Every public API, type and behavior of 2.18.0.
@@ -0,0 +1,12 @@
1
+ # Migration: 2.18.0 to 2.18.1
2
+
3
+ No changes required.
4
+
5
+ ## 1. Upgrade
6
+
7
+ ```sh
8
+ pnpm add @v-office/website-sdk@2.18.1
9
+ ```
10
+
11
+ Future core updates arrive through a new website SDK version; the lockfile
12
+ no longer needs a separate refresh to pick up a coordinated core release.
@@ -0,0 +1,3 @@
1
+ {
2
+ "componentsAffectedByHeadlessChange": []
3
+ }
@@ -0,0 +1,16 @@
1
+ # Changelog: 2.18.2
2
+
3
+ Maintenance release that repairs the command line entry point. There are no
4
+ functional changes to the SDK.
5
+
6
+ ## Fixed
7
+
8
+ - The `website-sdk` binary and the `./cli` export pointed at `dist/cli.mts`,
9
+ a file the build never produced; the bundle is `dist/cli.mjs`. Package
10
+ managers logged a missing-bin warning on every install and the `website-sdk`
11
+ command did not exist. Both now point at `dist/cli.mjs`, so `website-sdk`
12
+ is available after installing the package.
13
+
14
+ ## Unchanged
15
+
16
+ - Every public API, type and behavior of 2.18.1.
@@ -0,0 +1,12 @@
1
+ # Migration: 2.18.1 to 2.18.2
2
+
3
+ No changes required.
4
+
5
+ ## 1. Upgrade
6
+
7
+ ```sh
8
+ pnpm add @v-office/website-sdk@2.18.2
9
+ ```
10
+
11
+ If you worked around the missing binary by running `dist/cli.mjs` directly,
12
+ the `website-sdk` command works again and the workaround can go.
@@ -0,0 +1,3 @@
1
+ {
2
+ "componentsAffectedByHeadlessChange": []
3
+ }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@v-office/website-sdk",
3
- "version": "2.18.0",
3
+ "version": "2.18.2",
4
4
  "description": "Website-facing SDK facade backed by @v-office/sdk-core",
5
5
  "bin": {
6
6
  "website-sdk": "./dist/cli.mjs"
@@ -42,19 +42,19 @@
42
42
  },
43
43
  "dependencies": {
44
44
  "@graphql-typed-document-node/core": "3.2.0",
45
- "@v-office/sdk-core": "^1.19.0",
45
+ "@v-office/sdk-core": "1.20.0",
46
46
  "effect": "4.0.0-beta.85",
47
47
  "graphql": "17.0.2",
48
48
  "yaml": "^2.9.0"
49
49
  },
50
50
  "devDependencies": {
51
51
  "@effect/tsgo": "0.31.0",
52
- "@graphql-codegen/cli": "7.2.0",
53
- "@graphql-codegen/client-preset": "6.1.1",
54
- "@types/node": "26.1.2",
55
- "oxfmt": "0.62.0",
56
- "oxlint": "1.77.0",
57
- "tsdown": "0.22.14",
52
+ "@graphql-codegen/cli": "7.4.1",
53
+ "@graphql-codegen/client-preset": "6.2.0",
54
+ "@types/node": "26.5.1",
55
+ "oxfmt": "0.67.0",
56
+ "oxlint": "1.82.0",
57
+ "tsdown": "0.23.0",
58
58
  "typescript": "7.0.2"
59
59
  },
60
60
  "engines": {
@@ -1,6 +0,0 @@
1
- # Changelog: 2.6.0
2
-
3
- `@v-office/website-sdk` 2.6.0 was never published. The Stripe Checkout work
4
- documented under this version during development shipped as 2.7.0 on 2026-07-27.
5
-
6
- Use `../2.7.0/CHANGELOG.md` as the authoritative release record.
@@ -1,6 +0,0 @@
1
- # Migration: 2.6.0
2
-
3
- `@v-office/website-sdk` 2.6.0 was never published. The planned Stripe Checkout
4
- change shipped in 2.7.0.
5
-
6
- Consumers upgrading from 2.5.x should follow `../2.7.0/MIGRATION.md`.
@@ -1,6 +0,0 @@
1
- # Changelog: 2.6.0
2
-
3
- `@v-office/website-sdk` 2.6.0 was never published. The Stripe Checkout work
4
- documented under this version during development shipped as 2.7.0 on 2026-07-27.
5
-
6
- Use `../2.7.0/CHANGELOG.md` as the authoritative release record.
@@ -1,6 +0,0 @@
1
- # Migration: 2.6.0
2
-
3
- `@v-office/website-sdk` 2.6.0 was never published. The planned Stripe Checkout
4
- change shipped in 2.7.0.
5
-
6
- Consumers upgrading from 2.5.x should follow `../2.7.0/MIGRATION.md`.