vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 20:40:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: fan out qa lab lanes

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-23 06:14:54 +01:00
parent 76ab7c5b05
commit c78562d8a2
6 changed files with 224 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/RELEASING.md
View File

@@ -54,9 +54,9 @@ OpenClaw has three public release lanes:
- Run `pnpm release:check` before every tagged release
- Release checks now run in a separate manual workflow:
`OpenClaw Release Checks`
- `OpenClaw Release Checks` also runs the QA Lab mock parity gate and the live
Telegram QA lane before release approval. The live lane uses the
`qa-live-shared` environment and Convex CI credential leases.
- `OpenClaw Release Checks` also runs the QA Lab mock parity gate plus the live
Matrix and Telegram QA lanes before release approval. The live lanes use the
`qa-live-shared` environment; Telegram also uses Convex CI credential leases.
- Cross-OS install and upgrade runtime validation is dispatched from the
private caller workflow
`openclaw/releases-private/.github/workflows/openclaw-cross-os-release-checks.yml`,
@@ -169,7 +169,7 @@ When cutting a stable npm release:
when you intentionally want a direct stable publish
3. Run `OpenClaw Release Checks` separately with the same tag or the
full current workflow-branch commit SHA when you want live prompt cache,
QA Lab parity, and live Telegram coverage
QA Lab parity, Matrix, and Telegram coverage
- This is separate on purpose so live coverage stays available without
recoupling long-running or flaky checks to the publish workflow
4. Save the successful `preflight_run_id`