Repository navigation
v0.5.2
0.5.2
Compatibility: dsh ^0.1.7-alpha.1 || ^0.2.0-rc.1 || ^0.2.1-alpha.1 — verified on dsh web 0.2.1-alpha.1 and DSH Desktop 0.2.0-rc.2.
Changed
- Build baseline moved from
0.2.0-rc.1to0.2.1-alpha.1for every@deepseek-ai/*pin (@deepseek-ai/cordis4.0.5-alpha.1,@deepseek-ai/schemastery3.18.5-alpha.1). - Appended
|| ^0.2.1-alpha.1to every@deepseek-ai/dsh*peer range. - Added the missing
peerDependenciesblock. This package declared none, so the host compatibility gate had nothing to evaluate and could never refuse it. - Unified on pnpm and removed
package-lock.json: the repository recorded three different cohorts at once (^0.1.7-alpha.1in package.json,0.1.7-alpha.2in the npm lock,dsh-tools@0.1.2-alpha.2in the pnpm lock, and0.2.0-rc.1on disk). - README: declared floor is now dsh >= 0.1.7-alpha.1 (or 0.2.x).
Verified: pnpm install / typecheck / build / test (138) all green; cold boot in an isolated profile against a real 0.2.1-alpha.1 host passes.
npm i @fonlan/dsh-gitmemo@0.5.2