dsh-up-session 1.0.0 → 1.0.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # 更新日志
 
+## 1.0.1 - 2026-10-24
+
+### 修复
+
+- 兼容 DSH 0.2.1-rc.3
+
 ## 1.0.0 - 2026-10-22
 
 ### 新增

package/README.en.md

@@ -15,7 +15,7 @@ A simple DeepSeek Harness sidebar plugin: it inserts two sections, "Pinned" and
 
 ## Installation and compatibility
 
-Currently supports DSH `0.2.1-rc.2`.
+The DSH compatibility range is `>=0.2.1-rc.3`, allowing RC.3 and later versions to install; functionality still needs to be verified against the DSH version in use.
 
 **Web**
 
@@ -65,6 +65,20 @@ Rows in both sections read the same live status as the sidebar's own session row
 
 The marker sits at the left of the title and appears only when there is something to report, so an idle row keeps its original left edge; the archive and pin buttons still appear on hover where they always did.
 
+## Publishing
+
+Publishing a GitHub Release triggers the [publishing workflow](./.github/workflows/publish.yml), which publishes the package at that tag to npm. The tag must match the version in `package.json`, for example `v1.0.1` or `1.0.1`. Stable versions use the npm `latest` tag; prerelease versions use `next` and must also be marked as prereleases on GitHub. Saving a draft or pushing a tag alone does not trigger publishing.
+
+Before the first automated release, add a GitHub Actions trusted publisher in the npm settings for `dsh-up-session` ([official npm instructions](https://docs.npmjs.com/trusted-publishers/)):
+
+- Organization or user: `kyrsieger`
+- Repository: `dsh-up-session`
+- Workflow filename: `publish.yml`
+- Environment name: leave blank
+- Allowed actions: allow direct publishing with `npm publish`
+
+The workflow authenticates through OIDC, so no `NPM_TOKEN` is needed. Commit and push the workflow, version number, and changelog first, then create a tag for that commit and publish its Release. If publishing fails, rerun the failed job in GitHub Actions; npm versions that have already been published successfully cannot be published again.
+
 ## License
 
 This project is licensed under the [MIT License](./LICENSE).

package/README.md

@@ -15,7 +15,7 @@
 
 ## 安装与兼容
 
-当前支持 DSH `0.2.1-rc.2` 版本。
+DSH 兼容版本声明为 `>=0.2.1-rc.3`，允许 RC.3 及后续版本安装；具体功能仍需与所用 DSH 版本验证。
 
 **Web 端**
 
@@ -65,6 +65,20 @@ dsh plugin --profile web add dsh-up-session
 
 状态标记插在标题左侧，只在需要提示时才出现，空闲的行保持原本的左边缘；归档、置顶等操作按钮在悬停时出现的位置不受影响。
 
+## 发布
+
+发布 GitHub Release 后，[发布工作流](./.github/workflows/publish.yml) 会自动将该 tag 对应的包发布到 npm。tag 必须与 `package.json` 的版本一致，例如 `v1.0.1` 或 `1.0.1`。正式版使用 npm 的 `latest` 标签；预发布版使用 `next`，且 GitHub Release 必须标记为预发布。仅保存草稿或推送 tag 不会触发发布。
+
+首次使用前，在 npm 的 `dsh-up-session` 包设置中添加 GitHub Actions 可信发布者（[npm 官方说明](https://docs.npmjs.com/trusted-publishers/)）：
+
+- Organization or user：`kyrsieger`
+- Repository：`dsh-up-session`
+- Workflow filename：`publish.yml`
+- Environment name：留空
+- Allowed actions：允许直接执行 `npm publish`
+
+工作流使用 OIDC 认证，无需配置 `NPM_TOKEN`。先将工作流、版本号和更新日志提交并推送，再为该提交创建 tag 和发布 Release。发布失败时，可在 GitHub Actions 中重跑失败的任务；已成功发布的 npm 版本不能重复发布。
+
 ## 许可
 
 本项目基于 [MIT 许可证](./LICENSE) 授权。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-up-session",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "type": "module",
   "description": "Adds pinned and recent session sections above the workspace list in the DSH sidebar, with a small settings popup.",
   "license": "MIT",
@@ -42,7 +42,7 @@
     "CHANGELOG.md"
   ],
   "engines": {
-    "dsh": "0.2.1-rc.2"
+    "dsh": ">=0.2.1-rc.3"
   },
   "dsh": {
     "bundle": {