cross-tab-worker-databus 0.20.7 → 0.20.8
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/CHANGELOG.md +7 -0
- package/docs/release-checklist.md +1 -1
- package/docs/roadmap.md +6 -1
- package/docs/zh/release-checklist.md +1 -1
- package/docs/zh/roadmap.md +6 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,13 @@
|
|
|
2
2
|
|
|
3
3
|
本项目遵循 [Semantic Versioning](https://semver.org/)；变更记录格式参考 [Keep a Changelog](https://keepachangelog.com/)。
|
|
4
4
|
|
|
5
|
+
## [0.20.8] - 2026-09-02
|
|
6
|
+
|
|
7
|
+
### Added
|
|
8
|
+
|
|
9
|
+
- Release verification now retries npm tarball resolution to tolerate registry propagation after publication.
|
|
10
|
+
- The release workflow always verifies the exact tagged package's ESM and CommonJS consumers after the publish-or-skip step.
|
|
11
|
+
|
|
5
12
|
## [0.20.7] - 2026-09-02
|
|
6
13
|
|
|
7
14
|
### Added
|
|
@@ -19,4 +19,4 @@ Run `npm publish --access public` from the tagged checkout. A version already pr
|
|
|
19
19
|
2. Install the published tarball or version in a clean consumer and import the root plus every public subpath.
|
|
20
20
|
3. Record the result in the release notes. Do not advance to `1.0.0` until the public API and protocol deprecation policy are explicitly frozen.
|
|
21
21
|
|
|
22
|
-
Run `PUBLISHED_VERSION=0.20.
|
|
22
|
+
Run `PUBLISHED_VERSION=0.20.8 pnpm verify:published` after npm publication. The verifier retries while the registry propagates the tarball; tune `PUBLISHED_VERIFY_ATTEMPTS` and `PUBLISHED_VERIFY_DELAY_MS` only for unusually slow mirrors.
|
package/docs/roadmap.md
CHANGED
|
@@ -1,6 +1,11 @@
|
|
|
1
1
|
# Roadmap
|
|
2
2
|
|
|
3
|
-
0.20.
|
|
3
|
+
0.20.8 is the current development line. The project is intentionally continuing through reliability-focused minor releases before a 1.0.0 stability freeze.
|
|
4
|
+
|
|
5
|
+
## 0.20.8 delivered scope
|
|
6
|
+
|
|
7
|
+
- Release verification retries npm tarball resolution during registry propagation and validates the exact tagged version after publish or skip.
|
|
8
|
+
- GitHub Release now runs the same ESM/CJS published-consumer check used locally, including manually published releases.
|
|
4
9
|
|
|
5
10
|
## 0.20.7 delivered scope
|
|
6
11
|
|
|
@@ -19,4 +19,4 @@
|
|
|
19
19
|
2. 在干净消费者中安装已发布版本或 tarball，并导入主入口及所有公开子路径。
|
|
20
20
|
3. 将结果记录到发布说明。在公开 API 和协议弃用策略明确冻结前，不进入 `1.0.0`。
|
|
21
21
|
|
|
22
|
-
npm 发布后运行 `PUBLISHED_VERSION=0.20.
|
|
22
|
+
npm 发布后运行 `PUBLISHED_VERSION=0.20.8 pnpm verify:published`。验证器会在 registry 传播 tarball 时自动重试；只有遇到异常慢的镜像才需要调整 `PUBLISHED_VERIFY_ATTEMPTS` 和 `PUBLISHED_VERIFY_DELAY_MS`。
|
package/docs/zh/roadmap.md
CHANGED
|
@@ -1,6 +1,11 @@
|
|
|
1
1
|
# 路线图
|
|
2
2
|
|
|
3
|
-
0.20.
|
|
3
|
+
0.20.8 正在推进。项目会先持续完成可靠性与协议兼容性的中版本迭代，再进入 1.0.0 稳定性冻结。
|
|
4
|
+
|
|
5
|
+
## 0.20.8 已完成范围
|
|
6
|
+
|
|
7
|
+
- 发布后验证会在 npm registry 传播期间轮询 tarball，降低刚发布时的误报失败。
|
|
8
|
+
- GitHub Release 在发布或跳过发布后，都会验证当前 tag 对应版本的 ESM/CJS 消费者；手动 npm 发布也适用。
|
|
4
9
|
|
|
5
10
|
## 0.20.7 已完成范围
|
|
6
11
|
|
package/package.json
CHANGED