@@ -7,10 +7,9 @@ read_when:
77 - Looking for version naming and cadence
88---
9910-OpenClaw has four public release lanes:
10+OpenClaw has three public release lanes:
11111212- stable: tagged releases that publish to npm `beta` by default, or to npm `latest` when explicitly requested
13-- alpha: prerelease tags that publish to npm `alpha`
1413- beta: prerelease tags that publish to npm `beta`
1514- dev: the moving head of `main`
1615@@ -20,13 +19,10 @@ OpenClaw has four public release lanes:
2019- Git tag: `vYYYY.M.D`
2120- Stable correction release version: `YYYY.M.D-N`
2221- Git tag: `vYYYY.M.D-N`
23-- Alpha prerelease version: `YYYY.M.D-alpha.N`
24-- Git tag: `vYYYY.M.D-alpha.N`
2522- Beta prerelease version: `YYYY.M.D-beta.N`
2623- Git tag: `vYYYY.M.D-beta.N`
2724- Do not zero-pad month or day
2825- `latest` means the current promoted stable npm release
29-- `alpha` means the current alpha install target
3026- `beta` means the current beta install target
3127- Stable and stable correction releases publish to npm `beta` by default; release operators can target `latest` explicitly, or promote a vetted beta build later
3228- Every stable OpenClaw release ships the npm package and macOS app together;
@@ -79,15 +75,15 @@ the maintainer-only release runbook.
7975 file, lane, workflow job, package profile, provider, or model allowlist that
8076 proves the fix. Rerun the full umbrella only when the changed surface makes
8177 prior evidence stale.
82-9. For alpha or beta, tag `vYYYY.M.D-alpha.N` or `vYYYY.M.D-beta.N`, then run `OpenClaw Release Publish` from
78+9. For beta, tag `vYYYY.M.D-beta.N`, then run `OpenClaw Release Publish` from
8379 the matching `release/YYYY.M.D` branch. It verifies `pnpm plugins:sync:check`,
8480 publishes all publishable plugin packages to npm first, publishes the same
8581 set to ClawHub second, and then promotes the prepared OpenClaw npm preflight
8682 artifact with the matching dist-tag. After publish, run post-publish package
87- acceptance against the published `openclaw@YYYY.M.D-alpha.N`, `openclaw@alpha`,
88-`openclaw@YYYY.M.D-beta.N`, or `openclaw@beta` package. If a pushed or
89-published prerelease needs a fix, cut the next matching prerelease number;
90-do not delete or rewrite the old prerelease.
83+ acceptance against the published `openclaw@YYYY.M.D-beta.N` or
84+`openclaw@beta` package. If a pushed or published prerelease needs a fix,
85+ cut the next matching prerelease number; do not delete or rewrite the old
86+ prerelease.
918710. For stable, continue only after the vetted beta or release candidate has the
9288 required validation evidence. Stable npm publish also goes through
9389`OpenClaw Release Publish`, reusing the successful preflight artifact via
@@ -132,7 +128,7 @@ the maintainer-only release runbook.
132128`gh workflow run full-release-validation.yml --ref main -f ref=release/YYYY.M.D`
133129- Run the manual `Package Acceptance` workflow when you want side-channel proof
134130 for a package candidate while release work continues. Use `source=npm` for
135-`openclaw@alpha`, `openclaw@beta`, `openclaw@latest`, or an exact release version; `source=ref`
131+`openclaw@beta`, `openclaw@latest`, or an exact release version; `source=ref`
136132 to pack a trusted `package_ref` branch/tag/SHA with the current
137133`workflow_ref` harness; `source=url` for an HTTPS tarball with a required
138134 SHA-256; or `source=artifact` for a tarball uploaded by another GitHub
@@ -559,16 +555,6 @@ gh workflow run openclaw-release-publish.yml \
559555 -f npm_dist_tag=beta
560556```
561557562-Alpha publish example:
563-564-```bash
565-gh workflow run openclaw-release-publish.yml \
566- --ref release/YYYY.M.D \
567- -f tag=vYYYY.M.D-alpha.N \
568- -f preflight_run_id=<successful-openclaw-npm-preflight-run-id> \
569- -f npm_dist_tag=alpha
570-```
571-572558Stable publish to the default beta dist-tag:
573559574560```bash
@@ -600,7 +586,7 @@ OpenClaw package must not be published.
600586`OpenClaw NPM Release` accepts these operator-controlled inputs:
601587602588- `tag`: required release tag such as `v2026.4.2`, `v2026.4.2-1`, or
603-`v2026.4.2-alpha.1` or `v2026.4.2-beta.1`; when `preflight_only=true`, it may also be the current
589+`v2026.4.2-beta.1`; when `preflight_only=true`, it may also be the current
604590 full 40-character workflow-branch commit SHA for validation-only preflight
605591- `preflight_only`: `true` for validation/build/package only, `false` for the
606592 real publish path
@@ -630,7 +616,6 @@ OpenClaw package must not be published.
630616Rules:
631617632618- Stable and correction tags may publish to either `beta` or `latest`
633-- Alpha prerelease tags may publish only to `alpha`
634619- Beta prerelease tags may publish only to `beta`
635620- For `OpenClaw NPM Release`, full commit SHA input is allowed only when
636621`preflight_only=true`
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。