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

docs: point release evidence at public checks

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-27 06:32:59 +01:00
parent c7d77f8c7b
commit 2a6fab9d22
2 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/reference/RELEASING.md
View File

@@ -141,13 +141,12 @@ the maintainer-only release runbook.
live Matrix profile and Telegram QA lane before release approval. The live
lanes use the `qa-live-shared` environment; Telegram also uses Convex CI
credential leases. Run the manual `QA-Lab - All Lanes` workflow with
`matrix_profile=all` when you want full Matrix transport, media, and E2EE
inventory; the workflow always shards that full Matrix selection in parallel.
- 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`,
which invokes the reusable public workflow
`.github/workflows/openclaw-cross-os-release-checks-reusable.yml`
`matrix_profile=all` and `matrix_shards=true` when you want full Matrix
transport, media, and E2EE inventory in parallel.
- Cross-OS install and upgrade runtime validation is part of public
`OpenClaw Release Checks` and `Full Release Validation`, which call the
reusable workflow
`.github/workflows/openclaw-cross-os-release-checks-reusable.yml` directly
- This split is intentional: keep the real npm release path short,
deterministic, and artifact-focused, while slower live checks stay in their
own lane so they do not stall or block publish