fix: add ClawHub plugin display metadata#87354
Conversation
73faa33 to
a0c9a78
Compare
Dependency Changes DetectedThis PR changes dependency-related files. Maintainers should confirm these changes are intentional. Changed files:
Maintainer follow-up:
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. Re-review progress:
|
Summary
openclaw.plugin.jsonnamemetadata for ClawHub-published plugins that were missing it.@m1hengmaintainer note, NIP-04, zca-js, Codex app-server/catalog, LanceDB auto-recall/capture, OpenShell CLI details, and similar context.pixversepublishable plugin added onmain.Diagnosis
ClawHub package publishing resolves the card display name from
openclaw.plugin.json.namebefore falling back to README/folder naming. The screenshot items with broken names (WhatsApp, Matrix, Discord, Feishu/Lark, Memory LanceDB, Brave) were missing manifest names, so publishing a.tgzmade ClawHub title-case the tarball filename (openclaw-whatsapp-2026.5.26.tgz). Codex already hadopenclaw.plugin.json.name, which is why it rendered correctly.Verification
python3JSON/metadata check for all publishable ClawHub plugin manifests and package descriptions@m1heng,NIP-04,native zca-js, Codex app-server/catalog, LanceDB auto-recall/capture, OpenShell CLI details, etc.)git diff --check -- extensionspnpm release:plugins:clawhub:checkReal behavior proof
Behavior addressed: ClawHub-published plugin cards can use explicit manifest display names instead of title-casing uploaded tarball filenames, and summaries are clearer without dropping existing attribution/details.
Real environment tested: Local OpenClaw checkout metadata and release-check scripts.
Exact steps or command run after this patch:
pnpm release:plugins:clawhub:check;git diff --check -- extensions; JSON parse/metadata assertion over ClawHub-published plugin manifests/package metadata; targeted description fact-preservation check.Evidence after fix: All
publishToClawHubplugins report non-empty manifestnameanddescription; package descriptions are non-empty;plugin-clawhub-release-checkreports publishable plugin metadata OK.Observed result after fix: Release metadata validates for all ClawHub-published plugins.
What was not tested: Live ClawHub publish/render path.