dsh-quick-actions 0.2.0-rc.3 → 0.2.0

package/README.en.md

@@ -20,7 +20,7 @@ This release has **no insert action** (insert at the selection, keep the editing
 
 | Item | Value |
 |---|---|
-| Verified baseline | DSH core packages at `0.1.7-rc.1`. Note that `dsh --version` on the desktop build prints its dependency-set label, a different number from the core package version |
+| Verified baseline | DSH core packages at `0.1.7-rc.1`; the live GUI was additionally accepted on `0.1.7-rc.2`. Note that `dsh --version` on the desktop build prints its dependency-set label, a different number from the core package version |
 | DSH peers | `>=0.1.7-alpha.2` |
 | Cordis | `^4.0.4` |
 | Schemastery | `^3.18.4` |
@@ -28,7 +28,7 @@ This release has **no insert action** (insert at the selection, keep the editing
 | DSH UI primitives (browser side) | `>=0.1.7-alpha.2`, also supplied by the module table |
 | Platform | `web` profile only |
 
-The send and Settings contracts have no legacy compatibility layer. **`0.2.0-rc.3`** also supports the optional `conversation.composer.footer`: a locally patched core places the bar below the statistics row, with the action group centered within the input's width; an unpatched core keeps the existing placement. Official `0.1.7-rc.2` does not include this slot, and installing the plugin alone does not add it.
+The send and Settings contracts have no legacy compatibility layer. **`0.2.0`** also supports the optional `conversation.composer.footer`: a locally patched core places the bar below the statistics row, with the action group centered within the input's width; an unpatched core keeps the existing placement. Official `0.1.7-rc.2` does not include this slot, and installing the plugin alone does not add it.
 
 The floor is the DSH release whose Settings form this plugin reads. **Do not run it against anything older**: `0.1.7-alpha.1` rewrote Settings — plugins no longer register namespaces of their own, and user data became the plugin's own Config, written into the profile. This release reads and writes the new model only, and on the `0.1.5` and `0.1.6` lines its Client never starts. For those lines, install this plugin's `0.1.0`.
 
@@ -42,10 +42,12 @@ No upper bound is declared, but **that is not a promise of forward compatibility
 ## Install
 
 ```sh
-dsh plugin --profile web add dsh-quick-actions@next
+dsh plugin --profile web add dsh-quick-actions --config.minimumReleaseAge=0
 ```
 
-**Keep the `@next`.** The plugin's `0.2.0` line remains a prerelease and uses the `next` dist-tag. Without the tag you get the plugin's `0.1.0` from `latest`, which supports only DSH `0.1.5` and `0.1.6` and fails to activate on `0.1.7`. DSH's own `latest` is now `0.1.7-rc.2`, but that does not automatically change this plugin's release channel. This release has not been verified against the DSH `0.2.0` prerelease line.
+**`0.2.0` has replaced `0.1.0` as `latest`.** It supports the DSH `0.1.7` line only (floor `>=0.1.7-alpha.2`); users still on the `0.1.5`/`0.1.6` lines should stay on `0.1.0` and not upgrade.
+
+The `--config.minimumReleaseAge=0` above is needed only during the first 24 hours after a publish; drop it afterwards. pnpm refuses dependencies published inside a 24-hour cooldown window, and for such a version it **does not error — it silently falls back to an older qualifying release**, which here means `0.1.0`: a version that supports only the `0.1.5`/`0.1.6` lines and fails to activate on `0.1.7`. If you do end up with `0.1.0`, run `dsh plugin --profile web remove dsh-quick-actions` and install again with the flag.
 
 Then restart the web profile. One package is the whole thing: it carries `dsh.bundle.patch`, which inserts its Host half into the profile, while its `dsh.client` declaration makes the web app load the browser half.
 
@@ -54,7 +56,7 @@ Then restart the web profile. One package is the whole thing: it carries `dsh.bu
 ```sh
 mkdir -p /tmp/quick-actions
 pnpm --filter dsh-quick-actions pack --pack-destination /tmp/quick-actions
-dsh plugin --profile web add /tmp/quick-actions/dsh-quick-actions-0.2.0-rc.3.tgz
+dsh plugin --profile web add /tmp/quick-actions/dsh-quick-actions-0.2.0.tgz
 ```
 
 The `--filter` form works from anywhere in the repository; from the package directory itself, `pnpm pack --pack-destination /tmp/quick-actions` is the same thing.

package/README.md

@@ -20,7 +20,7 @@
 
 | 项目 | 值 |
 |---|---|
-| 验证基线 | DSH 核心包 `0.1.7-rc.1`。桌面端 `dsh --version` 打印的是依赖集标签，与核心包版本不是同一个数字 |
+| 验证基线 | DSH 核心包 `0.1.7-rc.1`；真实 GUI 另在 `0.1.7-rc.2` 上验收。桌面端 `dsh --version` 打印的是依赖集标签，与核心包版本不是同一个数字 |
 | DSH peer | `>=0.1.7-alpha.2` |
 | Cordis | `^4.0.4` |
 | Schemastery | `^3.18.4` |
@@ -28,7 +28,7 @@
 | DSH UI primitives（浏览器侧） | `>=0.1.7-alpha.2`，同样由模块表提供 |
 | 平台 | 只支持 `web` profile |
 
-发送与 Settings 契约不做旧版兼容。**`0.2.0-rc.3`** 另支持可选的 `conversation.composer.footer`：带本地核心补丁的 DSH 将 bar 放到统计行下方、动作组水平居中；未打补丁的核心保留原位置。该挂载点不是官方 `0.1.7-rc.2` 自带能力，也不会仅因安装插件而出现。
+发送与 Settings 契约不做旧版兼容。**`0.2.0`** 另支持可选的 `conversation.composer.footer`：带本地核心补丁的 DSH 将 bar 放到统计行下方、动作组水平居中；未打补丁的核心保留原位置。该挂载点不是官方 `0.1.7-rc.2` 自带能力，也不会仅因安装插件而出现。
 
 下界取的是本插件读取其 Settings 表单的那个 DSH 版本。**不要在更低版本上使用**：`0.1.7-alpha.1` 重写了 Settings——插件不再自己注册命名空间，用户数据改为插件自己的 Config、写进 profile。本版只按新模型读写，在 `0.1.5`、`0.1.6` 线上 Client 根本不会启动。要在那两条线上用，请装本插件的 `0.1.0`。
 
@@ -42,10 +42,12 @@
 ## 安装
 
 ```sh
-dsh plugin --profile web add dsh-quick-actions@next
+dsh plugin --profile web add dsh-quick-actions --config.minimumReleaseAge=0
 ```
 
-**`@next` 不能省。** 插件 `0.2.0` 仍处于预发布阶段，本版使用 `next` dist-tag；不带 tag 装到的是插件 `latest` 上的 `0.1.0`，它只支持 DSH `0.1.5`、`0.1.6` 线，在 `0.1.7` 上激活失败。DSH 的 `latest` 已是 `0.1.7-rc.2`，但这不会自动改变插件的发布通道。本版尚未验证 DSH `0.2.0` 预发布线。
+**`0.2.0` 已取代 `0.1.0` 成为 `latest`。** 它只支持 DSH `0.1.7` 线（下界 `>=0.1.7-alpha.2`）；仍在 `0.1.5`／`0.1.6` 线上的用户请继续使用 `0.1.0`，不要升级。
+
+上面那条 `--config.minimumReleaseAge=0` 在刚发布的头 24 小时内需要，之后可以去掉。pnpm 默认拒绝发布时间在 24 小时冷却窗口内的依赖，而它在遇到这种版本时**不报错，而是静默退回更旧的合格版本**——也就是只支持 `0.1.5`／`0.1.6` 线、在 `0.1.7` 上激活失败的 `0.1.0`。万一装成了 `0.1.0`，先 `dsh plugin --profile web remove dsh-quick-actions`，再带这个标志重装。
 
 然后重启 web profile。一个包就是全部：它自带 `dsh.bundle.patch` 把自己的 Host 半边插进 profile，`dsh.client` 声明让 web 端加载浏览器半边。
 
@@ -54,7 +56,7 @@ dsh plugin --profile web add dsh-quick-actions@next
 ```sh
 mkdir -p /tmp/quick-actions
 pnpm --filter dsh-quick-actions pack --pack-destination /tmp/quick-actions
-dsh plugin --profile web add /tmp/quick-actions/dsh-quick-actions-0.2.0-rc.3.tgz
+dsh plugin --profile web add /tmp/quick-actions/dsh-quick-actions-0.2.0.tgz
 ```
 
 上面的 `--filter` 形式在仓库任意位置都能用；如果你已经在包目录里，`pnpm pack --pack-destination /tmp/quick-actions` 即可。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-quick-actions",
-  "version": "0.2.0-rc.3",
+  "version": "0.2.0",
   "description": "Persistent Quick Actions for the DSH message composer",
   "license": "MIT",
   "repository": {