Add required openclaw.build metadata for ClawHub publishing - #3
Merged
Conversation
ClawHub's package validation requires both openclaw.compat.pluginApi and openclaw.build.openclawVersion in package.json for external code plugins. Only the former was present, so `clawhub package publish` rejected the package with "openclaw.build.openclawVersion is required for external code plugins published to ClawHub." Add the openclaw.build block (openclawVersion + pluginSdkVersion) and compat.minGatewayVersion, pinned to the openclaw version this plugin builds and tests against. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
clawhub package publishwas failing. Two distinct issues were found:Manifest-missing error (
openclaw.plugin.json is required for plugin packages) — this happened when publishing from a checkout that predated the manifest / had no builtdist/. Publishing from up-to-date, built code resolves it.Missing required package.json field — ClawHub's validator (
clawhub'sschema/openclawContract.js) requires bothopenclaw.compat.pluginApiandopenclaw.build.openclawVersionfor external code plugins. Only the first was present, so publish was rejected with:Fix
Add the
openclaw.buildblock (openclawVersion+pluginSdkVersion) andcompat.minGatewayVersion, pinned to2026.7.2-beta.3(the version this plugin builds and tests against).Verification
Reproduced the failure and confirmed the fix with the real
clawhubCLI (clawhub package pack .):Error: openclaw.build.openclawVersion is required ...openclaw.plugin.json,dist/tools/index.js, anddist/channel/index.js.Note for publishing
ClawHub packs with
npm pack --ignore-scripts, so it does not run the build. Publish from a locally-built folder or tarball (npm run plugin:buildfirst), not a raw GitHub ref — otherwisedist/(gitignored) is absent from the package.🤖 Generated with Claude Code