OpenClaw Release Maintainer

Features

• Automated release preparation and verification
• Changelog and release notes generation
• Publishing commands and artifact management
• Cross-platform build and verification procedures
• Detailed guidance on versioning, signing, and notarization

Use Cases

• Preparing a new stable OpenClaw release
• Publishing a beta version of OpenClaw
• Verifying release artifacts before public distribution
• Generating and updating release notes and changelogs

Non-Goals

• Managing ordinary development changes
• Handling GHSA-specific advisory work
• Automating general software development tasks outside of OpenClaw releases

Workflow

1. Confirm operator intent and choose target version/tag.
2. Commit, push, pull/rebase, and ensure worktree is clean.
3. Pull latest `main`, verify CI green, and run `/changelog`.
4. Create release branch `release/YYYY.M.D` and prepare release changes.
5. Create git tag and refresh GitHub release.
6. Dispatch and wait for CI/CD preflight and validation workflows (npm, macos).
7. Fix any failures, delete/recreate tag/release, and rerun preflights if needed.
8. Publish to npm using the appropriate dist-tag (`beta` or `latest`).
9. Run post-publish verification and beta roster checks.
10. Announce release on Discord.
11. Promote beta to latest if applicable, and verify `appcast.xml` updates.