Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix ClawHub publish still requires package.json openclaw.compat.pluginApi, but current plugin docs/runtime no longer document or rely on it [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#56903•Fetched 2026-04-08 01:46:16
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
robinsptrobinspt
Participants
robinsptrobinspt

There appears to be a mismatch between the current native plugin docs/runtime behavior and ClawHub publish validation.

Root Cause

When I removed the old compat block to follow the current docs/runtime direction, ClawHub publish failed because it still required openclaw.compat.pluginApi.

Fix Action

Fix / Workaround

Current workaround

RAW_BUFFERClick to expand / collapse

Summary

There appears to be a mismatch between the current native plugin docs/runtime behavior and ClawHub publish validation.

What I observed

On OpenClaw 2026.3.28, the current plugin docs emphasize package.json > openclaw.extensions for native plugins and no longer document openclaw.compat.pluginApi as part of the current publishing contract.

However, when publishing a plugin to ClawHub, the publish validator still rejects the package with:

package.json openclaw.compat.pluginApi is required

Why this is confusing

For a plugin that originally used this metadata:

  • pluginApi: 1.2.0
  • minGatewayVersion: 2026.3.22
  • builtWithOpenClawVersion: 2026.3.22

ClawHub accepted the metadata requirement, but openclaw plugins install <plugin> on 2026.3.28 then failed with:

Plugin "tickflow-assist" requires plugin API 1.2.0, but this OpenClaw runtime exposes 2026.3.28.

When I removed the old compat block to follow the current docs/runtime direction, ClawHub publish failed because it still required openclaw.compat.pluginApi.

Current workaround

I had to restore openclaw.compat and switch it to date-style values like:

  • pluginApi: 2026.3.22
  • minGatewayVersion: 2026.3.22
  • builtWithOpenClawVersion: 2026.3.28

Request

Could you clarify which contract is intended going forward?

  1. Should native plugins published to ClawHub still include openclaw.compat.pluginApi?
  2. If yes, what is the expected format now: legacy semver like 1.2.0, or date-version like 2026.3.22 / 2026.3.28?
  3. If no, could ClawHub publish validation be updated to match the current plugin docs/runtime?
  4. If the field remains required temporarily, could the docs mention that explicitly to avoid failed publishes?

Thanks.

extent analysis

Fix Plan

To resolve the issue, follow these steps:

  • Update the package.json file to include the required openclaw.compat.pluginApi field.
  • Use the date-version format (e.g., 2026.3.22) for the pluginApi value.
  • Ensure the minGatewayVersion and builtWithOpenClawVersion fields are also in the date-version format.

Example package.json snippet:

{
  "openclaw": {
    "extensions": {
      // existing extensions config
    }
  },
  "openclaw.compat": {
    "pluginApi": "2026.3.22"
  },
  "minGatewayVersion": "2026.3.22",
  "builtWithOpenClawVersion": "2026.3.28"
}

Verification

After updating the package.json file, attempt to publish the plugin to ClawHub again. The publish validation should now pass.

Extra Tips

  • Keep an eye on the official OpenClaw documentation for updates on the publishing contract and required fields.
  • If you encounter further issues, consider reaching out to the OpenClaw support team for assistance.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#integration issue#index setup#retrieval issue#search optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix ClawHub publish still requires package.json openclaw.compat.pluginApi, but current plugin docs/runtime no longer document or rely on it [1 participants]