clawhub-production-release

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

9.4k|1.5k|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/openclaw/clawhub --skill clawhub-production-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clawhub-production-release
Source: https://github.com/openclaw/clawhub/tree/main/.agents/skills/clawhub-production-release
Command: npx skills add https://github.com/openclaw/clawhub --skill clawhub-production-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ClawHub production changes are manual-only, and merging to main does not deploy the app or publish the CLI. This Skill enforces a safe, auditable release process so operators dispatch the right workflows against the exact verified SHA instead of guessing.

Core Features & Use Cases

  • App Production Deploys: Dispatch the deploy.yml workflow with full, backend, or frontend targets after confirming a successful Deploy Test run for the exact main SHA.
  • Stable CLI npm Releases: Run validation-only preflight for a vX.Y.Z tag, then promote that exact artifact through npm trusted publishing via the npm-release environment.
  • Release Verification: Record workflow URLs, deployed SHAs, and live-surface proof on clawhub.ai before declaring a release complete.
  • Use Case: After merging a backend fix to main, use this Skill to confirm the Test workflow passed for that SHA, dispatch a backend production deploy, and verify the live API contract on clawhub.ai.

Quick Start

Use the clawhub-production-release skill to deploy the current main branch of openclaw/clawhub to production and verify the result.

Frequently Asked Questions about clawhub-production-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy ClawHub to production?▼

Dispatch the deploy.yml workflow on the main branch with a target of full, backend, or frontend using gh workflow run. First confirm a successful Deploy Test run exists for the exact main SHA, then verify the live route on clawhub.ai after completion.

How do I publish a stable ClawHub CLI release to npm?▼

Dispatch clawhub-cli-npm-release.yml twice: first with preflight_only=true for validation, then with preflight_only=false and the preflight run ID to promote that exact artifact. Tags must use the vX.Y.Z format and point to a commit on main.

Does merging to main deploy ClawHub automatically?▼

No, ClawHub production changes are manual-only. Merging to main does not deploy the app or publish the CLI; an operator must explicitly dispatch the deploy or release workflows.

Why does the production deploy require a Deploy Test run first?▼

The successful Deploy Test run for the exact SHA proves the commit passed validation before production exposure. If no exact-SHA Test run exists, the release must stop until Test is fixed or rerun.

What is npm trusted publishing for the CLI release?▼

Real publishes use npm trusted publishing through the npm-release GitHub environment. The trusted publisher must match repository openclaw/clawhub, workflow clawhub-cli-npm-release.yml, and environment npm-release.