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

docs: clarify beta validation-only fixes

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-02 20:06:04 +01:00
parent 35af235755
commit 4b72d8e73c
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
.agents/skills/openclaw-release-maintainer/SKILL.md
View File

@@ -47,6 +47,13 @@ Use this skill for release and publish-time workflow. Keep ordinary development
recreate the tag and prerelease at the fixed commit so npm prerelease versions
stay contiguous. If a published prerelease needs a fix, commit the fix on the
release branch and increment to the next matching `-alpha.N` or `-beta.N`.
- After a beta is published, distinguish validation-only fixes from product
fixes. Test, docs, workflow, release-script, changelog, or agent-skill fixes
that do not change the `openclaw` package runtime can be committed and
validated without cutting a new beta. Any fix that changes shipped OpenClaw
runtime, package contents, install/update behavior, public API, or user-facing
behavior after the beta was published usually requires a new `-beta.N` before
treating release validation as evidence for the published package.
- For a beta release train, run the fast local preflight first, publish the
beta to npm `beta`, then run the expensive published-package roster focused
on install/update/Docker/Parallels/NPM Telegram. If anything fails, fix it on