Repository navigation
feat(ci): add MCP Registry automated publish workflow and bump version to 2.7.1 - #135
Conversation
MustermenschAlex
left a comment
There was a problem hiding this comment.
Gating the MCP publish action behind verify-live guarantees that we only publish verified images. The OIDC permission configuration and structural workflow tests in test_ci_workflows.py are clean and well-crafted. Approved.
kuenstlichedummheit-sys
left a comment
There was a problem hiding this comment.
Keyless OIDC is definitely the way to go—zero long-lived PATs floating around in secrets. Clean separation of the pre-publish gate. LGTM!
majorungustl
left a comment
There was a problem hiding this comment.
Automating this right off release tags saves us from having to run local CLI scripts every release. Simple and effective.
44b3497
MustermenschAlex
left a comment
There was a problem hiding this comment.
Re-reviewed after syncing with main and bumping to 2.7.2. Manifest, workflow, and release notes are consistent. Approved.
kuenstlichedummheit-sys
left a comment
There was a problem hiding this comment.
Rebase onto latest main and bump to 2.7.2 checked out fine. LGTM!
majorungustl
left a comment
There was a problem hiding this comment.
Still looking good. Re-approved for 2.7.2.
Summary
Add an automated GitHub Actions workflow (
.github/workflows/publish-mcp.yml) to automatically validate and publishtorproxy'sserver.jsonto the official Model Context Protocol (MCP) Registry (registry.modelcontextprotocol.io) upon pushing release tags (v*).Key Changes
.github/workflows/publish-mcp.ymltriggers on release tags (v*), gated by live image verification (verify-live), authenticates using GitHub Actions OIDC (id-token: write) under theio.github.hapheus/*namespace, and publishes viamcp-publisher.tests/unit/test_ci_workflows.pyto verifypublish-mcp.ymlconstraints.2.7.1across all synchronized single-source-of-truth files (pyproject.toml,docker/Dockerfile,server.json,uv.lock,CHANGELOG.md, anddocs/releases.md).Closes #134