# Clawhub Production Release

Run and verify ClawHub production deploys and stable ClawHub CLI npm releases.

- Repository: https://github.com/openclaw/clawhub (9543 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add openclaw/clawhub --skill clawhub-production-release -g -a claude-code -y`
Codex: `npx skills add openclaw/clawhub --skill clawhub-production-release -g -a codex -y`
Cursor: `npx skills add openclaw/clawhub --skill clawhub-production-release -g -a cursor -y`
Gemini CLI: `npx skills add openclaw/clawhub --skill clawhub-production-release -g -a gemini-cli -y`

## Description

Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# ClawHub Production Release

ClawHub production changes are manual-only. Merging to `main` does not deploy
the app or publish the CLI.

## Safety Rules

- Run production workflows from `main`.
- Re-read the workflow and exact `main` SHA immediately before dispatch.
- Require a successful `Deploy Test` workflow for that exact SHA before
  dispatching an app production deploy. This is an operator check until the
  production workflow enforces the gate directly.
- Do not treat a green workflow alone as proof. Record the workflow URL, exact
  deployed SHA, and live-surface verification.
- Do not add one-off migrations or repairs to the deploy workflow. Run
  operator-controlled data changes separately with `clawhub-convex` and
  `create-and-cleanup-migration`.
- Never start a production deploy or npm publish unless the user explicitly
  asked for that release action.

## App Production Deploy

The workflow is `.github/workflows/deploy.yml`.

1. Confirm the selected commit is on `origin/main` and record its SHA.
2. Find the successful Test deployment for that exact SHA and record its URL:

```bash
gh run list \
  --repo openclaw/clawhub \
  --workflow deploy-test.yml \
  --branch main \
  --commit <MAIN_SHA> \
  --status success \
  --limit 1
```

If no successful exact-SHA Test run exists, stop and fix or rerun Test before
releasing production.

3. Run the required pre-merge or release validation for the changed surface.
4. Dispatch one target:

```bash
gh workflow run deploy.yml \
  --repo openclaw/clawhub \
  --ref main \
  -f target=full \
  -f allow_deleting_large_indexes=false
```

Choose `full`, `backend`, or `frontend`:

- `full`: deploy Convex, wait for the matching Vercel production deployment,
  and run production smoke checks.
- `backend`: deploy Convex and run production HTTP smoke checks.
- `frontend`: wait for Vercel's production deployment for the selected `main`
  SHA, then run HTTP and UI smoke checks. The workflow does not call
  `vercel deploy`.

The rest: https://github.com/openclaw/clawhub/blob/HEAD/.agents/skills/clawhub-production-release/SKILL.md