ci: record package proof in release evidence · openclaw/openclaw@295d63c
steipete
·
2026-04-28
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -103,7 +103,10 @@ the maintainer-only release runbook.
|
103 | 103 | `OpenClaw Release Checks` for install smoke, package acceptance, Docker |
104 | 104 | release-path suites, live/E2E, OpenWebUI, QA Lab parity, Matrix, and Telegram |
105 | 105 | lanes. Provide `npm_telegram_package_spec` only after a package has been |
106 | | - published and the post-publish Telegram E2E should run too. Example: |
| 106 | + published and the post-publish Telegram E2E should run too. Provide |
| 107 | +`evidence_package_spec` when the private evidence report should prove that the |
| 108 | + validation matches a published npm package without forcing Telegram E2E. |
| 109 | + Example: |
107 | 110 | `gh workflow run full-release-validation.yml --ref main -f ref=release/YYYY.M.D` |
108 | 111 | - Run the manual `Package Acceptance` workflow when you want side-channel proof |
109 | 112 | for a package candidate while release work continues. Use `source=npm` for |
@@ -233,7 +236,8 @@ gh workflow run full-release-validation.yml \
|
233 | 236 | --ref main \ |
234 | 237 | -f ref=release/YYYY.M.D \ |
235 | 238 | -f provider=openai \ |
236 | | - -f mode=both |
| 239 | + -f mode=both \ |
| 240 | + -f evidence_package_spec=openclaw@YYYY.M.D-beta.N |
237 | 241 | ``` |
238 | 242 | |
239 | 243 | The workflow resolves the target ref, dispatches manual `CI` with |
@@ -273,6 +277,7 @@ gh workflow run full-release-validation.yml \
|
273 | 277 | -f ref=release/YYYY.M.D \ |
274 | 278 | -f provider=openai \ |
275 | 279 | -f mode=both \ |
| 280 | + -f evidence_package_spec=openclaw@YYYY.M.D-beta.N \ |
276 | 281 | -f npm_telegram_package_spec=openclaw@YYYY.M.D-beta.N \ |
277 | 282 | -f npm_telegram_provider_mode=mock-openai |
278 | 283 | ``` |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
