Skip to content

[PR] release: v0.1.217 no-op updater validation - #7184

Open
Hahn-Moen wants to merge 3 commits into
ranxianglei:masterfrom
Hahn-Moen:2026-11-18_release-v0.1.217
Open

Hahn-Moen wants to merge 3 commits into
ranxianglei:masterfrom
Hahn-Moen:2026-11-18_release-v0.1.217

Conversation

@Hahn-Moen

Copy link
Copy Markdown

Purpose

This is the required no-op validation release for the DSH desktop updater lane.

It bumps the package version from v0.1.216 to v0.1.217 and synchronizes the four published plugin manifests. It intentionally does not change updater behavior.

Validation

  • npm run typecheck passed.
  • npm run build passed (the existing esbuild side-effect warning remains).
  • The official manifest sync check passed.
  • git diff --check passed.
  • The Windows full-test wrapper hit the repository's argument-length limitation; the retry did not produce a reliable complete-suite verdict, so this PR does not claim the full suite passed.

Release gate

After this PR is merged and CI publishes v0.1.217, the release must be observed upgrading an older installed updater successfully. Only after that observation should the separate DSH minimumReleaseAge fix be prepared.

This PR must not be merged by automation.

Hahn-Moen and others added 3 commits November 18, 2026 18:49
No-op validation release required to verify that existing DSH desktop copies can update before any updater behavior change.
Keep the release manifest and lockfile root package metadata aligned.
@ranxianglei ranxianglei changed the title release: v0.1.217 no-op updater validation [PR] release: v0.1.217 no-op updater validation Nov 18, 2026
@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

(ai: qwen/qwen3.8-27b)

Reviewed PR #7184 (release v0.1.217 no-op updater validation). This is a release-type PR, so I ran the full version-window regression audit (v0.1.216..master) before judging it.

PR's own diff: pure version bump 0.1.216→0.1.217 in 6 files (+7/-7): package.json, package-lock.json (2 lines), and the four plugin manifests (.agents/plugins/marketplace.json, .claude-plugin/marketplace.json, .claude-plugin/plugin.json, plugins/codex/.codex-plugin/plugin.json). All four manifests synced (matches §5). Three commits: release bump, lockfile sync, manifest sync. No src/, no kernel/ change in the PR diff.

