openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@c4b8d6d5ab

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-13 12:59:56 +00:00
parent ea0ee28824
commit 0dc8af0dbe
2 changed files with 19 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "9e2ac8a1cb9ace335622a453d742f2b86fcff717",
"syncedAt": "2026-04-13T10:04:29.387Z"
"sha": "c4b8d6d5ab368225c89330a8b8663abc39e352fd",
"syncedAt": "2026-04-13T12:59:55.637Z"
}

22
docs/reference/RELEASING.md
View File

@ -75,7 +75,9 @@ OpenClaw has three public release lanes:
- stable npm releases default to `beta`
- stable npm publish can target `latest` explicitly via workflow input
- stable npm promotion from `beta` to `latest` is still available as an explicit manual mode on the trusted `OpenClaw NPM Release` workflow
- that promotion mode still needs a valid `NPM_TOKEN` in the `npm-release` environment because npm `dist-tag` management is separate from trusted publishing
- direct stable publishes can also run an explicit dist-tag sync mode that
points both `latest` and `beta` at the already-published stable version
- those dist-tag modes still need a valid `NPM_TOKEN` in the `npm-release` environment because npm `dist-tag` management is separate from trusted publishing
- public `macOS Release` is validation-only
- real private mac publish must pass successful private mac
`preflight_run_id` and `validate_run_id`
@ -113,6 +115,8 @@ OpenClaw has three public release lanes:
- `npm_dist_tag`: npm target tag for the publish path; defaults to `beta`
- `promote_beta_to_latest`: `true` to skip publish and move an already-published
stable `beta` build onto `latest`
- `sync_stable_dist_tags`: `true` to skip publish and point both `latest` and
`beta` at an already-published stable version
`OpenClaw Release Checks` accepts these operator-controlled inputs:
@ -129,8 +133,12 @@ Rules:
the workflow verifies that metadata before publish continues
- Promotion mode must use a stable or correction tag, `preflight_only=false`,
an empty `preflight_run_id`, and `npm_dist_tag=beta`
- Promotion mode also requires a valid `NPM_TOKEN` in the `npm-release`
environment because `npm dist-tag add` still needs regular npm auth
- Dist-tag sync mode must use a stable or correction tag,
`preflight_only=false`, an empty `preflight_run_id`, `npm_dist_tag=latest`,
and `promote_beta_to_latest=false`
- Promotion and dist-tag sync modes also require a valid `NPM_TOKEN` in the
`npm-release` environment because `npm dist-tag add` still needs regular npm
auth
## Stable npm release sequence
@ -152,9 +160,13 @@ When cutting a stable npm release:
same stable `tag`, `promote_beta_to_latest=true`, `preflight_only=false`,
`preflight_run_id` empty, and `npm_dist_tag=beta` when you want to move that
published build to `latest`
7. If the release intentionally published directly to `latest` and `beta`
should follow the same stable build, run `OpenClaw NPM Release` with the same
stable `tag`, `sync_stable_dist_tags=true`, `promote_beta_to_latest=false`,
`preflight_only=false`, `preflight_run_id` empty, and `npm_dist_tag=latest`
The promotion mode still requires the `npm-release` environment approval and a
valid `NPM_TOKEN` in that environment.
The promotion and dist-tag sync modes still require the `npm-release`
environment approval and a valid `NPM_TOKEN` in that environment.
That keeps the direct publish path and the beta-first promotion path both
documented and operator-visible.