From 5bc728d4800cc5ef99b83cdaee1fbb5bb9355e71 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 26 Apr 2026 11:51:06 +0100 Subject: [PATCH] docs(release): refine beta validation guidance --- .../skills/openclaw-release-maintainer/SKILL.md | 16 +++++++++------- docs/.generated/config-baseline.sha256 | 4 ++-- 2 files changed, 11 insertions(+), 9 deletions(-) diff --git a/.agents/skills/openclaw-release-maintainer/SKILL.md b/.agents/skills/openclaw-release-maintainer/SKILL.md index 985061192b6..dd004c28a35 100644 --- a/.agents/skills/openclaw-release-maintainer/SKILL.md +++ b/.agents/skills/openclaw-release-maintainer/SKILL.md @@ -86,10 +86,11 @@ Use this skill for release and publish-time workflow. Keep ordinary development parallel, publish npm from the successful npm preflight, then start published npm install/update, Docker, and Parallels verification while mac artifacts continue. -- After a beta is published, run the expensive Docker, Parallels, and QA-Lab - release rosters in parallel instead of serializing them. Use selective reruns - after failures or fixes, but keep proof that Docker, Parallels, and QA-Lab - each passed at least once before stable/latest promotion. +- After a beta is published, overlap remote/manual release rosters where useful, + but avoid piling local Docker, Parallels, and QA-Lab work onto the same host + when it would create system-load noise. Use selective reruns after failures or + fixes, but keep proof that Docker, Parallels, and QA-Lab each passed at least + once before stable/latest promotion. - Mac packaging may be built from a slight release-branch variation of the tagged commit when the delta is mac packaging, signing, workflow, or validation-only release machinery. If mac packaging needs release-branch-only @@ -558,9 +559,10 @@ node --import tsx scripts/openclaw-npm-postpublish-verify.ts the next beta if the fix must change the already-published package. If any lane fails after the beta tag/package is pushed or published, fix, commit/push/pull, increment to the next beta tag, and rerun the affected - beta evidence. Start Docker, Parallels, and QA-Lab in parallel once the - beta is live. Ensure the full expensive roster has passed at least once - before stable/latest promotion. The roster includes the manual Actions > + beta evidence. Once the beta is live, start remote/manual rosters where they + can overlap safely, but keep local Docker and Parallels load controlled. + Ensure the full expensive roster has passed at least once before + stable/latest promotion. The roster includes the manual Actions > `NPM Telegram Beta E2E` workflow against the exact published beta package. If a pre-npm lane fails before any tag/package leaves the machine, fix and rerun the same intended beta attempt. Repeat up to the operator's diff --git a/docs/.generated/config-baseline.sha256 b/docs/.generated/config-baseline.sha256 index 61450d59778..4270a1983a3 100644 --- a/docs/.generated/config-baseline.sha256 +++ b/docs/.generated/config-baseline.sha256 @@ -1,4 +1,4 @@ -61b66003b38f203b7570372be08e2bccb4e20322c50e67e605a5da73f8ced35b config-baseline.json +91a6cec6c5bdf4b0bf955a058955278990a1af31f32f8fcf2ac26d7548fb99e5 config-baseline.json 5f5fb87fd46f9cbb84d8af17e00ae3c4b74062e8ad517bc2260ba83da2e9014f config-baseline.core.json 080c0a4f2d4175d6d7ab1e38f76b21de32669055c518d75c96e784865d89bf25 config-baseline.channel.json -a5479c182ec987bb21e814b8a4e7b3bda7190ae5c2b35fd5ca403dfa48afa115 config-baseline.plugin.json +f9e0174988718959fe1923a54496ec5b9262721fe1e7306f32ccb1316d9d9c3f config-baseline.plugin.json