ci: publish @snowmead/oxcode-mcp + MCP Registry entry on release - #27
Merged
Conversation
Add a thin npm launcher (npm/) that execs `oxcode mcp`, a server.json registry manifest (io.github.snowmead/oxcode), and a cargo-dist custom publish job (publish-npm.yml). On each release tag it publishes the npm package via OIDC trusted publishing and the registry entry via mcp-publisher (GitHub PAT). Versions are stamped from the oxcode-cli crate version.
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.
What
Automates publishing the oxcode MCP server to npm + the official MCP Registry on every release tag.
npm/— thin launcher@snowmead/oxcode-mcpthat execsoxcode mcp(no binary bundling; requires the self-updatingoxcodeon PATH).server.json— registry manifestio.github.snowmead/oxcode(stdio → the npm package)..github/workflows/publish-npm.yml— cargo-dist custom publish job: stamps the version fromcrates/oxcode-cli/Cargo.toml, publishes to npm via OIDC trusted publishing (no token, auto-provenance), then registers viamcp-publisher(GitHub PAT).dist-workspace.toml/release.yml— wire the new job into the release pipeline (regenerated viadist generate; no hand-edits).One-time setup (already done)
oxgraph/oxcode, workflowrelease.yml(the caller — npm validates the caller's filename for reusable workflows).MCP_GITHUB_TOKENrepo secret (classic PAT,read:org+read:user) — grants theio.github.snowmead/*namespace from inside the oxgraph repo, where OIDC can't.@snowmead/oxcode-mcp@0.2.0+ the registry entry were published manually to bootstrap.Note
The next release must bump
oxcode-cliabove0.2.0(0.2.0 is already on npm). The workflow stamps that single crate version into both the npm package andserver.json.🤖 Generated with Claude Code