@bushizhanghan/dsh-publish-gate 0.8.1 → 0.8.2

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.8.2
+
+- `publish_gate_verify` now returns `pending: true` when the wait runs out with the version still invisible.
+  Measured on 0.8.1 itself: the version appeared **four minutes** after `npm publish`, so one call cannot
+  outwait it — the cap is 90 s because the host kills a tool call at 120 s. `pending` says "run it again",
+  which is a different answer from "the registry holds different bytes".
 ## 0.8.1
 
 - `publish_gate_verify` gained `waitMs` (capped at 90 s) and reports `waitedMs`. npm answers 202 and keeps

package/README.md

@@ -207,6 +207,7 @@ dsh plugin --profile desktop add @bushizhanghan/dsh-publish-gate
 - **产物层用 `npm pack --dry-run`，不用自己推 `files` 规则**：npm 的入包规则（`main` / `exports` 强制入包、README/LICENSE 强制入包、`.npmignore` 优先级）比自己实现的准。唯一的代价是它需要这台机器上有 npm，所以跑不起来时降级成 `pack-unavailable` 而不是报错。
 - **运行时层真的执行插件代码**：这是唯一能回答「装上能不能用」的办法。代价是 `apply()` 会跑，所以：假 ctx 是 Proxy 不落盘、20 秒硬超时、`skipTools` 一键跳过。
 - **`--ignore-scripts`**：dry run 不跑 `prepack`，否则检查会触发一次构建。代价是清单可能和真实产物不同，所以有 `pack-script-build` 把这件事说出来。
+- **发完那几十秒不算失败**：npm 收下包会先回 202，然后六十秒到几分钟里这个版本在 registry 上根本不存在。这个插件自己的 0.8.1 实测是**四分钟**才出现。所以 `publish_gate_verify` 加了 `waitMs` 轮询；一轮等不到就返回 `pending: true`——那是「还没轮到」，不是「没发成功」。单次最多等 90 秒，因为宿主 120 秒就掐掉工具调用，剩下的只能再跑一次。
 - **`publish_gate_verify` 比 shasum，不比版本号**：版本号相同而字节不同（发了又改、或本地根本没发）是最常见的自欺。`npm pack --dry-run` 的 shasum 和 registry 的 `dist.shasum` 是同一套算法，所以这个比较是精确的。
 - **只读**：修不修由你定，每条 finding 都带 `fix` 文案。门禁的职责是把话说清楚，不是替你做决定——所以没有 `--fix`。
 - **确定性**：全部规则是文件内容、子进程或 registry/GitHub API 检查，没有 LLM 调用——一条规则答错，你可以直接看规则。
@@ -215,7 +216,7 @@ dsh plugin --profile desktop add @bushizhanghan/dsh-publish-gate
 ## 开发
 
 ```sh
-node --test                      # 92 个引擎单测
+node --test                      # 93 个引擎单测
 node test/integration.test.mjs   # 27 条集成断言（9 个真实插件作 fixture）
 ```
 

package/lib/engine.js

@@ -1936,7 +1936,13 @@ export async function waitForPublished(name, version, localPack, opts = {}) {
     await new Promise((r) => setTimeout(r, Math.min(intervalMs, waitMs - (Date.now() - started))))
     findings = await probe(net)
   }
-  return { findings, waitedMs: Date.now() - started }
+  const served = findings.some((f) => f.rule === 'publish-served')
+  const mismatch = findings.some((f) => f.rule === 'publish-served-mismatch')
+  // `pending` means the wait ran out with the version still invisible — the
+  // normal outcome for a publish npm has not finished processing, NOT a
+  // failure. Measured on this plugin's own 0.8.1: the version appeared four
+  // minutes after `npm publish`, longer than one call can wait.
+  return { findings, waitedMs: Date.now() - started, pending: !served && !mismatch }
 }
 
 /** The async half of the gate: everything that needs a subprocess or the network. */

package/lib/index.js

@@ -199,7 +199,7 @@ export function apply(ctx, config = {}) {
           waitMs: {
             type: 'number',
             description:
-              'Poll until the registry serves the bytes, up to this many milliseconds (capped at 90000). npm returns 202 and keeps the version invisible for 60-180 s after a publish, so a single shot reports "not published" on a release that already succeeded.',
+              'Poll until the registry serves the bytes, up to this many milliseconds (capped at 90000 — the host kills a tool call at 120000). npm answers 202 and keeps the version invisible for 60-180 s after a publish, measured up to 4 minutes, so a single shot reports "not published" on a release that already succeeded. When the wait runs out with `pending: true`, run it again; that is not a failure.',
           },
         },
       },
@@ -212,7 +212,7 @@ export function apply(ctx, config = {}) {
         const { pack, findings: packFindings } = await checkPack(dir)
         if (!pack) return { ok: false, error: `npm pack --dry-run did not run, so there is nothing to compare: ${packFindings.map((f) => f.title).join('; ')}` }
         const waitMs = Math.min(Math.max(0, Number(args.waitMs) || 0), 90_000)
-        const { findings, waitedMs } = await waitForPublished(json.name, version, pack, {
+        const { findings, waitedMs, pending } = await waitForPublished(json.name, version, pack, {
           registry: cfg.registry,
           timeoutMs: cfg.networkTimeoutMs,
           waitMs,
@@ -224,6 +224,7 @@ export function apply(ctx, config = {}) {
           version,
           published: served || findings.some((f) => f.rule === 'publish-served-mismatch'),
           shasumMatch: served,
+          pending,
           localShasum: pack.shasum,
           unpackedSize: pack.unpackedSize,
           files: (pack.files || []).length,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bushizhanghan/dsh-publish-gate",
-  "version": "0.8.1",
+  "version": "0.8.2",
   "description": "Pre-publish gate for DSH plugins: manifest, dependencies, artifact, runtime, browser half, traceability and market readiness — plus an input fuzzer that drives every declared parameter with the wrong type. 发布前的七层门禁 + 入参模糊测试。",
   "type": "module",
   "main": "lib/index.js",