Publish @aimlapi/openclaw-provider v1.2.1 to ClawHub - #7
Merged
Conversation
…nto setup Published @aimlapi/openclaw-provider@1.2.1 (previous latest: 1.2.0, missing the icon/description this pass adds). package.json needed openclaw.release.publishToClawHub:true restored — the local runtime-build tooling (scripts/check-plugin-npm-runtime-builds.mts) gates on that flag to even produce a dist/ build plan, which clawhub package publish requires (raw .ts entries aren't accepted). Also mirrored providerAuthEnvVars into setup.providers[].envVars per the plugin-validation-fixes doc for the provider-auth-env-vars deprecation warning — kept the legacy field too, as instructed. Note: this doesn't fully silence the inspector's warning, but neither does OpenClaw's own bundled Anthropic provider plugin (checked live), so not chasing further.
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. |
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
Follow-up to #6. Turns out
@aimlapi/openclaw-providerwas already live on ClawHub at v1.2.0 (published from an earlierfeature/aimlapi-provider-pluginbranch, 50 downloads / 7 installs) — but without the icon this repo'smainnever shipped either. Published v1.2.1 with the icon + description now live.extensions/aimlapi/package.jsonto1.2.1.openclaw.release.publishToClawHub: true— Ready the AI/ML API plugin for third-party ClawHub publishing #6 accidentally dropped it, and the local build tooling (scripts/check-plugin-npm-runtime-builds.mts) gates thedist/runtime-build plan on that flag;clawhub package publishrejects raw.tsentries without it.providerAuthEnvVarsintosetup.providers[].envVarsper the ClawHub plugin-validation-fixes guidance (kept the legacy field too, as instructed).Test plan
node --import tsx scripts/check-plugin-npm-runtime-builds.mts --package extensions/aimlapi— builds clean, 8 entriesclawhub package publish extensions/aimlapi --dry-run— packs clean, 23 files (101.7 KB)clawhub package publish extensions/aimlapi— live-published,@aimlapi/openclaw-provider@1.2.1, pending ClawHub security scanclawhub package validate— Plugin Inspector PASS, 0 breakages, 2 P2 warnings (same class of warnings OpenClaw's own bundled Anthropic provider plugin has, verified live — not chasing further)