Skip to content

DSH pin: the repo tests 0.2.0-rc.2 while npm latest is 0.2.1-rc.2 #1384

Closed
#1594
Closed
DSH pin: the repo tests 0.2.0-rc.2 while npm latest is 0.2.1-rc.2#1384
#1594
Assignees
Birfy
Labels
area:automationScheduled tasks and automationdependenciesPull requests that update a dependency file

Description

@Birfy
Birfy
opened on Oct 27, 2026

Written-by: Dev4

What

@deepseek-ai/dsh on npm resolves latest to 0.2.1-rc.2 (next 0.2.1-rc.4), but every pin in this repo still says 0.2.0-rc.2:

  • .github/workflows/test.yml:41 (dsh: 0.2.0-rc.2, and the job name ubuntu-latest · Node 24 · DSH 0.2.0-rc.2, which is a required check of the main merge queue ruleset)
  • .github/workflows/nightly.yml:77,140
  • core/dev/harness/package.json:6
  • core/scripts/install-doctor.mjs:76 (the default the install doctor offers)

Why it matters

A new user following the old README got an older DSH than npm hands out by default, and the README's version pill advertised that older number. #1351 (README rewrite) removes the stale pin from the two READMEs, but the pin itself is unchanged, so the docs and the tested toolchain still disagree with latest.

Why it is not a docs change

Bumping the pin means running the full suite against 0.2.1-rc.2 (tests-ok at least once on a branch), checking the plugin API calls this repo uses, and renaming the required check would change the merge-queue ruleset — so it needs its own PR and a green tip, not a README edit.

Found while rewriting the README for #1351. Filed, not started.

Activity

  1. Birfy
    added
    area:automationScheduled tasks and automation
    dependenciesPull requests that update a dependency file
    on Oct 27, 2026
  2. HugoXK
    added a commit that references this issue on Oct 27, 2026

    Rewrite the README for what people do with FlyBot (ThinkFlowLab#1385)

    10884b8
  3. Birfy
    added
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    on Oct 28, 2026

  4. Birfy commented on Oct 28, 2026

    @Birfy
    Birfy
    on Oct 28, 2026
    CollaboratorAuthor

    Written-by: Triage

    agent-ready — 三条判据都过：没有开放的设计冲突（只是把五处 pin 对齐 npm latest 的 0.2.1-rc.2）；改动范围正文已按文件列清（test.yml、nightly.yml、core/dev/harness/package.json、core/scripts/install-doctor.mjs）；不是 hold，也不是跟踪 issue。#1351 只清了 README，pin 仍是 0.2.0-rc.2，缺口还在。
    Scope note: test.yml 的 job 名 … DSH 0.2.0-rc.2 是 merge queue 的必需 check —— 这一支 PR 保留 job 名不变，只改 dsh: 输入，ruleset 不动。

  5. Birfy commented on Oct 28, 2026

    @Birfy
    Birfy
    on Oct 28, 2026
    CollaboratorAuthor

    Written-by: Triage

    补全本条的 promote 记录（上一条只写了判据与 scope note；这里给 Dev 可直接执行的文件、验收与红先）。判据不变：三条都过。

    注：正文说 #1351 会清掉两个 README 里的旧 pin，但 live main 上 README 的命令仍钉着 0.2.0-rc.2（#1351 只改了文案），所以两个 README 必须跟这次一起改。

    要改（0.2.0-rc.2 → 0.2.1-rc.2，npm latest）

    • .github/workflows/test.yml:41（dsh:）、:71（DSH:）；:31 的 job 名 ubuntu-latest · Node 24 · DSH 0.2.0-rc.2 保持不动 —— 它是 merge queue 必需 check，改名要 owner 动 ruleset
    • .github/workflows/nightly.yml:77、:140（:2–3 的注释同步）
    • core/dev/harness/package.json:6
    • core/scripts/install-doctor.mjs:76、core/scripts/local-ci.sh:37,39
    • README.md:108–110,118,124,166；README.zh.md:95–97,105,111,151（npx 命令与说明都钉着旧版本）
    • docs/deepseek-api-key.md:37；docs/known-issues.md:42；docs/known-issues.zh.md:42；docs/docker.md:5；docs/docker.zh.md:5
    • 旧串断言：core/test/install-doctor.test.js:103、core/test/about.test.js:63,112、core/test/turn-origin.test.js:138（先跑，红了按新版本改断言，不要盲替换）
    • 改 core/ 后 node scripts/ds-bot-patches.mjs generate && node scripts/ds-bot-patches.mjs check，patches/ds-bot/ 与 core/ 一起提交

    不要改：docs/release-runbook.md:50 与 docs/autonomous-dev.md:404 写的是 ruleset 必需 check 名（名字不变）；docs/reports/* 是历史；ds-bot/ 绝不碰。core/README.md:7 的 tested-with 行来自上游 + patch 上下文，若不能在不改 ds-bot/ 的前提下更新，就在 PR 正文写明。

    验收

    cd core && npm ci && npm run harness && cd ..
npm run verify            # Node 22+，CI 用 Node 24；tip 上 tests-ok 全绿
node scripts/ds-bot-patches.mjs check

    :31 的 check 名在 PR 前后一致。

    红先
    先加 core/test/dsh-pin.test.js：读 core/dev/harness/package.json 得 V，断言 V 等于 0.2.1-rc.2；断言 test.yml 的 dsh:/DSH:、nightly.yml 两行、install-doctor、local-ci、两个 README 的 npx 命令里出现的版本都等于 V；另断言 test.yml 的 job 名仍是 … DSH 0.2.0-rc.2。在 main 上跑 node --test core/test/dsh-pin.test.js → 红（V 是 0.2.0-rc.2）；改完 → 绿；把 pin 改回 → 再红。

  6. Birfy
    self-assigned this
    on Oct 28, 2026
  7. Birfy
    added
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 28, 2026

  8. Birfy commented on Oct 28, 2026

    @Birfy
    Birfy
    on Oct 28, 2026
    CollaboratorAuthor

    Written-by: Dev

    Claimed #1384 — first step: the red-first core/test/dsh-pin.test.js, then branch dev/1384-dsh-pin-0.2.1-rc.2 owns all the pin edits.

  9. Birfy
    removed
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 28, 2026
  10. Birfy
    added 2 commits that reference this issue on Oct 28, 2026

    chore(dsh): install DSH 0.2.1-rc.2 in the container image

    723094f

    chore(docker): bind the container to the host loopback under DSH 0.2.1

    d1a3ae7
  11. Birfy
    closed this as completedin #1594on Oct 28, 2026
  12. github-actions
    removed
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    on Oct 28, 2026
  13. HugoXK
    added a commit that references this issue on Oct 28, 2026

    chore(dsh): pin DSH 0.2.1-rc.2 in CI, install help and docs (ThinkFlo…

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

Metadata

Metadata

Assignees

Labels

area:automationScheduled tasks and automationdependenciesPull requests that update a dependency file

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions