docs: document release evidence workflow · openclaw/openclaw@390b965
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 |
|---|
@@ -131,6 +131,32 @@ If a full run is already active on a newer `origin/main`, prefer watching that
|
131 | 131 | run over dispatching a duplicate. If you accidentally dispatch a stale duplicate, |
132 | 132 | cancel it and monitor the current run. |
133 | 133 | |
| 134 | +### Release Evidence |
| 135 | + |
| 136 | +After release-candidate validation or before a release decision, record the |
| 137 | +important run ids in the private `openclaw/releases-private` evidence ledger. |
| 138 | +Use the manual `OpenClaw Release Evidence` |
| 139 | +(`openclaw-release-evidence.yml`) workflow there. It writes durable summaries |
| 140 | +under `evidence/<release-id>/` and commits: |
| 141 | + |
| 142 | +- `release-evidence.md` |
| 143 | +- `release-evidence.json` |
| 144 | +- `index.json` |
| 145 | +- `runs/<label>.json` |
| 146 | + |
| 147 | +Use one run per line: |
| 148 | + |
| 149 | +```text |
| 150 | +full-release-validation openclaw/openclaw <run-id> blocking |
| 151 | +package-acceptance openclaw/openclaw <run-id> blocking |
| 152 | +private-cross-os openclaw/releases-private <run-id> advisory |
| 153 | +``` |
| 154 | + |
| 155 | +Store summaries, run URLs, artifact metadata, timings, pass/fail state, and |
| 156 | +short release-manager notes there. Do not store raw logs, provider |
| 157 | +prompts/responses, channel transcripts, signing material, or secret-bearing |
| 158 | +config in git; raw logs stay in Actions artifacts. |
| 159 | + |
134 | 160 | ### Release Checks |
135 | 161 | |
136 | 162 | `OpenClaw Release Checks` (`openclaw-release-checks.yml`) is the release child |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
