feat(compat): support DSH 0.2.0-rc.1 and 0.2.0-rc.2 - #11
Conversation
Extend the exact support list so 0.2.0 hosts pass app-boot peer checks while older verified releases keep loading.
Point local and CI baseline hosts at the newest supported release so day-to-day work matches 0.2.0, while older matrix lanes still rebuild their own runtimes.
List the lockfile's exact DSH 0.2.0-rc.2 packages in minimumReleaseAgeExclude so frozen install can succeed without disabling the default cooldown.
pnpm 11.7 honors only the first name@version rule per package, so the old 0.1.5-rc.2 rows blocked the 0.2.0-rc.2 pin. Keep the current development pin only.
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dfb9e1e2ce
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -0,0 +1,25 @@ | |||
| # 主 CI 冻结安装因 `minimumReleaseAge` 拒绝开发 pin | |||
There was a problem hiding this comment.
This new troubleshooting page is committed only as the Chinese canonical file, and the English index consequently sends readers back to that Chinese page. Repository documentation rules require a synchronized foo.md / foo.en.md pair, so add minimum-release-age-dev-pin.en.md and point the English index to it.
AGENTS.md reference: AGENTS.md:L31-L31
Useful? React with 👍 / 👎.
| "@deepseek-ai/dsh-subprocess": "0.1.5-rc.2", | ||
| "@deepseek-ai/dsh-subprocess-local": "0.1.5-rc.2", | ||
| "@deepseek-ai/cordis": "4.0.4", | ||
| "@deepseek-ai/dsh-agent-default-model": "0.2.0-rc.2", |
There was a problem hiding this comment.
When this line changes the development baseline to 0.2.0-rc.2, both .agent/note/branch-and-mirror-layout.md and its English companion continue to state that the current pin is 0.1.5-rc.2. Because repository contributors are explicitly instructed to consult these notes before making changes, subsequent compatibility work can select or describe the wrong default lane; update both note variants or remove the duplicated pin in favor of the canonical compatibility-document link.
AGENTS.md reference: AGENTS.md:L13-L15
Useful? React with 👍 / 👎.
Codex review still sent English readers to the Chinese troubleshooting page, and the agent note still named 0.1.5-rc.2 as the pin. The pin now lives only in the compatibility contract.
1 participant
Summary
@deepseek-ai/dsh-*peer OR ranges to0.2.0-rc.1and0.2.0-rc.2, so 0.2.0 hosts passapp-bootwhile the seven previously verified releases stay loadable.0.1.5-rc.2. Existingsrc/compat/structure probes cover settings, schema, and icons; 0.2.0-only packages stay out of the peer OR..cursor/directory.Test plan
pnpm compat:checkon the development pin (0.1.5-rc.2)0.2.0-rc.1and0.2.0-rc.2pnpm test,pnpm build,pnpm test:artifact,pnpm docs:checkopenTab/openResourceon a 0.2.0 host with a selected session