@uni-design-system/uni-mcp 10.2.0 → 10.3.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.
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,28 @@
|
|
|
1
1
|
# @uni-design-system/uni-mcp
|
|
2
2
|
|
|
3
|
+
## 10.3.0
|
|
4
|
+
|
|
5
|
+
## 10.2.1
|
|
6
|
+
|
|
7
|
+
### Patch Changes
|
|
8
|
+
|
|
9
|
+
- [`704e79b`](https://github.com/uni-design-system/uni/commit/704e79bb896bd32de17f45b4bed8e5b9e5882186) Thanks [@gaenglish](https://github.com/gaenglish)! - The published MCP server carries the index for its own release.
|
|
10
|
+
|
|
11
|
+
`uni-mcp@10.2.0` shipped a bundle whose index was stamped `meta.version:
|
|
12
|
+
10.1.0`. The data itself was current, but the one field a consumer reads to
|
|
13
|
+
check which release the server describes said the previous one — the same drift
|
|
14
|
+
the version alignment had just been made to end.
|
|
15
|
+
|
|
16
|
+
The cause was ordering, not data. `tsup` **inlines** `uni-index.json` into the
|
|
17
|
+
bundle, so the dist built during the verify step was stamped before
|
|
18
|
+
`changeset version` ran; publishing then shipped that stale bundle even though
|
|
19
|
+
the regenerated index was correctly committed to the repo. `version-packages`
|
|
20
|
+
now rebuilds `uni-mcp` after regenerating the index, so the artifact and its
|
|
21
|
+
source agree.
|
|
22
|
+
|
|
23
|
+
The general rule, for anything added later: a package whose dist embeds
|
|
24
|
+
release-time data has to be rebuilt _after_ the version bump, not before.
|
|
25
|
+
|
|
3
26
|
## 10.2.0
|
|
4
27
|
|
|
5
28
|
### Patch Changes
|