Repository navigation
Conversation
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.
(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): Version-window audit (v0.1.216..master, 122 files +5634/-378): I read all 40 Blocking issues (do not merge yet):
To proceed: (1) approve the fork workflows so CI runs; (2) sync the branch to current master; (3) confirm the CI Labeled the PR: 结构化八问:
判定:暂不可合并。 窗口干净(无回归),PR 自身 diff 是干净的版本 bump,但 CI 从未运行(action_required——作者需批准 fork workflows),且作者自认无可靠全量测试结论。作者需:①批准 fork workflows 让 CI 跑起来;②把分支同步到当前 master;③确认 CI |
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 typecheckpassed.npm run buildpassed (the existing esbuild side-effect warning remains).git diff --checkpassed.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.