Skip to content

Test and install against DSH 0.2.1-rc.2 - #293

Merged
Fei2411 merged 3 commits into
devfrom
chore/dsh-0.2.1-rc.2
Oct 19, 2026
Merged

Fei2411 merged 3 commits into
devfrom
chore/dsh-0.2.1-rc.2

Conversation

@Fei2411

@Fei2411 Fei2411 commented Oct 17, 2026

Copy link
Copy Markdown
Owner

Issue

None. DSH 0.2.1-rc.2 is the newest release candidate, and DSH Desktop offers it as an update.

What changed / 改了什么

  • The unit tests and the linter run against DSH 0.2.1-rc.2 (ds-bot/dev/harness).
  • CI: Ubuntu (Node 24 and 22) and Windows run on 0.2.1-rc.2. One Ubuntu row stays on 0.2.0-rc.2, which npm still tags as latest; it takes the place of the 0.2.1-alpha.1 row.
  • The install commands (README, known issues), the bench checkout (CONTRIBUTING) and the release checklist name 0.2.1-rc.2. The plugin README names the tested versions.
  • Not in this pull request:
    • The Docker image stays on 0.2.0-rc.2. DSH 0.2.1's web server refuses a wildcard bind address (0.0.0.0), which the image's entrypoint uses, so the image needs its own change.
    • The desktop app keeps its own DSH pin; its engine profile is in Give the desktop app its own engine profile #291.

Changelog

The install commands use DeepSeek Harness 0.2.1-rc.2.

How I checked it / 怎么验证的

  • npm test (in ds-bot/): 648 of 648 on 0.2.1-rc.2, the same as on 0.2.0-rc.2. The released 0.1.7 also passes on 0.2.1-rc.2 (635 of 635).
  • node scripts/build-client.mjs --check
  • npm run lint: 0 errors.
  • Smoke test on DSH Web 0.2.1-rc.2 (Windows): 41 of 41. Its normalized transcript is identical to a run on 0.2.0-rc.2.
  • dev/ui-shots.mjs web on both versions: every check passes. In the screenshots, one difference: the run statistics under the composer no longer show in Bot chats on 0.2.1-rc.2. ds-bot hides the composer's activity and usage entries, which 0.2.1 introduced in place of stats.
  • Every slot name and DSH style class that the client targets is still defined, by the same packages, in 0.2.1-rc.2.
  • Not checked: DSH Desktop 0.2.1-rc.2.

Checklist / 检查

  • One issue, one subject. / 只做一件事。
  • src/client/ changed → npm run build ran and client.js is committed. / 改了 src/client/ 就已重新 build 并提交 client.js。(没改 src/client/)
  • No keys, tokens or personal data, also in screenshots. / 没有密钥、token 或个人信息,截图里也没有。
  • No AI tool as author or Co-authored-by. / 没有把 AI 工具写成作者或 Co-authored-by。

DSH 0.2.1-rc.2 is the newest release candidate, and DSH Desktop offers it
as an update. The unit tests, the smoke test and the UI checks pass on it
with the same results as on 0.2.0-rc.2, so the test harness, the install
commands and the bench checkout move to it.

npm still tags 0.2.0-rc.2 as latest, so one CI row stays on it in place of
the old 0.2.1-alpha.1 row. The Docker image and the desktop app keep their
own DSH pins: 0.2.1 refuses a wildcard bind address, which the image's
entrypoint uses, and the app's engine profile follows its own pull request.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T08:13:10.862148Z 173a439 Manual request
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5c6e116290

ℹ️ 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".

Comment thread README.md
```sh
npx @deepseek-ai/dsh@0.2.0-rc.2 plugin --profile web add ds-bot
npx @deepseek-ai/dsh@0.2.0-rc.2 web
npx @deepseek-ai/dsh@0.2.1-rc.2 plugin --profile web add ds-bot

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the DSH compatibility badges too

After these commands move Web users to 0.2.1-rc.2, the prominent DSH badge at README.md:12 (and its counterpart at README.zh.md:12) still advertises 0.2.0-rc.2. Readers using the badge as the current tested-version signal therefore receive contradictory guidance; update both badges as part of this version bump.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 173a439: both badges show 0.2.1-rc.2. I also merged dev into the branch (19ac631).

@Fei2411 Fei2411 mentioned this pull request Oct 19, 2026
10 tasks done
The install commands already name 0.2.1-rc.2, so the badges gave a different version.
@Fei2411

Fei2411 commented Oct 19, 2026

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 173a4391a7

ℹ️ 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".

@Fei2411
Fei2411 merged commit ee07140 into dev Oct 19, 2026
11 checks passed
@Fei2411
Fei2411 deleted the chore/dsh-0.2.1-rc.2 branch October 19, 2026 08:15

@rahul05ranjan rahul05ranjan left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The npm package exists (@deepseek-ai/dsh@0.2.1-rc.2 resolves), and the CI matrix + harness pin + docs all move together, which is the right shape for a "test and install against" bump.

One gap I hit while cross-checking: the Docker setup still installs 0.2.0-rc.2 while everything else moves to 0.2.1-rc.2. On this branch:

  • docker/Dockerfile:10 — ARG DSH_VERSION=0.2.0-rc.2
  • docker/compose.yml:8 — DSH_VERSION: ${DSH_VERSION:-0.2.0-rc.2}
  • docker/.env.example:41 — commented default still 0.2.0-rc.2
  • docker/README.md:168 — "The image is built and tested with dsh 0.2.0-rc.2"

Since the release checklist's smoke test ("Windows 10/11 x64 ... DSH Desktop, version matching the README") doesn't cover Docker, the README's "Install against 0.2.1-rc.2" claim would be silently wrong for everyone using the Docker path. Either bump these four in the same PR or note that Docker is deliberately staying one release behind.

(ds-bot/test/dsh-offer.test.js also has 0.2.0-rc.2 as a default fixture, but that's test data rather than a version pin, so no change needed there.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants