@ilaomianyang/dsh-memory-graph 0.10.2 → 0.10.3
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 +14 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,19 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.10.3 — 2026-11-03
|
|
4
|
+
|
|
5
|
+
发布流水线的两件收尾。插件功能没有变化——这一版自己就是流水线的验收样本。
|
|
6
|
+
|
|
7
|
+
**Added**
|
|
8
|
+
|
|
9
|
+
- 发布成功后自动在本仓库建 GitHub Release：`gh release create --generate-notes`，并把 `npm pack` 出来的 tarball 附上去。建 Release 的前提是 npm 已经接受这个版本（`steps.publish.outcome == 'success'`），所以不会出现「有 Release、npm 上没有」的错位；同名 Release 已存在就跳过，重跑同一条流水线是安全的。`gh` 是 runner 自带的，没有引入第三方 action。
|
|
10
|
+
- 给 `v0.10.0`、`v0.10.1`、`v0.10.2` 补建了 Release。
|
|
11
|
+
|
|
12
|
+
**Changed**
|
|
13
|
+
|
|
14
|
+
- `actions/checkout@v4`、`actions/setup-node@v4` → `v5`。GitHub 通报 Node 20 运行时弃用：v4 会被强行拉到 Node 24 上跑，功能不变但每次 run 都挂一条警告。
|
|
15
|
+
- 发布流水线需要 `contents: write`（建 Release 用），原来只有 `contents: read`。
|
|
16
|
+
|
|
3
17
|
## 0.10.2 — 2026-11-03
|
|
4
18
|
|
|
5
19
|
补一个从第一天就存在的渲染缺陷，并让发布流水线第一次真正跑完。
|