fix(release): pin clawhub publish to --family code-plugin

[kaghni]

Summary

Adds --family code-plugin to the clawhub package publish invocation in release.yml. Was meant to land in PR #107 but the merge happened before this commit got included — the family-fix commit (5759109) was pushed to that branch but the merge was finalized using an earlier tip. Re-opening it stand-alone here.

Why

After PR #107 merged, the next Release run is going to hit this on the ClawHub publish step:

ConvexError: Package "hivemind" already exists as a code-plugin;
family changes are not allowed
    at handler (../convex/packages.ts:4305:8)

The existing hivemind package on ClawHub was originally registered with family=code-plugin (verified via clawhub package inspect hivemind → Family: Code Plugin). The clawhub CLI's auto-detection on this openclaw plugin layout picks a different default (bundle-plugin), so without an explicit --family flag it tries to publish as the wrong family and ClawHub refuses.

Fix

One-line change in .github/workflows/release.yml:

-        run: clawhub package publish ./openclaw
+        run: clawhub package publish ./openclaw --family code-plugin

Plus a comment block explaining why.

Verified locally

Test publish run from this machine using the @kaghni token (matches what 1Password now hands CI):

$ clawhub package publish /home/ubuntu/al-projects/hivemind/openclaw \
    --family code-plugin --name hivemind --version 0.0.1-test --tags test
- Preparing hivemind@0.0.1-test
✔ OK. Published hivemind@0.0.1-test (rd7d1frmgts4j1z9mpv9bqk4jd8697hg)

Without --family code-plugin the same auth/data hits family changes are not allowed every time. With it, publish succeeds. Latest tag on ClawHub stayed at 0.6.56 (test publish only set a test tag). Ownership/auth verified working under @kaghni.

Test plan

• CI passes on this PR
• On merge: auto-bump fires (0.7.11 → 0.7.12), Release workflow runs, the publish job clears all upstream gates (build, npm publish), and the clawhub publish step now finds the right family and succeeds — ClawHub's latest tag bumps from 0.6.56 to 0.7.12

Summary by CodeRabbit

• Bug Fixes
  • Corrected package publishing configuration to resolve deployment issues during the release process.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 45d366d0-1b1c-439e-81fd-f091b086e61d

📥 Commits

Reviewing files that changed from the base of the PR and between 0e51e02 and 6e8b7f6.

📒 Files selected for processing (1)

• .github/workflows/release.yml

---

📝 Walkthrough

Walkthrough

The release workflow is modified to explicitly pass the --family code-plugin flag when publishing the openclaw bundle to ClawHub. This ensures the published package matches its registered family and prevents server rejection due to family mismatch.

Changes

ClawHub Release Configuration

Layer / File(s)	Summary
Publish Command Flag .github/workflows/release.yml	The clawhub package publish ./openclaw command is updated to include --family code-plugin to prevent server rejection due to family mismatch.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• activeloopai/hivemind#103: Both PRs modify the release workflow to publish the openclaw bundle to ClawHub, with this PR fixing the publish command by adding the --family code-plugin flag.

Suggested reviewers

• efenocchi

Poem

🐰 A flag so small, yet oh so vital,
The family must match in every title!
ClawHub now knows where code plugins dwell,
No more rejections—all is well! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding the --family code-plugin flag to the clawhub publish command in the release workflow.
Description check	✅ Passed	The description includes comprehensive details (Summary, Why, Fix, Verification, Test plan) that align well with the template, though the version bump guidance in the template is addressed implicitly through the test plan.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/clawhub-family-flag

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Claude finished @kaghni's task in 48s —— View job

---

Review

Reviewed the diff against origin/main — single, narrowly-scoped change to .github/workflows/release.yml:255 adding --family code-plugin to the clawhub package publish invocation, plus an inline comment explaining the rationale.

• Read PR body and verify intent matches diff
• Inspect the changed hunk in context (release.yml lines 242–255)
• Check for collateral concerns (auth, version sync, secret handling)

Findings: none blocking.

• The flag value (code-plugin) matches what the PR body says is already registered on ClawHub (clawhub package inspect hivemind → "Family: Code Plugin"), so pinning it is the correct way to stop the CLI's auto-detection from drifting to bundle-plugin.
• Comment block is appropriately load-bearing — it captures the non-obvious gotcha (server-side family-immutability check at convex/packages.ts:4305) that a future maintainer hitting this would need.
• No changes to auth, secret handling, or the version-sync logic upstream of this step. The publish still runs after the same npm publish --provenance and clawhub login --token steps, so blast radius is just this one CLI invocation.
• This is genuinely a re-do of the commit that missed the merge window on fix(openclaw): drop npm scope from openclaw plugin name for ClawHub publish #107; the diff is consistent with that framing.

Per repo review policy, no inline comments — nothing rises to the bar of a real bug, security issue, or correctness concern.
· branch fix/clawhub-family-flag

[github-actions]

Coverage Report

No src/*.ts files changed in this PR.

_{Generated for commit 6570539.}