mirror of https://github.com/openclaw/openclaw.git synced 2026-03-24 16:32:29 +00:00

Files

Onur Solmaz 8ed33c2aff release: automate macOS publishing (#52853 )

* release: automate macOS publishing

* release: keep mac appcast in openclaw repo

* release: add preflight-only release workflow runs

* release: keep appcast updates manual

* release: generate signed appcast as workflow artifact

* release: require preflight before publish

* release: require mac app for every release

* docs: clarify every release ships mac app

* release: document Sparkle feed and SHA rules

* release: keep publish flow tag-based

* release: stabilize mac appcast flow

* release: document local mac fallback

2026-03-23 16:04:53 +01:00

1.4 KiB

Raw Blame History

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

Public references

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

1.4 KiB Raw Blame History

Release Policy

Version naming

Release cadence

Public references

1.4 KiB

Raw Blame History