adityamparikh opened a new issue, #251: URL: https://github.com/apache/solr-mcp/issues/251
## What we want Once 1.0.0 passes its vote, solr-mcp should be listed in: - **The official MCP Registry** ([registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io)) as `io.github.apache/solr-mcp`, pointing at the release images on Docker Hub (`apache/solr-mcp`) and GHCR (`ghcr.io/apache/solr-mcp`). - **The Docker MCP Catalog** ([hub.docker.com/mcp](https://hub.docker.com/mcp)), the catalog behind Docker Desktop's MCP Toolkit, pointing at `apache/solr-mcp`. Only voted releases get listed. ASF policy says projects ["SHALL NOT publish unreleased materials outside the development community"](https://www.apache.org/legal/release-policy.html#publication), so no snapshots or nightlies. `release-publish.yml` already publishes to the MCP Registry as part of the post-vote release. ## What needs to happen on the ASF side These steps need a PMC member and ASF Infra. Contributors can't do them. 1. **An INFRA ticket.** A PMC member files an [INFRA Jira](https://issues.apache.org/jira/projects/INFRA) ticket, linking the [email protected] thread that agrees to publish solr-mcp images. Infra's [Docker Hub policy](https://infra.apache.org/docker-hub-policy.html) asks for that link. The ticket asks Infra to: - **Create the Docker Hub repository `apache/solr-mcp`.** - **Add the `DOCKERHUB_USER` / `DOCKERHUB_TOKEN` secrets to `apache/solr-mcp`.** These are the names Infra provisions. apache/solr uses the same two to push `apache/solr-nightly` ([docker-nightly.yml](https://github.com/apache/solr/blob/cabedd1d968059215188f4e7563fb303241899ed/.github/workflows/docker-nightly.yml#L141-L142)). - **Make the `ghcr.io/apache/solr-mcp` package public after the first release push.** GHCR packages are [private when first published](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry), even when pushed from Actions with `GITHUB_TOKEN`. The MCP Registry only accepts images it can pull anonymously. Changing a package's visibility needs admin on it, which in the `apache` org means Infra. 2. **A re-run on the first release.** The release manager runs `release-publish.yml` after the vote as usual. On the first release only, the MCP Registry step fails, because the new GHCR package is still private. Once Infra has made it public, re-run that one job. Later releases push to the same package, which is public by then. Nothing is needed from Infra for the MCP Registry login itself. The `io.github.apache/*` namespace is authorized through GitHub OIDC from the workflow, with no stored secret. ## Contributor side These need no ASF permissions: - bringing `server.json` up to the registry's current format and the image names the workflow actually pushes; - switching `release-publish.yml` to the secret names above; - the [docker/mcp-registry](https://github.com/docker/mcp-registry) submission, after the release. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
