Skip to content

ci: publish to MCP registry on release - #18

Closed
simonnordberg wants to merge 1 commit into
mainfrom
ci/mcp-registry-publish
Closed

simonnordberg wants to merge 1 commit into
mainfrom
ci/mcp-registry-publish

Conversation

@simonnordberg

Copy link
Copy Markdown
Contributor

Summary

  • Adds an mcp-registry job to the release workflow, triggered on v* tags
  • Uses GitHub OIDC authentication (no secrets to manage)
  • Updates server.json version from the tag before publishing
  • Runs in parallel with the release job (both depend only on test)

Prerequisite

The first publish must be done manually to claim the name io.github.codebahn/codebahn:

mcp-publisher login github
mcp-publisher publish

After that, every tagged release keeps the registry listing up to date automatically.

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.
@simonnordberg

Copy link
Copy Markdown
Contributor Author

Superseded by #19, which includes the MCP registry publish as a job in the consolidated release workflow.

@simonnordberg
simonnordberg deleted the ci/mcp-registry-publish branch September 23, 2026 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant