openclaw-release-maintainer
starsforks
How to install openclaw-release-maintainer?
safeai-lab-x/clawkeeper/openclaw-release-maintainer
$npx -y skills add SafeAI-Lab-X/ClawKeeper --skill openclaw-release-maintainerMaintainer 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
SKILL.md
| 1 | # OpenClaw Release Maintainer |
| 2 | |
| 3 | Use this skill for release and publish-time workflow. Keep ordinary development changes and GHSA-specific advisory work outside this skill. |
| 4 | |
| 5 | ## Respect release guardrails |
| 6 | |
| 7 | - Do not change version numbers without explicit operator approval. |
| 8 | - Ask permission before any npm publish or release step. |
| 9 | - Use the private maintainer release docs for the actual runbook and `docs/reference/RELEASING.md` for public policy. |
| 10 | |
| 11 | ## Keep release channel naming aligned |
| 12 | |
| 13 | - `stable`: tagged releases only, with npm dist-tag `latest` |
| 14 | - `beta`: prerelease tags like `vYYYY.M.D-beta.N`, with npm dist-tag `beta` |
| 15 | - Prefer `-beta.N`; do not mint new `-1` or `-2` beta suffixes |
| 16 | - `dev`: moving head on `main` |
| 17 | - When using a beta Git tag, publish npm with the matching beta version suffix so the plain version is not consumed or blocked |
| 18 | |
| 19 | ## Handle versions and release files consistently |
| 20 | |
| 21 | - Version locations include: |
| 22 | - `package.json` |
| 23 | - `apps/android/app/build.gradle.kts` |
| 24 | - `apps/ios/Sources/Info.plist` |
| 25 | - `apps/ios/Tests/Info.plist` |
| 26 | - `apps/macos/Sources/OpenClaw/Resources/Info.plist` |
| 27 | - `docs/install/updating.md` |
| 28 | - Peekaboo Xcode project and plist version fields |
| 29 | - “Bump version everywhere” means all version locations above except `appcast.xml`. |
| 30 | - Release signing and notary credentials live outside the repo in the private maintainer docs. |
| 31 | |
| 32 | ## Build changelog-backed release notes |
| 33 | |
| 34 | - Changelog entries should be user-facing, not internal release-process notes. |
| 35 | - When cutting a mac release with a beta GitHub prerelease: |
| 36 | - tag `vYYYY.M.D-beta.N` from the release commit |
| 37 | - create a prerelease titled `openclaw YYYY.M.D-beta.N` |
| 38 | - use release notes from the matching `CHANGELOG.md` version section |
| 39 | - attach at least the zip and dSYM zip, plus dmg if available |
| 40 | - Keep the top version entries in `CHANGELOG.md` sorted by impact: |
| 41 | - `### Changes` first |
| 42 | - `### Fixes` deduped with user-facing fixes first |
| 43 | |
| 44 | ## Run publish-time validation |
| 45 | |
| 46 | Before tagging or publishing, run: |
| 47 | |
| 48 | ```bash |
| 49 | node --import tsx scripts/release-check.ts |
| 50 | pnpm release:check |
| 51 | pnpm test:install:smoke |
| 52 | ``` |
| 53 | |
| 54 | For a non-root smoke path: |
| 55 | |
| 56 | ```bash |
| 57 | OPENCLAW_INSTALL_SMOKE_SKIP_NONROOT=1 pnpm test:install:smoke |
| 58 | ``` |
| 59 | |
| 60 | ## Use the right auth flow |
| 61 | |
| 62 | - Core `openclaw` publish uses GitHub trusted publishing. |
| 63 | - Do not use `NPM_TOKEN` or the plugin OTP flow for core releases. |
| 64 | - `@openclaw/*` plugin publishes use a separate maintainer-only flow. |
| 65 | - Only publish plugins that already exist on npm; bundled disk-tree-only plugins stay unpublished. |
| 66 | |
| 67 | ## GHSA advisory work |
| 68 | |
| 69 | - Use `openclaw-ghsa-maintainer` for GHSA advisory inspection, patch/publish flow, private-fork validation, and GHSA API-specific publish checks. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
