dsh-plugin-toolkit 0.13.3 → 0.13.4
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 +8 -0
- package/README.md +2 -0
- package/README.zh.md +2 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,11 @@
|
|
|
1
|
+
## 0.13.4
|
|
2
|
+
|
|
3
|
+
- **`docs/why-it-exists.md`**: the five failures that shaped these checks, each
|
|
4
|
+
with the exact error text, the root cause, the check that catches it now, and
|
|
5
|
+
how to reproduce it. Linked from both READMEs.
|
|
6
|
+
- **A release for the GitHub Action** (`v1.0.0`), so the action can be published
|
|
7
|
+
to the Marketplace.
|
|
8
|
+
|
|
1
9
|
## 0.13.3
|
|
2
10
|
|
|
3
11
|
- **`verify` no longer fails a correct plugin.** The check that calls a client
|
package/README.md
CHANGED
|
@@ -73,6 +73,8 @@ Releasing one plugin fifteen times taught me three things the ecosystem's toolin
|
|
|
73
73
|
2. **The market index is a second release, done by hand.** Each version needs an entry carrying `publishTimestamp` from the registry and `engines.dsh` from the manifest. Forget the range and the index validator rejects the PR with `Engines mismatch` — after the tag is already public.
|
|
74
74
|
3. **Reading a manifest is not the same as checking it.** A plugin can have a valid `package.json` and still be uninstallable: `files` that omit the entry the manifest points at, a bundle patch that does not exist, a README that never states the host range it declares.
|
|
75
75
|
|
|
76
|
+
The five failures behind these checks — a red dot with no panel, a row the host drops, an app that disables every plugin after one unguarded `apply()`, a tab nothing can open, and a checker that was wrong — are written up with their exact error text and how to reproduce each one: [Five plugins that installed and did nothing](https://github.com/WJDdidi-1/dsh-plugin-toolkit/blob/main/docs/why-it-exists.md).
|
|
77
|
+
|
|
76
78
|
### Four ways a plugin installs and still does nothing
|
|
77
79
|
|
|
78
80
|
Each of these shipped in a real version of this toolkit before the check below existed. A manifest check passes on all four.
|
package/README.zh.md
CHANGED
|
@@ -44,6 +44,8 @@ npx dsh-plugin-toolkit@latest release --pr --merge # 打 tag、等
|
|
|
44
44
|
|
|
45
45
|
前三条是静态的:`doctor` 和 `verify` 不用开应用就能抓到。第四条是 UI 契约,必须把面板挂起来、检查注册出去的参数——那是 [`testkit`](#不用浏览器测面板) 的活。
|
|
46
46
|
|
|
47
|
+
这五个事故——红点没有面板、宿主丢掉一行、一行没加保护的 `apply()` 让应用禁用全部插件、注册了却没人能打开的标签、以及一个判错了的检查器——都写了原始报错和复现步骤:[插件装上了,却什么都不做](https://github.com/WJDdidi-1/dsh-plugin-toolkit/blob/main/docs/why-it-exists.md)。
|
|
48
|
+
|
|
47
49
|
## 安装要求
|
|
48
50
|
|
|
49
51
|
- Node.js 18 或更新(CI 在 18/20/22 × ubuntu/macos/windows 上跑)。
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-plugin-toolkit",
|
|
3
|
-
"version": "0.13.
|
|
3
|
+
"version": "0.13.4",
|
|
4
4
|
"description": "Preflight, release and test DeepSeek Harness plugins: check a folder or any GitHub repository, wait for npm to actually serve the version, and keep the market index honest.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|