Ready the AI/ML API plugin for third-party ClawHub publishing - #6
Merged
Conversation
Upstream (openclaw#49177) told us to publish this as a third-party ClawHub plugin instead of merging into core. Two gaps blocked that: - No `icon` in openclaw.plugin.json — ClawHub falls back to a generic icon without one. Added AIMLAPI's hosted logo mark. - package.json was still scoped `@openclaw/aimlapi-provider` and marked `private: true` — ClawHub publishing is owner-scoped (docs/clawhub/ publishing.md), so publishing under the `@openclaw` scope would be rejected outright (we don't control that namespace). Renamed to `@aimlapi/openclaw-provider`, dropped `private`, added the `compat.pluginApi` / `build.openclawVersion` fields ClawHub requires, and pointed `repository`/`install.*Spec` at our own fork. Structurally validated: `clawhub package publish extensions/aimlapi --dry-run` packs clean (15 files, 66.6 KB) with the corrected name/compat resolved from this repo. Actual publish still needs `clawhub login` under an @aimlapi-owned ClawHub account — not something this session can do.
Dependency GuardThis PR changes dependency-related files. Maintainers should confirm these changes are intentional. Changed files:
Maintainer follow-up:
|
Dependency graph changes notedThis PR includes dependency graph changes. The dependency guard is informational because the PR author is a repository admin or a member of
Security review is still recommended before merge when the dependency graph change is intentional. |
4 tasks
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.
Summary
Upstream (openclaw#49177) closed our two earlier attempts to merge AI/ML API as a bundled core provider, telling us to publish it as a third-party ClawHub plugin instead:
extensions/aimlapi/already exists onmainas a self-contained plugin (provider + web search + video generation), but two things blocked actually publishing it:iconinopenclaw.plugin.json— ClawHub falls back to the generic default icon without one. Added AIMLAPI's hosted logo mark (https://cdn.prod.website-files.com/.../Logo Icon.png, same brand asset the marketing site uses for its own favicon) + adescription.package.jsonwas still named@openclaw/aimlapi-providerand markedprivate: true(leftover from when this was aimed at the core monorepo). ClawHub publishing is owner-scoped (docs/clawhub/publishing.md) — publishing under@openclawwould be rejected outright since we don't control that namespace. Renamed to@aimlapi/openclaw-provider, droppedprivate, added thecompat.pluginApi/build.openclawVersionfields ClawHub requires, and pointedrepository/install.*Specat our own fork instead ofopenclaw/openclaw.Test plan
clawhub package publish extensions/aimlapi --dry-run— packs clean, 15 files (66.6 KB), name/compat/source all resolve correctly from this repoclawhub login+clawhub package publish) still needs to run under an@aimlapi-owned ClawHub account — not something this PR can do; someone with those credentials needs to run it after merge