Repository navigation
Releases
v0.8.0
v0.7.0
0.2.0-rc.2 迁移:dev 九包钉 0.1.7-rc.1 -> 0.2.0-rc.2 + peer 地板抬 >=0.2.0-rc.2 + package-lock 清图重生成
- match.ts 错误文案面对 0.2.0-rc.2 闭包逐条预核零漂移(pi-ai 0.87.1 Provider finish_reason / stream ended 家族 / dsh-llm-pi-ai STREAM_CLOSED / dsh-llm-deepseek 三条 Messages 文案 / DEFAULT_RETRYABLE_CODES 不变——NOT_OURS 仍正确);断言未改
- cordis 4.0.4 / schemastery 3.18.4 维持(0.2.0 闭包同钉)
- package-lock 从干净安装重生成:旧 0.1.7 锁图对新钉 ERESOLVE(沿 0.6.0 先例)
- 测试:24 单测 + 3 e2e(真 pi-ai 0.87.1 线)全绿;真机 smoke 0.2.0-rc.2 装载/移除通过
- ACCOUNT_QUOTA 攒批(7bfc49d)未动,随本波发版
v0.6.0
0.1.7-rc.1 迁移:Messages 线错误面适配(新增 unsupported stop reason / stream ended 两条 pattern 及夹具)、cordis 4.0.4/schemastery 3.18.4 随动、peer 地板抬 rc.1;icon/locale 元数据
v0.5.0
feat: match gateway-echoed EOF/TLS/stream-read wordings + stock-taxonomy code guard
Three new leak families reported upstream (#4361 comment 18418461, #3158) land
as non-retryable PI_AI_ERROR on dsh 0.1.5-rc.2 and now get claimed by the net:
- unexpected EOF (body cut short: Go io.ErrUnexpectedEOF, Node
HPE_UNEXPECTED_EOF*, zlib truncated-gunzip 'unexpected end of file') - remote error: tls: bad record MAC (Go TLS alert family)
- stream_read_error (#3158, _/space/- spellings)
Matcher now also takes the failure code and declines codes whose recovery the
harness already owns (stock default retryable set, permanent failures,
ABORTED) — mechanizing the 'only leaked spellings' charter and standing down
automatically if upstream reclassifies a wording. Everything else
(PI_AI_ERROR catch-all, DeepSeek unknown-reason codes, raw-throw UNKNOWN,
HTTP_) falls through to the message patterns.
Tests: matcher table over wordings x codes + near-misses; decision-level
coverage for the new wordings and the guard stand-down; e2e leg for the
relay-echo finish_reason shape; integration check against the installed
rc.2 classifier's real output; READMEs/CHANGELOG updated.
v0.4.0
dsh floor 0.1.5-rc.2.
- Completes the rc.2 closure: dev pins + locks had already tracked rc.2 (4ab6787); this release adds the peer floor and README support floor.
- No code change vs 0.3.1 — rc.2 is a UI-only host release.
Note: the Release run's verify gate expired before npm packument propagation, but the publish landed and was confirmed on the registry; gate widened to ~5min in f47fec5.
v0.3.1
docs: uninstall sections + smoke script key + smoke uninstall leg
v0.3.0
chore(deps): ride the dsh rc/stable line — 0.1.2-rc.1 closure, retire alpha
v0.2.0
chore(deps): track the dsh 0.1.2-alpha.4 closure