@wenbin_wb/dsh-bridge 2.0.2 → 2.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -0
- package/README.zh-CN.md +10 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -95,6 +95,16 @@ dsh plugin --profile web add @wenbin_wb/dsh-bridge@latest
|
|
|
95
95
|
|
|
96
96
|
> **Note**: `update --latest` may fail to reach the newest major version due to version constraints from already-installed dependencies. Use the `add @latest` command above to force-install the latest version (no need to know the exact version number).
|
|
97
97
|
|
|
98
|
+
#### Still on an old version after upgrading? (pnpm 11 new-version filtering)
|
|
99
|
+
|
|
100
|
+
If you upgrade right after a release, `add @latest` may still install an older version. This is caused by **pnpm 11's supply-chain safety mechanism `minimumReleaseAge`** (default: filters versions published less than 24 hours ago) — not a plugin issue.
|
|
101
|
+
|
|
102
|
+
**Solutions** (pick one):
|
|
103
|
+
|
|
104
|
+
1. **Add `minimumReleaseAge: 0` to your profile's `pnpm-workspace.yaml`**, then run `pnpm install` (recommended, permanent)
|
|
105
|
+
2. **Specify the exact version**: `dsh plugin --profile web add @wenbin_wb/dsh-bridge@2.0.2` (works immediately, no waiting)
|
|
106
|
+
3. **Wait 24 hours**: the protection lifts automatically after 1 day
|
|
107
|
+
|
|
98
108
|
After upgrading, restart DSH and **hard-refresh** the browser (Windows: `Ctrl+Shift+R`, macOS: `Cmd+Shift+R`) to clear the cache, then confirm the latest version is shown in settings.
|
|
99
109
|
|
|
100
110
|
---
|
package/README.zh-CN.md
CHANGED
|
@@ -95,6 +95,16 @@ dsh plugin --profile web add @wenbin_wb/dsh-bridge@latest
|
|
|
95
95
|
|
|
96
96
|
> **注意**：`update --latest` 可能因已安装依赖的版本约束而无法升级到最新版。用上面的 `add @latest` 命令即可强制安装最新版（无需知道具体版本号）。
|
|
97
97
|
|
|
98
|
+
#### 升级后仍是旧版本？（pnpm 11 新版本过滤）
|
|
99
|
+
|
|
100
|
+
如果你刚发布后立即升级，`add @latest` 可能仍然装到旧版本。这是 **pnpm 11 的供应链安全机制 `minimumReleaseAge`**（默认过滤发布不足 24 小时的新版本）导致的，不是插件问题。
|
|
101
|
+
|
|
102
|
+
**解决方法**（任选其一）：
|
|
103
|
+
|
|
104
|
+
1. **在 profile 的 `pnpm-workspace.yaml` 添加 `minimumReleaseAge: 0`**，然后重新 `pnpm install`（推荐，一劳永逸）
|
|
105
|
+
2. **显式指定版本号**：`dsh plugin --profile web add @wenbin_wb/dsh-bridge@2.0.2`（立即生效，无需等待）
|
|
106
|
+
3. **等待 24 小时**：发布满 1 天后保护自动解除
|
|
107
|
+
|
|
98
108
|
升级完成后重启 DSH，并在浏览器**硬刷新**（Windows: `Ctrl+Shift+R`，macOS: `Cmd+Shift+R`）清除缓存，然后确认设置页显示最新版本号。
|
|
99
109
|
|
|
100
110
|
---
|
package/package.json
CHANGED