chore(deps): 宿主开发依赖对齐 0.2 线（0.1.0-rc.6 → 0.2.0-rc.1） - #344
Merged
Merged
Conversation
peerDependencies 自 #121 起已声明覆盖 0.2.x，但 devDependencies 与 lockfile 一直停在 0.1.0-rc.8，CI 的 npm ci 装的也是这套——声明支持 0.2 却从未验证， 中间隔着 0.1.5 / 0.1.6 / 0.1.7 三条线外加整个 0.2.0。本次把四个 @deepseek-ai/dsh-* 开发依赖提到 ^0.2.0-rc.1（现锁 0.2.0-rc.2），并让 README 的兼容性说明与 peer 声明一致（原文只写「兼容 DSH 0.1.x」）。 运行时代码零改动：src/ 未动、lib/ 未重新生成，check-sync 通过。测试 1437 项 在 0.2.0-rc.1（当前桌面端 2.0.16-next 内置内核）与 0.2.0-rc.2 上均 1436 通过 / 0 失败 / 1 跳过。 依赖面本身很小，升级无需改代码：src/ 只用到宿主四个 API——dsh-llm 的 createUserMessage 与 BlockAssembler、dsh-tools 的 defineTool、schemastery 的 z；0.2 线上这四个都在，createMessage 仍是 structuredClone + deepFreeze、 不带 schema 校验，故 source.kind: "plugin:dsh-mneme" 之类的自定义取值不受影响。
|
Warning Review limit reachedNext included review available in 6 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Repository: slow-stack/mneme/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
问题
peerDependencies从 #121 起就声明覆盖 0.2.x：但
devDependencies一直停在^0.1.0-rc.6—— 在 0.x 语义下这等于>=0.1.0-rc.6 <0.2.0，永远装不到 0.2.x —— lockfile 锁在0.1.0-rc.8，CI 的npm ci装的也是这套。结果：声明支持 0.2，却没有任何测试跑在 0.2 上。中间隔着 0.1.5 / 0.1.6 / 0.1.7 三条线，外加整个 0.2.0。而当前桌面端 DSH NEXT 2.0.16-next 内置的内核已经是
0.2.0-rc.1—— 用户跑在从未被验证过的版本上。改动
@deepseek-ai/dsh-*开发依赖^0.1.0-rc.6→^0.2.0-rc.1（现锁0.2.0-rc.2，caret 覆盖整个 0.2.x）运行时代码零改动：
src/未动、lib/未重新生成（check-sync 通过）。peerDependencies未改，0.1.x 仍可安装。验证
测试 1437 项，两个内核版本都跑过：
0.2.0-rc.10.2.0-rc.2^0.2.0-rc.1解析到的最新另有完整 CI 路径回放（
npm ci→check-sync→npm test）全绿。依赖面本身很小，升级无需改代码。
src/只用到宿主四个 API：createUserMessage{content, source}）BlockAssemblerdefineToolz另注：
createMessage在 0.2 上仍是structuredClone+deepFreeze、不带 schema 校验，所以source.kind: "plugin:dsh-mneme"这类自定义取值不会被拦。一个遗留问题（不在本 PR 范围）
改完之后，0.1.x 变成了「声明但不再被 CI 覆盖」的那一侧。本 PR 保留 peer 里的 0.1.x 分支（老桌面端仍可安装，且运行时代码零改动所以行为不变），但要让两边都有覆盖，需要给 CI 加一个宿主版本矩阵维度——代价是 CI 时间翻倍。要不要做、怎么做，想听意见。