openclaw/docs/reference/RELEASING.md

title, summary, read_when

title	summary	read_when
Release Policy	Public release channels, version naming, and cadence	Looking for public release channel definitions Looking for version naming and cadence

Release Policy

OpenClaw has three public release lanes:

• stable: tagged releases that publish to npm latest
• beta: prerelease tags that publish to npm beta
• dev: the moving head of main

Version naming

• Stable release version: YYYY.M.D
  • Git tag: vYYYY.M.D
• 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 stable npm release
• beta means the current prerelease npm release
• Every OpenClaw release ships the npm package and macOS app together

Release cadence

• Releases move beta-first
• Stable follows only after the latest beta is validated
• Detailed release procedure, approvals, credentials, and recovery notes are maintainer-only

Release preflight

• Run pnpm release:check before every tagged release
• Run RELEASE_TAG=vYYYY.M.D node --import tsx scripts/openclaw-npm-release-check.ts (or the matching beta/correction tag) before approval
• npm release preflight fails closed unless the tarball includes both dist/control-ui/index.html and a non-empty dist/control-ui/assets/ payload so we do not ship an empty browser dashboard again

Public references

• .github/workflows/openclaw-npm-release.yml
• scripts/openclaw-npm-release-check.ts

Maintainers use the private release docs in openclaw/maintainers/release/README.md for the actual runbook.