Version-window audit (v0.1.216..master, 122 files +5634/-378): I read all 40 src/ files, the kernel change (0.0.198→0.0.199, unit-projection anchorNote only), and the 60 test files. No regressions found. Every behavior change is targeted, documented, and pinned by a test. The window ships ~20 intentional behavior changes (3 MODEL-FACING text changes, KDD #10 thoughtSignature byte-fidelity, #6861 cache-mark pinning, #6884 sidecar demotion, #6361 Claude /clear rebind, #7085 dsh runtime-context, loopback self-recognition, process-handler lifecycle, SSE framer refactor, image cache budget, plus a batch of perf/leak/race fixes). All intentional, all tested.

Blocking issues (do not merge yet):

  1. CI has never run. All 12 check suites on head 70b667bb10 are action_required (fork PR — the author must approve the workflows). There is no authoritative green. Per §7.2 the full-suite verdict is the remote CI test lane on the pushed head.
  2. The PR body admits no reliable full-suite verdict (Windows argument-length limit).
  3. Branch is 5 commits behind master (merge-base 548e396022, master head 3f0c1d2110). The merge dry-run is clean (zero conflicts), so on merge v0.1.217 also ships master's [PR] Remove head/tail tags from the compression success receipt (keep excerpts) + add collapse timestamps + annotate kernel a | 压缩成功回执去掉 head/tail 标签(保留摘录)+ 打折叠时间戳 + kernel 锚点引文标注来源(模型可见文本,4 处) #7105 + lock sync — that is fine — but the branch should be synced to current master before merge (§7.2).

To proceed: (1) approve the fork workflows so CI runs; (2) sync the branch to current master; (3) confirm the CI test lane is green on the pushed head. After that this is a human-only merge (the PR correctly states "must not be merged by automation").

Labeled the PR: release + p3 (no-op validation release — a process step; the PR's own diff is a pure version bump).

结构化八问:

  1. 是什么问题: 这是 DSH 桌面更新器车道的 no-op 验证发版——把版本从 v0.1.216 升到 v0.1.217 并同步四个插件清单,不改动更新器行为本身。目的是在单独的 DSH minimumReleaseAge 修复动手之前,先验证「bump → CI 发布 → tag → npm」这条升级路径端到端健康。
  2. 什么原因导致的: 这不是 bug 修复,而是一个验证步骤。DSH 桌面更新器车道需要一个已验证的 no-op 发版来证明升级路径健康,之后才能安全地引入 minimumReleaseAge 行为变更。
  3. 影响范围与严重程度: PR 自身 diff 是纯版本号 bump(6 文件 +7/-7),无 src/ 无 kernel/ 改动,本身低风险(p3)。但合并后 v0.1.217 会把整个 v0.1.216..master 窗口(122 文件 +5634/-378)随更新推给所有用户——窗口内含约 20 处有意的行为变更(3 处 MODEL-FACING 文本、KDD release v0.1.3 #10 thoughtSignature 字节保真、bili claude: every request rewrites mid-history, breaking the prefix cache (cache hit falls to 8.7% on one request, 119K tokens re-billed, no fold or switch attribution) #6861 缓存标记钉住、跨 agent 核查:「session id = 唯一会话身份」这条定律,谁满足谁违反(#6880 背景) #6884 sidecar 降级、[Bug][claude] After /clear (or /new), bili MCP stays bound to the pre-clear session ID — tools hit the old session and the new one never enters plugin mode #6361 Claude /clear 重绑、[Bug][dsh] 0.2.2-rc.3 changes the runtime-context snapshot copy, dshRuntimeContextPath silently stops classifying #7085 dsh runtime-context、loopback 自识别、进程 handler 生命周期、SSE framer 重构、图片缓存预算,以及一批 perf/泄漏/竞态修复)。全部有意、有文档、有测试钉住。
  4. 怎么修复的: package.json + package-lock.json(2 行)+ 四个插件清单的版本号 0.1.216→0.1.217。3 个 commit:release bump、lockfile sync、manifest sync。四个插件清单全部同步(符合 §5)。
  5. 是否有回归问题: 窗口审计 v0.1.216..master——未发现回归。通读了全部 40 个 src/ 文件 + kernel(0.0.198→0.0.199,仅 unit-projection anchorNote)+ 60 个测试文件。每处行为变更都是定向的、有文档的、被测试钉住的。无意外语义漂移、无 fail-fast 变吞错、无阈值/时序/输出格式漂移、无缓存/重试策略静默失效。
  6. 是否破坏缓存: 否。窗口内含缓存修复(bili claude: every request rewrites mid-history, breaking the prefix cache (cache hit falls to 8.7% on one request, 119K tokens re-billed, no fold or switch attribution) #6861 客户端缓存标记钉住——修复缓存塌缩到 8.7%;image-rescale 编码缓存按数量+字节双重封顶)。没有破坏任何缓存失效策略。
  7. 是否改了设计方向: 否。全部改动在既有架构/边界/数据流之内。
  8. 是否引入了新的配置: 否。无新 env 变量、无新 config key、无新默认值。

判定:暂不可合并。 窗口干净(无回归),PR 自身 diff 是干净的版本 bump,但 CI 从未运行(action_required——作者需批准 fork workflows),且作者自认无可靠全量测试结论。作者需:①批准 fork workflows 让 CI 跑起来;②把分支同步到当前 master;③确认 CI test 车道在推送 head 上绿。之后这是 human-only 合并(PR 已正确声明「不得由自动化合并」)。

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants