@@ -7,9 +7,10 @@ read_when:
77 - Looking for version naming and cadence
88---
9910-OpenClaw has three public release lanes:
10+OpenClaw has four 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`
1314- beta: prerelease tags that publish to npm `beta`
1415- dev: the moving head of `main`
1516@@ -19,10 +20,13 @@ OpenClaw has three public release lanes:
1920- Git tag: `vYYYY.M.D`
2021- Stable correction release version: `YYYY.M.D-N`
2122- Git tag: `vYYYY.M.D-N`
23+- Alpha prerelease version: `YYYY.M.D-alpha.N`
24+- Git tag: `vYYYY.M.D-alpha.N`
2225- Beta prerelease version: `YYYY.M.D-beta.N`
2326- Git tag: `vYYYY.M.D-beta.N`
2427- Do not zero-pad month or day
2528- `latest` means the current promoted stable npm release
29+- `alpha` means the current alpha install target
2630- `beta` means the current beta install target
2731- Stable and stable correction releases publish to npm `beta` by default; release operators can target `latest` explicitly, or promote a vetted beta build later
2832- Every stable OpenClaw release ships the npm package and macOS app together;
@@ -75,14 +79,15 @@ the maintainer-only release runbook.
7579 file, lane, workflow job, package profile, provider, or model allowlist that
7680 proves the fix. Rerun the full umbrella only when the changed surface makes
7781 prior evidence stale.
78-9. For beta, tag `vYYYY.M.D-beta.N`, then run `OpenClaw Release Publish` from
82+9. For alpha or beta, tag `vYYYY.M.D-alpha.N` or `vYYYY.M.D-beta.N`, then run `OpenClaw Release Publish` from
7983 the matching `release/YYYY.M.D` branch. It verifies `pnpm plugins:sync:check`,
8084 publishes all publishable plugin packages to npm first, publishes the same
8185 set to ClawHub second, and then promotes the prepared OpenClaw npm preflight
82- artifact with dist-tag `beta`. After publish, run post-publish package
83- acceptance against the published `openclaw@YYYY.M.D-beta.N` or `openclaw@beta`
84- package. If a pushed or published beta needs a fix, cut the next `-beta.N`;
85- do not delete or rewrite the old beta.
86+ 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.
869110. For stable, continue only after the vetted beta or release candidate has the
8792 required validation evidence. Stable npm publish also goes through
8893`OpenClaw Release Publish`, reusing the successful preflight artifact via
@@ -124,7 +129,7 @@ the maintainer-only release runbook.
124129`gh workflow run full-release-validation.yml --ref main -f ref=release/YYYY.M.D`
125130- Run the manual `Package Acceptance` workflow when you want side-channel proof
126131 for a package candidate while release work continues. Use `source=npm` for
127-`openclaw@beta`, `openclaw@latest`, or an exact release version; `source=ref`
132+`openclaw@alpha`, `openclaw@beta`, `openclaw@latest`, or an exact release version; `source=ref`
128133 to pack a trusted `package_ref` branch/tag/SHA with the current
129134`workflow_ref` harness; `source=url` for an HTTPS tarball with a required
130135 SHA-256; or `source=artifact` for a tarball uploaded by another GitHub
@@ -548,6 +553,16 @@ gh workflow run openclaw-release-publish.yml \
548553 -f npm_dist_tag=beta
549554```
550555556+Alpha publish example:
557+558+```bash
559+gh workflow run openclaw-release-publish.yml \
560+ --ref release/YYYY.M.D \
561+ -f tag=vYYYY.M.D-alpha.N \
562+ -f preflight_run_id=<successful-openclaw-npm-preflight-run-id> \
563+ -f npm_dist_tag=alpha
564+```
565+551566Stable publish to the default beta dist-tag:
552567553568```bash
@@ -579,7 +594,7 @@ OpenClaw package must not be published.
579594`OpenClaw NPM Release` accepts these operator-controlled inputs:
580595581596- `tag`: required release tag such as `v2026.4.2`, `v2026.4.2-1`, or
582-`v2026.4.2-beta.1`; when `preflight_only=true`, it may also be the current
597+`v2026.4.2-alpha.1` or `v2026.4.2-beta.1`; when `preflight_only=true`, it may also be the current
583598 full 40-character workflow-branch commit SHA for validation-only preflight
584599- `preflight_only`: `true` for validation/build/package only, `false` for the
585600 real publish path
@@ -609,6 +624,7 @@ OpenClaw package must not be published.
609624Rules:
610625611626- Stable and correction tags may publish to either `beta` or `latest`
627+- Alpha prerelease tags may publish only to `alpha`
612628- Beta prerelease tags may publish only to `beta`
613629- For `OpenClaw NPM Release`, full commit SHA input is allowed only when
614630`preflight_only=true`
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。