Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kaghni merged 1 commit into from
May 7, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,16 @@ jobs:
# The release job above already synced openclaw/package.json and
# openclaw/openclaw.plugin.json versions to the bumped root
# version, so this publishes the same X.Y.Z that npm just got.
run: clawhub package publish ./openclaw
#
# --family code-plugin: the existing `hivemind` package on ClawHub
# was originally registered with family=code-plugin (see
# `clawhub package inspect hivemind` → "Family: Code Plugin"). The
# CLI's auto-detection picks a different default (bundle-plugin) on
# this layout, and ClawHub's server rejects with
# `Package already exists as a code-plugin; family changes are not
# allowed` (convex/packages.ts:4305). Pinning the family explicitly
# matches what's already registered and lets the publish proceed.
run: clawhub package publish ./openclaw --family code-plugin

- name: Summary
run: |
Expand Down
Loading