dsh-context-domains 0.3.0 → 0.3.1
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/docs/PUBLISH.md +11 -1
- package/package.json +1 -1
package/docs/PUBLISH.md
CHANGED
|
@@ -80,7 +80,17 @@ npm publish --access public --registry=https://registry.npmjs.org --otp=123456
|
|
|
80
80
|
- 标签必须是 `v<version>`，否则 release workflow 直接失败；
|
|
81
81
|
- npm 不允许覆盖已发布版本：改代码后必须 bump version 才能再发。
|
|
82
82
|
|
|
83
|
-
## 5.
|
|
83
|
+
## 5. 两个 registry 的坑（本仓库都踩过）
|
|
84
|
+
|
|
85
|
+
**发布成功 ≠ 立刻可查。** 第一次发布时 CI 打完 `npm publish` 立刻 `npm view`，
|
|
86
|
+
拿到 404 就把整条发布判成失败——其实版本两分钟后就在了。所以 `release.yml` 里
|
|
87
|
+
那步现在是「已存在就跳过，不存在才发，发完轮询 registry」，rerun 也安全。
|
|
88
|
+
|
|
89
|
+
**包名会先出现一个 `0.0.0-stage`。** 首次发布一个新包时，npm 会先用这个占位版本
|
|
90
|
+
建出包，再放真正的版本（`dsh-archify-projects` 也是这样）。它是正常的，
|
|
91
|
+
`dist-tags.latest` 指向真实版本后就不用管它。
|
|
92
|
+
|
|
93
|
+
## 6. 常见错误
|
|
84
94
|
|
|
85
95
|
| 报错 | 原因 | 处理 |
|
|
86
96
|
| --------------------------------------------------------------- | ------------- | ---------------------------------------------- |
|