ci(docker): add the MCP Registry ownership-verification label - #866
ci(docker): add the MCP Registry ownership-verification label#866moonming wants to merge 1 commit into
Conversation
The MCP Registry verifies OCI-package ownership by checking the io.modelcontextprotocol.server.name label on the image against the server.json name. Bake it into the runtime stage so the next release image is publishable to the registry as io.github.api7/aisix.
|
Warning Review limit reached
Next review available in: 57 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
One-line enabler for listing AISIX in the official MCP Registry (registry.modelcontextprotocol.io).
The registry's OCI ownership verification requires the image to carry
LABEL io.modelcontextprotocol.server.namematching theserver.jsonname (package-types docs, Docker/OCI section). Namespaceio.github.api7/aisixuses GitHub-org authentication (no DNS setup needed); it can be republished under a DNS-verifiedai.api7/*name later without breaking anything — the label just has to match whatever name we publish under.No behavior change — a static image label. The registry entry itself will be published after the next release ships with this label.