@viceme-ai/cli 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/CHANGELOG.md +10 -0
- package/README.md +3 -1
- package/README.zh.md +3 -1
- package/checksums.txt +6 -6
- package/docs/releasing.md +12 -5
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[](https://www.npmjs.com/package/@viceme-ai/cli)
|
|
4
4
|
[](https://go.dev/)
|
|
5
|
-
[](https://github.com/ViceMe-AI/cli/actions/workflows/ci.yml)
|
|
6
6
|
|
|
7
7
|
[中文版](./README.zh.md) | [English](./README.md)
|
|
8
8
|
|
|
@@ -147,6 +147,8 @@ viceme profile remove company
|
|
|
147
147
|
|
|
148
148
|
`VICEME_CLI_CONFIG_DIR` can override the config root. Local API development still uses the process-only `VICEME_API_BASE_URL`; it is never persisted in a profile.
|
|
149
149
|
|
|
150
|
+
Update checks query the npm registry directly and store only the last successful version result in `~/.viceme-cli/update-state.json`. A result is used as a fallback for at most 24 hours when the registry is temporarily unavailable. npm operations launched by `viceme install` or `viceme update` use the isolated `~/.viceme-cli/npm-cache`, so a broken user-level `~/.npm` cache does not block the CLI. Both files are non-secret and can be deleted safely; credentials never enter either cache.
|
|
151
|
+
|
|
150
152
|
## Agent Skills
|
|
151
153
|
|
|
152
154
|
The current release deliberately ships one platform-level Agent Skill:
|
package/README.zh.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[](https://www.npmjs.com/package/@viceme-ai/cli)
|
|
4
4
|
[](https://go.dev/)
|
|
5
|
-
[](https://github.com/ViceMe-AI/cli/actions/workflows/ci.yml)
|
|
6
6
|
|
|
7
7
|
[中文版](./README.zh.md) | [English](./README.md)
|
|
8
8
|
|
|
@@ -147,6 +147,8 @@ viceme profile remove company
|
|
|
147
147
|
|
|
148
148
|
可以用 `VICEME_CLI_CONFIG_DIR` 覆盖配置根目录。本地 API 联调仍使用进程环境变量 `VICEME_API_BASE_URL`，不会写入 Profile。
|
|
149
149
|
|
|
150
|
+
更新检查直接请求 npm registry，并且只把最近一次成功查询到的版本写入 `~/.viceme-cli/update-state.json`；registry 暂时不可用时，该结果最多回退使用 24 小时。`viceme install` 和 `viceme update` 启动的 npm 操作统一使用隔离的 `~/.viceme-cli/npm-cache`，不会因为用户级 `~/.npm` 缓存损坏而失败。这两个位置都不包含秘密信息，可以安全删除；凭证不会进入任何更新缓存。
|
|
151
|
+
|
|
150
152
|
## Agent Skills
|
|
151
153
|
|
|
152
154
|
当前版本有意只提供一个平台级 Agent Skill：
|
package/checksums.txt
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
1
|
+
bad1e762de8e1dee474e1704008a3341d85917072d499738ad14042af9b91ca4 viceme_0.3.1_darwin_amd64
|
|
2
|
+
5d91b2ab59fd7d58e491f8500b7164a6a93ad310d5bdbbb7e974e7748721dc8e viceme_0.3.1_darwin_arm64
|
|
3
|
+
10125de1ee952e5fe59f620900164ba577bce88cd260a4b81c842bc822d7923a viceme_0.3.1_linux_amd64
|
|
4
|
+
4a9daf2223ca7a1a680ae83cdfbe0f02a96e0c660d9f508bb6d6d1f252d24099 viceme_0.3.1_linux_arm64
|
|
5
|
+
b9f70d30eaf89690e184e404e999ce5c649402797226f2dedb47aac5d44414e4 viceme_0.3.1_windows_amd64.exe
|
|
6
|
+
35ee86d798a65fcf72725b47a092558af5462115f29fa25489868b0d86e27f56 viceme_0.3.1_windows_arm64.exe
|
package/docs/releasing.md
CHANGED
|
@@ -9,7 +9,7 @@ files, create tags, write changelog entries, or run npm commands locally.
|
|
|
9
9
|
1. Feature and fix PRs can merge into `dev` without starting release
|
|
10
10
|
preparation.
|
|
11
11
|
2. A maintainer explicitly opens or marks ready a repository-owned `dev` to
|
|
12
|
-
`main` PR. That release intent starts `
|
|
12
|
+
`main` PR. That release intent starts `CLI release preparation`.
|
|
13
13
|
3. `npm/scripts/prepare-release.mjs` finds the newest reachable stable tag and
|
|
14
14
|
reads all unreleased non-merge commits.
|
|
15
15
|
4. Conventional Commits select the next version:
|
|
@@ -26,7 +26,7 @@ files, create tags, write changelog entries, or run npm commands locally.
|
|
|
26
26
|
checks, and is updated to `chore(release): vX.Y.Z` with exact run and commit
|
|
27
27
|
evidence. No internal preparation PR is created.
|
|
28
28
|
8. A maintainer reviews and merges that same Release PR.
|
|
29
|
-
9. `
|
|
29
|
+
9. `CLI release publication` tags the exact reviewed `dev` head, reruns
|
|
30
30
|
the quality gates, builds six platform binaries and six checksums, creates
|
|
31
31
|
the GitHub Release, bundles those exact checksums into the npm launcher,
|
|
32
32
|
publishes it, and then sends an
|
|
@@ -43,8 +43,9 @@ are not required. Configure:
|
|
|
43
43
|
- repository secret `RELEASE_APP_PRIVATE_KEY`: the complete generated PEM key.
|
|
44
44
|
|
|
45
45
|
Protect `dev` with an active branch ruleset that retains the normal pull request,
|
|
46
|
-
one approving review,
|
|
47
|
-
|
|
46
|
+
one approving review, the `PR quality` check, all three `PR npm installer
|
|
47
|
+
(<runner>)` checks, deletion protection, and force push protection. Add `ViceMe
|
|
48
|
+
CLI Release Bot` and the organization-admin role to
|
|
48
49
|
the bypass list with `Always allow`; the latter preserves the legacy rule's
|
|
49
50
|
existing `enforce_admins: false` behavior. Do not leave the legacy
|
|
50
51
|
branch-protection rule active beside the ruleset because it cannot recognize the
|
|
@@ -56,12 +57,18 @@ when the job finishes. The workflow still stages an explicit allowlist of
|
|
|
56
57
|
generated files and validates the complete release before pushing. No
|
|
57
58
|
maintainer PAT or Deploy Key is used.
|
|
58
59
|
|
|
59
|
-
The general CLI
|
|
60
|
+
The general `CLI PR checks` workflow runs for pull requests, not branch pushes. A
|
|
60
61
|
Release App push synchronizes the already-open `dev` to `main` PR, producing one
|
|
61
62
|
set of required checks for the exact prepared commit without duplicate generic
|
|
62
63
|
push and pull-request runs. The synchronize event may run release preparation a
|
|
63
64
|
second time; that run is intentionally idempotent and produces no new commit.
|
|
64
65
|
|
|
66
|
+
Protect `main` with the same four PR checks plus `Release candidate
|
|
67
|
+
preparation`. The checks from `CLI release publication` are deliberately not
|
|
68
|
+
required for merging: that workflow starts only after the release PR has been
|
|
69
|
+
merged and performs the tag, binary, GitHub Release, npm, and notification
|
|
70
|
+
steps.
|
|
71
|
+
|
|
65
72
|
Configure npm trusted publishing for:
|
|
66
73
|
|
|
67
74
|
- npm package: `@viceme-ai/cli`;
|