build: make npm release tag configurable

This commit is contained in:
Peter Steinberger
2026-04-02 19:05:27 +01:00
parent bcd61e54e1
commit 209535b7c7
10 changed files with 203 additions and 96 deletions

View File

@@ -18,8 +18,11 @@ OpenClaw ships three update channels:
The `main` branch is for experimentation and active development. It may contain
incomplete features or breaking changes. Do not use it for production gateways.
We ship builds to **beta**, test them, then **promote a vetted build to `latest`**
without changing the version number -- dist-tags are the source of truth for npm installs.
We usually ship stable builds to **beta** first, test them there, then run an
explicit promotion step that moves the vetted build to `latest` without
changing the version number. Maintainers can also publish a stable release
directly to `latest` when needed. Dist-tags are the source of truth for npm
installs.
## Switching channels
@@ -109,7 +112,7 @@ source (config, git tag, git branch, or default).
- Keep tags immutable: never move or reuse a tag.
- npm dist-tags remain the source of truth for npm installs:
- `latest` -> stable
- `beta` -> candidate build
- `beta` -> candidate build or beta-first stable build
- `dev` -> main snapshot (optional)
## macOS app availability