@yiliang114/dsh-session-deck 0.1.3 → 0.1.4

package/README.md

@@ -85,7 +85,7 @@ https://raw.githubusercontent.com/yiliang114/dsh-session-deck/main/market-index.
 
 This is a **user-added custom market source**, not an official DSH listing. Publishing to npm does not automatically add the plugin to an official DSH market.
 
-Maintainers: the intended automatic release process queues pushes to `main`, tests the latest `main` after acquiring the release queue, and increments the patch version (for example, `0.1.2` → `0.1.3`). To choose a minor version, run `npm version minor --no-git-tag-version`, then commit and push to `main` normally: an explicit greater stable version such as `0.2.0` is preserved, and the following release becomes `0.2.1`. The workflow owns tags, publication with provenance, registry verification, market updates, and GitHub Releases. See the [release guide](https://github.com/yiliang114/dsh-session-deck/blob/main/docs/releasing.md) for authentication prerequisites and recovery; this description is not evidence that the new automation has been verified.
+Maintainers: pushing to `main` queues an automatic patch release (for example, `0.1.2` → `0.1.3`). Rapid pushes can be combined: stale queued runs skip, and the latest eligible run includes the accumulated changes. To choose a minor version, run `npm version minor --no-git-tag-version`, then commit and push normally; an explicit greater stable version such as `0.2.0` is preserved, and the following release becomes `0.2.1`. The workflow runs verification, creates the version commit and tag, publishes with provenance, and updates the market index and GitHub Release. See the [release guide](https://github.com/yiliang114/dsh-session-deck/blob/main/docs/releasing.md) for authentication prerequisites and recovery.
 
 ## How session status works
 

package/README.zh-CN.md

@@ -85,7 +85,7 @@ https://raw.githubusercontent.com/yiliang114/dsh-session-deck/main/market-index.
 
 这是**用户自行添加的自定义市场源**，并非 DSH 官方收录。发布 npm 不会自动将插件加入官方 DSH 市场。
 
-维护者：预期的自动发布流程会将 `main` 推送加入发布队列，取得队列执行权后测试最新的 `main`，并递增补丁版本（例如 `0.1.2` → `0.1.3`）。需要手动选择次版本时，执行 `npm version minor --no-git-tag-version`，再正常提交并推送到 `main`：显式指定的更高稳定版本（例如 `0.2.0`）会保留，下一次发布则为 `0.2.1`。工作流负责标签、带 provenance 的发布、注册表验证、市场索引更新和 GitHub Release。认证前提与失败恢复请参阅[发布指南（英文）](https://github.com/yiliang114/dsh-session-deck/blob/main/docs/releasing.md)；此流程说明不代表新自动化已经验证完成。
+维护者：推送到 `main` 会自动排队发布补丁版本（例如 `0.1.2` → `0.1.3`）。连续快速推送可能合并处理：过时的排队任务跳过，最新可执行任务包含累计改动。需要手动选择次版本时，执行 `npm version minor --no-git-tag-version`，再正常提交并推送；显式指定的更高稳定版本（例如 `0.2.0`）会保留，下一次发布为 `0.2.1`。工作流负责验证、版本提交和标签、带 provenance 的发布、市场索引更新和 GitHub Release。认证前提与失败恢复请参阅[发布指南（英文）](https://github.com/yiliang114/dsh-session-deck/blob/main/docs/releasing.md)。
 
 ## 会话状态与边界
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yiliang114/dsh-session-deck",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "license": "MIT",
   "author": "yiliang114",
   "publishConfig": {