@stalfh233/omc-cli 0.4.0 → 0.4.10

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.
Files changed (2) hide show
  1. package/README.md +11 -22
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -244,42 +244,31 @@ src/ args/support/plan/read/write/package/context(治理管道)
244
244
  | `omc-acceptance-criteria` | 验收门:读回、交付态、零残留、反例基线 |
245
245
  | `omc-glossary` | 术语:环境指纹、覆盖清单、交付态、Void envelope、结果状态 |
246
246
 
247
- ## GitLab npm Package Registry 分发
247
+ ## npm 分发
248
248
 
249
- 本包通过项目级 GitLab npm Registry 分发。`omc-core` 是 `omc-cli` 的内部依赖,发布流水线会先发布 `omc-core`,再发布 `omc-cli`;两者版本保持一致。当前版本为 `0.3.0`,尚未宣称 `1.0.0` 稳定契约。
249
+ 本包(`@stalfh233/omc-cli`,可执行命令仍是 `omc`)通过公共 npm registry 分发。`omc-core` 是 `omc-cli` 的内部依赖,发布时先发 `omc-core`,再发 `omc-cli`;两者版本保持一致。当前版本为 `0.4.10`,尚未宣称 `1.0.0` 稳定契约。
250
250
 
251
251
  ### 使用已发布包
252
252
 
253
- 先从 GitLab 项目概览页取得 `<PROJECT_ID>`,再在使用方项目目录创建本地 `.npmrc`。不要把 token 写入仓库:
254
-
255
- ```ini
256
- registry=https://gitlab.h3yun.com/api/v4/projects/<PROJECT_ID>/packages/npm/
257
- //gitlab.h3yun.com/api/v4/projects/<PROJECT_ID>/packages/npm/:_authToken=${NPM_TOKEN}
258
- ```
259
-
260
- `NPM_TOKEN` 使用具有 `read_package_registry` 的 Deploy Token,或 GitLab 推荐的其他 npm Registry token。然后安装:
261
-
262
253
  ```bash
263
- npm install omc-cli@0.3.0
264
- npx omc setup
265
- npx omc doctor
266
- npx omc help omc-write-hazards
267
- npx omc help omc-business-configuration
254
+ npm install -g @stalfh233/omc-cli@0.4.10
255
+ omc setup
256
+ omc doctor
257
+ omc help omc-write-hazards
258
+ omc help omc-business-configuration
268
259
  ```
269
260
 
270
- 如果组织使用 group/instance Registry,可把 `.npmrc` 的 project endpoint 换成对应 group/instance endpoint;token 必须有目标包及其 `omc-core` 依赖的读取权限。
271
-
272
261
  ### 发布新版本
273
262
 
274
- 发布由 GitLab CI 的 tag pipeline 完成,不在开发机直接 `npm publish`:
263
+ 发布在开发机执行,必须先 `omc-core` 后 `omc-cli`,顺序不能反:
275
264
 
276
265
  ```bash
277
266
  npm run verify
278
- git tag v0.3.0
279
- git push origin v0.3.0
267
+ npm publish --workspace packages/omc-core
268
+ npm publish --workspace packages/omc-cli
280
269
  ```
281
270
 
282
- `vX.Y.Z` tag 触发 `publish-npm` job。job 使用 `CI_JOB_TOKEN` 写入项目 Package Registry,校验 `omc-core`/`omc-cli` 版本与 tag 一致,构建后按顺序发布两个包。不要手工提交 `.npmrc` 或 token。
271
+ `omc-core` 与 `omc-cli` 版本保持一致;发布前先用 `git tag vX.Y.Z` 记录该版本。新包首次发布进入 npm staged-publishing 审核队列,需维护者在 npmjs.com 用交互式 2FA 批准后真实版本才可见。
283
272
 
284
273
  ### 版本策略
285
274
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@stalfh233/omc-cli",
3
- "version": "0.4.0",
3
+ "version": "0.4.10",
4
4
  "description": "CloudPivot 8.6 configuration capability CLI — governed, fail-closed, coverage-manifest bounded.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -51,7 +51,7 @@
51
51
  },
52
52
  "dependencies": {
53
53
  "commander": "14.0.3",
54
- "omc-core": "0.4.0",
54
+ "omc-core": "0.4.10",
55
55
  "proper-lockfile": "4.1.2",
56
56
  "write-file-atomic": "6.0.0",
57
57
  "zod": "^3.23.8",