dsh-plugin-toolkit 0.7.0 → 0.7.1

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,3 +1,18 @@
1
+ ## 0.7.1
2
+
3
+ The action now checks the tarball, which is the only thing a user installs.
4
+
5
+ - `uses: WJDdidi-1/dsh-plugin-toolkit@v1` defaults to `command: verify` instead
6
+ of `doctor`. `doctor` reads the working copy, so a `files` list that omits
7
+ `client.js` passes it and the plugin installs without a panel.
8
+ - The action fetches the published package with `npx` rather than shipping
9
+ `node_modules` in the repository — `verify` mounts the panel, which needs
10
+ jsdom and React, and those belong to the caller's dev dependencies.
11
+ - New `version` input (default `latest`) so a workflow can pin the tool.
12
+ - `test/action.test.mjs` guards the three things that break silently: the
13
+ default command, the commands it offers existing in the CLI, and the README
14
+ showing the action the way a consumer writes it.
15
+
1
16
  # Changelog
2
17
 
3
18
  ## 0.7.0
package/README.md CHANGED
@@ -215,9 +215,17 @@ The same checks run as a GitHub Action, so a tag cannot go out on a plugin that
215
215
  - uses: WJDdidi-1/dsh-plugin-toolkit@v1
216
216
  with:
217
217
  dir: plugin # the folder holding the plugin's package.json
218
+ command: verify # pack it, install the tarball, mount the panel
218
219
  ```
219
220
 
220
- `command: index` audits `market/index.json` instead, and fails on any version that cannot state a host range.
221
+ `verify` is the default because it is the only check that reads what a user
222
+ actually installs: `doctor` reads the working copy, so a `files` list that
223
+ forgets `client.js` passes it and fails only after `npm i`.
224
+
225
+ `command: doctor` stops at the manifest checks (fast, no install), and
226
+ `command: index` audits `market/index.json` instead, failing on any version that
227
+ cannot state a host range. Pin `version:` if you would rather not track the
228
+ latest release.
221
229
 
222
230
  ## What `doctor` checks
223
231
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dsh-plugin-toolkit",
3
- "version": "0.7.0",
3
+ "version": "0.7.1",
4
4
  "description": "Preflight, release and test DeepSeek Harness plugins: checks what the host needs, waits for npm to actually serve the version, and keeps the market index honest.",
5
5
  "type": "module",
6
6
  "bin": {