feat: add Tencent CloudBase plugin to the curated marketplace - #3136
Conversation
🦋 Changeset detectedLatest commit: 592d608 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fc6dc47f57
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "version": "0.2.0", | ||
| "description": "Build, deploy, and manage Tencent CloudBase apps — databases, cloud functions, storage, auth, and hosting, powered by cloudbase-mcp.", | ||
| "homepage": "https://github.com/TencentCloudBase/CloudBase-AI-Toolkit", | ||
| "keywords": ["cloudbase", "tencent-cloud", "baas", "database", "cloud-function", "mcp"], | ||
| "source": "https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/releases/latest/download/cloudbase-kimi.zip" |
There was a problem hiding this comment.
Pin the asset URL to the advertised plugin version
When upstream publishes a release after 0.2.0, the releases/latest URL will serve different plugin bytes while this entry continues to advertise 0.2.0. Because withLatestVersions skips entries that already define version, the UI will still consider an installed 0.2.0 copy up to date, while a fresh installation labeled v0.2.0 may install the newer artifact. Use an immutable release-asset URL and bump both fields together, or derive the catalog version from the mutable source.
Useful? React with 👍 / 👎.
| if (await hasManifest(child)) { | ||
| out.push(child); | ||
| } else { | ||
| await collectNestedManifestDirs(child, depth + 1, out); |
There was a problem hiding this comment.
Continue searching below each discovered manifest
When one nested plugin directory contains another plugin manifest below it, this branch records the parent but never traverses its descendants. The search therefore reports exactly one candidate and installs the parent even though the archive contains multiple nested manifests, bypassing the intended ambiguity fallback; continue walking the subtree after recording a candidate so every manifest within the depth limit is counted. The same logic is duplicated in the v1 archive implementation.
Useful? React with 👍 / 👎.
fc6dc47 to
592d608
Compare
|
Codex Review: Didn't find any major issues. 🎉 Reviewed commit: ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback". |
Related Issue
N/A — internal plugin-marketplace onboarding. Upstream plugin manifest: TencentCloudBase/CloudBase-AI-Toolkit#932.
Problem
The curated marketplace had no Tencent CloudBase entry. Upstream ships an official Kimi plugin manifest and, per our recommendation, now publishes a single-plugin zip (
cloudbase-kimi.zip) as a GitHub release asset — so the marketplace can list it like any other curated plugin.What changed
plugins/marketplace.json: new curatedcloudbaseentry.sourcepoints at the upstream release asset via the stable latest-release URL (releases/latest/download/cloudbase-kimi.zip);versionis pinned to the plugin manifest version (0.2.0), which upstream versions independently of the toolkit's own release numbers — so the update badge only moves when the plugin itself revs.patch.Verified end to end against the real artifacts: installing through the new entry downloads the upstream zip and yields a healthy plugin (29 skills discovered,
plugin-cloudbase:cloudbaseMCP server enabled,sessionStartrouting skill wired, no diagnostics, reinstall idempotent). CLI marketplace tests (33) pass.Testing note: installing within seconds of an upstream release can hit a transient MCP startup failure if the GitHub asset lands before
@cloudbase/cloudbase-mcpfinishes publishing on npm (the manifest pins the exact MCP version). Flagged to upstream; retrying after the npm publish resolves it.Checklist
/approve). N/A — internal change.gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.