docs: point release evidence at public checks · openclaw/openclaw@2a6fab9
steipete
·
2026-04-27
·
via Recent Commits to openclaw:main
File tree
.agents/skills/openclaw-testing
| Original file line number | Diff line number | Diff line change |
|---|
@@ -149,7 +149,7 @@ Use one run per line:
|
149 | 149 | ```text |
150 | 150 | full-release-validation openclaw/openclaw <run-id> blocking |
151 | 151 | package-acceptance openclaw/openclaw <run-id> blocking |
152 | | -private-cross-os openclaw/releases-private <run-id> advisory |
| 152 | +release-checks openclaw/openclaw <run-id> blocking |
153 | 153 | ``` |
154 | 154 | |
155 | 155 | Store summaries, run URLs, artifact metadata, timings, pass/fail state, and |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -141,13 +141,12 @@ the maintainer-only release runbook.
|
141 | 141 | live Matrix profile and Telegram QA lane before release approval. The live |
142 | 142 | lanes use the `qa-live-shared` environment; Telegram also uses Convex CI |
143 | 143 | credential leases. Run the manual `QA-Lab - All Lanes` workflow with |
144 | | -`matrix_profile=all` when you want full Matrix transport, media, and E2EE |
145 | | - inventory; the workflow always shards that full Matrix selection in parallel. |
146 | | -- Cross-OS install and upgrade runtime validation is dispatched from the |
147 | | - private caller workflow |
148 | | -`openclaw/releases-private/.github/workflows/openclaw-cross-os-release-checks.yml`, |
149 | | - which invokes the reusable public workflow |
150 | | -`.github/workflows/openclaw-cross-os-release-checks-reusable.yml` |
| 144 | +`matrix_profile=all` and `matrix_shards=true` when you want full Matrix |
| 145 | + transport, media, and E2EE inventory in parallel. |
| 146 | +- Cross-OS install and upgrade runtime validation is part of public |
| 147 | +`OpenClaw Release Checks` and `Full Release Validation`, which call the |
| 148 | + reusable workflow |
| 149 | +`.github/workflows/openclaw-cross-os-release-checks-reusable.yml` directly |
151 | 150 | - This split is intentional: keep the real npm release path short, |
152 | 151 | deterministic, and artifact-focused, while slower live checks stay in their |
153 | 152 | own lane so they do not stall or block publish |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
