ci: publish to MCP registry on release - #18
Closed
simonnordberg wants to merge 1 commit into
Closed
simonnordberg wants to merge 1 commit into
simonnordberg wants to merge 1 commit into
Conversation
Adds an mcp-registry job to the release workflow that runs on every v* tag. Uses GitHub OIDC auth (no secrets needed), updates the server.json version from the tag, and publishes via mcp-publisher. Runs in parallel with the binary release job.
Contributor
Author
|
Superseded by #19, which includes the MCP registry publish as a job in the consolidated release workflow. |
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.
Summary
mcp-registryjob to the release workflow, triggered onv*tagsserver.jsonversion from the tag before publishingreleasejob (both depend only ontest)Prerequisite
The first publish must be done manually to claim the name
io.github.codebahn/codebahn:After that, every tagged release keeps the registry listing up to date automatically.