What problem does it solve?
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
Core Features & Use Cases
- Respect release guardrails by requiring operator approval before version changes and before any publish step.
- Keep release channel naming aligned across stable, beta, and dev channels and ensure appropriate npm dist-tags.
- Handle versions and release files consistently across multiple files (e.g., package.json, app/build files, Info.plist, and changelog entries).
- Build changelog-backed release notes by integrating changes from CHANGELOG.md and tagging releases appropriately.
- Run publish-time validation with scripted checks, ensuring preflight checks and artifact validation before tagging.
- Use the right auth flow for publishing using GitHub trusted publishing and separate maintainer flows for plugins.
Quick Start
Run the maintainer workflow to validate a beta release by updating versions, verifying changelog entries, and executing the release-check sequence before tagging.
