From 881c2e514e2bc12d8563b2eb6004c8ec9f220012 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Sat, 2 May 2026 22:43:41 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@816f3f11a1c222ff6cc450c600048eaa98b6b4ed --- .openclaw-sync/source.json | 4 ++-- docs/ci.md | 2 +- docs/reference/RELEASING.md | 31 ++++++++----------------------- 3 files changed, 11 insertions(+), 26 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 0e19bf49b..757702f1e 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "bcb2476ae717342a0808003cdc2dfeee42ea078b", - "syncedAt": "2026-05-02T22:36:12.413Z" + "sha": "816f3f11a1c222ff6cc450c600048eaa98b6b4ed", + "syncedAt": "2026-05-02T22:41:43.932Z" } diff --git a/docs/ci.md b/docs/ci.md index f0da6566b..5b5c882ce 100644 --- a/docs/ci.md +++ b/docs/ci.md @@ -239,7 +239,7 @@ Use `Package Acceptance` when the question is "does this installable OpenClaw pa ### Candidate sources -- `source=npm` accepts only `openclaw@alpha`, `openclaw@beta`, `openclaw@latest`, or an exact OpenClaw release version such as `openclaw@2026.4.27-beta.2`. Use this for published prerelease/stable acceptance. +- `source=npm` accepts only `openclaw@beta`, `openclaw@latest`, or an exact OpenClaw release version such as `openclaw@2026.4.27-beta.2`. Use this for published prerelease/stable acceptance. - `source=ref` packs a trusted `package_ref` branch, tag, or full commit SHA. The resolver fetches OpenClaw branches/tags, verifies the selected commit is reachable from repository branch history or a release tag, installs deps in a detached worktree, and packs it with `scripts/package-openclaw-for-docker.mjs`. - `source=url` downloads an HTTPS `.tgz`; `package_sha256` is required. - `source=artifact` downloads one `.tgz` from `artifact_run_id` and `artifact_name`; `package_sha256` is optional but should be supplied for externally shared artifacts. diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md index 118b05e1d..c48110076 100644 --- a/docs/reference/RELEASING.md +++ b/docs/reference/RELEASING.md @@ -7,10 +7,9 @@ read_when: - Looking for version naming and cadence --- -OpenClaw has four public release lanes: +OpenClaw has three public release lanes: - stable: tagged releases that publish to npm `beta` by default, or to npm `latest` when explicitly requested -- alpha: prerelease tags that publish to npm `alpha` - beta: prerelease tags that publish to npm `beta` - dev: the moving head of `main` @@ -20,13 +19,10 @@ OpenClaw has four public release lanes: - Git tag: `vYYYY.M.D` - Stable correction release version: `YYYY.M.D-N` - Git tag: `vYYYY.M.D-N` -- Alpha prerelease version: `YYYY.M.D-alpha.N` - - Git tag: `vYYYY.M.D-alpha.N` - Beta prerelease version: `YYYY.M.D-beta.N` - Git tag: `vYYYY.M.D-beta.N` - Do not zero-pad month or day - `latest` means the current promoted stable npm release -- `alpha` means the current alpha install target - `beta` means the current beta install target - Stable and stable correction releases publish to npm `beta` by default; release operators can target `latest` explicitly, or promote a vetted beta build later - Every stable OpenClaw release ships the npm package and macOS app together; @@ -79,15 +75,15 @@ the maintainer-only release runbook. file, lane, workflow job, package profile, provider, or model allowlist that proves the fix. Rerun the full umbrella only when the changed surface makes prior evidence stale. -9. For alpha or beta, tag `vYYYY.M.D-alpha.N` or `vYYYY.M.D-beta.N`, then run `OpenClaw Release Publish` from +9. For beta, tag `vYYYY.M.D-beta.N`, then run `OpenClaw Release Publish` from the matching `release/YYYY.M.D` branch. It verifies `pnpm plugins:sync:check`, publishes all publishable plugin packages to npm first, publishes the same set to ClawHub second, and then promotes the prepared OpenClaw npm preflight artifact with the matching dist-tag. After publish, run post-publish package - acceptance against the published `openclaw@YYYY.M.D-alpha.N`, `openclaw@alpha`, - `openclaw@YYYY.M.D-beta.N`, or `openclaw@beta` package. If a pushed or - published prerelease needs a fix, cut the next matching prerelease number; - do not delete or rewrite the old prerelease. + acceptance against the published `openclaw@YYYY.M.D-beta.N` or + `openclaw@beta` package. If a pushed or published prerelease needs a fix, + cut the next matching prerelease number; do not delete or rewrite the old + prerelease. 10. For stable, continue only after the vetted beta or release candidate has the required validation evidence. Stable npm publish also goes through `OpenClaw Release Publish`, reusing the successful preflight artifact via @@ -132,7 +128,7 @@ the maintainer-only release runbook. `gh workflow run full-release-validation.yml --ref main -f ref=release/YYYY.M.D` - Run the manual `Package Acceptance` workflow when you want side-channel proof for a package candidate while release work continues. Use `source=npm` for - `openclaw@alpha`, `openclaw@beta`, `openclaw@latest`, or an exact release version; `source=ref` + `openclaw@beta`, `openclaw@latest`, or an exact release version; `source=ref` to pack a trusted `package_ref` branch/tag/SHA with the current `workflow_ref` harness; `source=url` for an HTTPS tarball with a required SHA-256; or `source=artifact` for a tarball uploaded by another GitHub @@ -559,16 +555,6 @@ gh workflow run openclaw-release-publish.yml \ -f npm_dist_tag=beta ``` -Alpha publish example: - -```bash -gh workflow run openclaw-release-publish.yml \ - --ref release/YYYY.M.D \ - -f tag=vYYYY.M.D-alpha.N \ - -f preflight_run_id= \ - -f npm_dist_tag=alpha -``` - Stable publish to the default beta dist-tag: ```bash @@ -600,7 +586,7 @@ OpenClaw package must not be published. `OpenClaw NPM Release` accepts these operator-controlled inputs: - `tag`: required release tag such as `v2026.4.2`, `v2026.4.2-1`, or - `v2026.4.2-alpha.1` or `v2026.4.2-beta.1`; when `preflight_only=true`, it may also be the current + `v2026.4.2-beta.1`; when `preflight_only=true`, it may also be the current full 40-character workflow-branch commit SHA for validation-only preflight - `preflight_only`: `true` for validation/build/package only, `false` for the real publish path @@ -630,7 +616,6 @@ OpenClaw package must not be published. Rules: - Stable and correction tags may publish to either `beta` or `latest` -- Alpha prerelease tags may publish only to `alpha` - Beta prerelease tags may publish only to `beta` - For `OpenClaw NPM Release`, full commit SHA input is allowed only when `preflight_only=true`