Repository navigation
ci: publish server.json to the MCP Registry on release tags - #8
Merged
Merged
Conversation
The registry listing (io.github.flagrix-io/flagrix) was still at 0.1.0: nothing published server.json after the first release, and the interactive `mcp-publisher login github` can no longer publish to an organisation namespace (modelcontextprotocol/registry#1468). The release workflow now, after `npm publish`: - installs mcp-publisher at a pinned version (v1.8.4) and verifies its Sigstore bundle with cosign before running it - logs in with `mcp-publisher login github-oidc` (no secret; uses the job's existing id-token: write permission) - runs `mcp-publisher publish` A first step fails the job before anything is published if the tag disagrees with package.json or either version in server.json. server.json moves to the current 2025-12-11 schema; the 2025-09-29 one is deprecated. For an npm package the migration is only the URL.
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
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.
Why
The MCP Registry listing for
io.github.flagrix-io/flagrixis still at 0.1.0 (published 2026-07-08), while npm is at 0.5.0. Nothing has publishedserver.jsonsince the first release. The interactivemcp-publisher login githubalso can't publish under an organisation namespace any more (modelcontextprotocol/registry#1468). The registry docs recommend logging in from GitHub Actions with OIDC instead.What
.github/workflows/release.yml(still triggered byv*tags):package.jsonversion,server.jsonversionorserver.jsonpackages[0].version. Otherwise npm could get one version while the registry advertises another.mcp-publisherpinned to v1.8.4 and verify its Sigstore bundle before extracting it. v1.8.8 is the newest release but came out 3 days ago, so it isn't pinned yet.mcp-publisher login github-oidc: no secret needed; it uses the job's existingid-token: writepermissionmcp-publisher publishserver.jsonmoves from the deprecated2025-09-29schema to2025-12-11. The only change in that schema is for remote servers, so for an npm package the migration is just the URL.Checked
mcp-publisher validateon the newserver.json: valid, with no deprecation warning (before: valid, with a deprecation warning).v0.5.0passes;v0.5.1(against 0.5.0 files) fails with the mismatch error.After merging
main, using a GitHub token withread:orgfrom an org owner:mcp-publisher login github --token …thenmcp-publisher publish.package.jsonand bothserver.jsonversions, otherwise step 1 fails.