@viceme-ai/cli 0.22.2 → 0.23.0
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 +16 -0
- package/checksums.txt +6 -6
- package/docs/releasing.md +21 -13
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,21 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.23.0] - 2026-09-01
|
|
4
|
+
|
|
5
|
+
### Features
|
|
6
|
+
|
|
7
|
+
- 买家侧交易闭环：install 未购版直接下单扫码支付并新增 subscribe (`0efec34`)
|
|
8
|
+
|
|
9
|
+
### Fixes
|
|
10
|
+
|
|
11
|
+
- 发布终态后本地恢复清理失败降级为警告 (`513d7b7`)
|
|
12
|
+
|
|
13
|
+
### Other Changes
|
|
14
|
+
|
|
15
|
+
- 约束 main 拉取请求来源 (`bf8e79f`)
|
|
16
|
+
- viceme-skill-use 购买引导改为扫码支付闭环 (`2c6cf5c`)
|
|
17
|
+
- 钉死 sell-a-skill 预览、改名与来源判定合同 (`374cb95`)
|
|
18
|
+
|
|
3
19
|
## [0.22.2] - 2026-09-01
|
|
4
20
|
|
|
5
21
|
### Fixes
|
package/checksums.txt
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
1
|
+
9c449e3ba96b87714b57c53177ce04941ac60c0eb9d3570fdc789ea72ca4c660 viceme_0.23.0_darwin_amd64
|
|
2
|
+
fc574ce3480c7704acf92e505a6619de7e00b01721c4b41833b96339e7278015 viceme_0.23.0_darwin_arm64
|
|
3
|
+
a242883978eaf5422cdf924618d8a49055cb2fa6142aa52d8e49ae4d3d8284db viceme_0.23.0_linux_amd64
|
|
4
|
+
33643d8f6ae4d2a49e0d6790480288afe871f226f8b00eedf3bf2041395fb5d9 viceme_0.23.0_linux_arm64
|
|
5
|
+
a161833605647336b08ec44a7feef03c1f8633967cfaf843a5a03bf1433d430b viceme_0.23.0_windows_amd64.exe
|
|
6
|
+
5e84f99e041b1420f388437a7db143dc6f2aad7cfeb19b8b750046a19dd54dae viceme_0.23.0_windows_arm64.exe
|
package/docs/releasing.md
CHANGED
|
@@ -64,14 +64,24 @@ Shop signs with the new key. Never replace key material under an existing ID;
|
|
|
64
64
|
remove an old public key only after every Release signed by it is no longer
|
|
65
65
|
installable.
|
|
66
66
|
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
67
|
+
Keep `main` as the repository default branch, but target normal feature and fix
|
|
68
|
+
pull requests explicitly at `dev`. Repository settings allow merge commits only;
|
|
69
|
+
squash and rebase merging are disabled so an administrator bypass cannot detach
|
|
70
|
+
a reviewed `dev` head from `main` history.
|
|
71
|
+
|
|
72
|
+
Protect `dev` with its own active branch ruleset that retains the normal pull
|
|
73
|
+
request, one approving review, the `PR quality` check, all three `PR npm
|
|
74
|
+
installer (<runner>)` checks, strict required-status synchronization, deletion
|
|
75
|
+
protection, and force push protection. Protect `main` with a separate ruleset
|
|
76
|
+
that requires the same checks plus `Release candidate preparation`, but does
|
|
77
|
+
not require `dev` to contain the previous release merge commit. Both rulesets
|
|
78
|
+
allow merge commits only. The required `PR quality` job rejects `main` pull
|
|
79
|
+
requests unless they come from the same repository's `dev` or `hotfix/*`.
|
|
80
|
+
|
|
81
|
+
Add `ViceMe CLI Release Bot` and the organization-admin role to both bypass
|
|
82
|
+
lists with `Always allow`; the latter preserves the legacy rule's existing
|
|
83
|
+
`enforce_admins: false` behavior. Do not leave a legacy branch-protection rule
|
|
84
|
+
active beside the rulesets because it cannot recognize the ruleset's App bypass.
|
|
75
85
|
|
|
76
86
|
The App installation token is scoped to the current repository and
|
|
77
87
|
`Contents: write`, expires after at most one hour, and is revoked automatically
|
|
@@ -85,11 +95,9 @@ set of required checks for the exact prepared commit without duplicate generic
|
|
|
85
95
|
push and pull-request runs. The synchronize event may run release preparation a
|
|
86
96
|
second time; that run is intentionally idempotent and produces no new commit.
|
|
87
97
|
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
merged and performs the tag, binary, GitHub Release, npm, and notification
|
|
92
|
-
steps.
|
|
98
|
+
The checks from `CLI release publication` are deliberately not required for
|
|
99
|
+
merging: that workflow starts only after the release PR has been merged and
|
|
100
|
+
performs the tag, binary, GitHub Release, npm, and notification steps.
|
|
93
101
|
|
|
94
102
|
Create a GitHub Actions Environment named `cdn` and restrict deployments to
|
|
95
103
|
protected branches. The S3 publication job is the only release job that uses
|