Repository navigation
Releases
v0.4.2
dsh-update-safe 0.4.1
包名、仓库名和 bundle 行统一为 dsh-update-safe。0.4.0 用过的 dsh-update-plugin 在 npm 上是个没有版本、没有维护者的占位（发布会被拒），dsh-update-safe 是空的，所以 0.4.1 换过来。
- 内部配置 id
safe-release-update、RPC 路由、监督进程锁和~/.local/share/dsh-safe-release-update数据目录不变，设置、快照和更新记录保留。 - 0.4.0 只在 GitHub 上存在过，npm 上从未发布过本插件的任何版本。
- 旧 profile 迁移：先
pnpm dsh plugin --profile web remove dsh-update-plugin（更早的是dsh-upgrade），再按下式安装。
源码目录安装：
pnpm dsh plugin --profile web add https://github.com/zudazhuang/dsh-update-safe/releases/download/v0.4.1/dsh-update-safe-0.4.1.tgz附件校验（SHA-256）：
2457e7b3b398ee495bd85ba2d2f4eef4ac54746a7427d0e5e4b160c9a57bb264 dsh-update-safe-0.4.1.tgz
验证：21 项测试通过；干净 profile 安装后 --dump-config 出现 dsh-update-safe 层。npm 发布待账号 2FA 凭据。
已发布到 npm：dsh-update-safe@0.4.1（pnpm dsh plugin --profile web add dsh-update-safe@0.4.1），与附件内容一致。
dsh-update-plugin 0.4.0
包名、仓库名和 bundle 行统一改为 dsh-update-plugin：npm 上的 dsh-upgrade 属于另一位作者的另一个插件，同名发不出去，继续用旧名只会让人装错。
- 内部配置 id
safe-release-update、RPC 路由、监督进程锁和~/.local/share/dsh-safe-release-update数据目录不变，设置与更新记录保留。 - 安装说明改为固定 Release 附件地址；profile 记录 URL 后，移动或删除本地 tgz 不会再导致重装失败。
- 旧 profile 迁移：先
pnpm dsh plugin --profile web remove dsh-upgrade，再按下式安装。
源码目录安装：
pnpm dsh plugin --profile web add https://github.com/zudazhuang/dsh-update-plugin/releases/download/v0.4.0/dsh-update-plugin-0.4.0.tgz附件校验（SHA-256）：
bf3955ab57890b3fc9c5edc77bf1b00d010208744dfa86f8888cc0bed3efbfd6 dsh-update-plugin-0.4.0.tgz
验证：21 项测试通过；在全新 DSH_HOME 的临时 profile 里用上面的地址安装，--dump-config 出现 dsh-update-plugin 层。未发布到 npm；未在真实用户数据上执行跨版本切换。
dsh-upgrade 0.3.8
修复实际慢速网络下反复准备失败的问题：
- 官方版本元数据使用压缩 HTTPS 请求，有限重试。
- 源码下载时限可配置，默认 3600 秒；连接时限 20 秒。
- 完整且版本校验通过的源码归档保存 SHA-256 缓存，再次准备时校验后复用；损坏缓存重新下载。
验证：21 项测试和 GitHub CI 通过。本机通过真实插件 RPC 完成 rc.2 准备，包含本地修改迁移、完整构建、实际 Web profile 副本启动和版本健康检查，页面显示“新版已准备”并启用“安装并重启”。本次复用了前次从官方完整下载并验证的归档；当前慢速链路未重新完整下载 33 MB 归档。
生产 Harness 保持 0.2.1-alpha.4，未执行安装切换。此前隔离环境已验证真实安装重启流程。第三方插件的全部业务功能未逐项验证。
下载附件 tgz，通过 Harness 插件管理安装。此版本未发布到 npm。
附件校验（SHA-256）：
2dcb5ada93aafc11f2c9de08abf4e4474d1b58ed5219a559752ef778586ee6bc dsh-upgrade-0.3.8.tgz
dsh-upgrade 0.3.5
修复官方源码下载超时、准备失败后无法重试，以及多实例共享状态覆盖问题。
改用官方 HTTPS 标签归档下载，保留本地修改迁移、隔离构建和监督进程安装恢复流程。需要 curl 与 tar。
验证：19 项测试通过；隔离实例通过真实 RPC 执行安装并重启，从 0.2.1-alpha.2 切换至 0.2.1-rc.2，事务 completed，健康检查通过。本机生产 Harness 保持原版本，只安装了插件修复。
下载附件 tgz，通过 Harness 插件管理安装。此版本未发布到 npm。
dsh-upgrade 0.3.4
The updater now snapshots and migrates uncommitted working edits and non-ignored new files, without changing the user's branch or normal Git index. Prepared candidates are invalidated if working files change before handoff. Dependency settings migrate and the candidate lockfile is rebuilt; source conflicts list the affected files and stop safely.
18 tests passed. The full preparation flow was also exercised from a 0.2.1-alpha.1 checkout with an untracked custom file to 0.2.1-alpha.2: dependency resolution, complete build, copied-profile startup and authenticated health verification all passed. The GitHub download timed out in that run; the build/migration validation used the previously verified local official tag cache. No real update switch was executed in this validation.
Install dsh-upgrade-0.3.4.tgz with pnpm dsh plugin --profile web add /absolute/path/dsh-upgrade-0.3.4.tgz. npm publication remains pending account login.
dsh-upgrade 0.3.3
Local dependency migrations now replay manifest and workspace settings, omit the old pnpm lockfile, and regenerate the candidate lockfile when dependency configuration changes. Source conflicts still stop without modifying the original installation. Builds and profile startup are validated before handoff. Existing project folder names are unchanged; isolated candidates stay in updater storage.
18 tests pass. Download the attached dsh-upgrade-0.3.3.tgz and install with pnpm dsh plugin --profile web add /absolute/path/dsh-upgrade-0.3.3.tgz. npm publication remains pending account login.
dsh-upgrade 0.3.2
Preserve committed local source changes during isolated upgrades. The updater creates a private patch relative to the current official tag and applies it to the candidate using Git three-way merging. Conflicts stop preparation without changing the original installation. Uncommitted changes remain blocked.
18 keyless tests pass, including successful custom-file migration and conflict rejection. Tested with a built Harness 0.2.1-alpha.2 installation and a copied profile. This does not publish private installation commits.
Install the attached dsh-upgrade-0.3.2.tgz using pnpm dsh plugin --profile web add /absolute/path/dsh-upgrade-0.3.2.tgz. npm publication remains pending login.
dsh-upgrade 0.3.1
Rename the community update plugin and repository to dsh-upgrade. The previous unscoped npm name dsh-update is owned by another author. npm publication is pending account login; this release is installable from its attached tarball.
Download dsh-upgrade-0.3.1.tgz, then run from your Harness source checkout:
pnpm dsh plugin --profile web add /absolute/path/dsh-upgrade-0.3.1.tgzExisting configuration IDs, update records, backups and login job remain compatible. Do not enable both the old and new bundle. Supports source Web installations; tested with Harness 0.2.1-alpha.1. All 17 keyless tests pass. See README for startup, scheduled installation and recovery requirements.
dsh-update 0.3.0
dsh-update is a community plugin for DeepSeek Harness source Web installations. This is the first public release, renamed from the local dsh-safe-release-update package.
Features:
- Official GitHub and npm release checks at startup, on demand, and at configurable intervals.
- Idle daily installation windows, isolated builds, supervised switching and data snapshot recovery.
- Optional macOS login startup and a ConfigForms settings page.
Installation: download dsh-update-0.3.0.tgz, then run pnpm dsh plugin --profile web add /absolute/path/dsh-update-0.3.0.tgz from your Harness source checkout.
Tested locally with Harness 0.2.1-alpha.1: 17 keyless tests and browser checks. A real future-version switch has not been exercised with live user data. Uncommitted source changes block installation. Power-loss recovery requires manual review. See README for requirements and migration instructions.