Skip to content

feat(ci): add MCP Registry automated publish workflow and bump version to 2.7.1 - #135

Merged
hapheus merged 2 commits into
mainfrom
feat/mcp-publish-workflow
Nov 10, 2026
Merged

hapheus merged 2 commits into
mainfrom
feat/mcp-publish-workflow

Conversation

@hapheus

@hapheus hapheus commented Nov 10, 2026

Copy link
Copy Markdown
Owner

Summary

Add an automated GitHub Actions workflow (.github/workflows/publish-mcp.yml) to automatically validate and publish torproxy's server.json to the official Model Context Protocol (MCP) Registry (registry.modelcontextprotocol.io) upon pushing release tags (v*).

Key Changes

  • Publish Workflow: .github/workflows/publish-mcp.yml triggers on release tags (v*), gated by live image verification (verify-live), authenticates using GitHub Actions OIDC (id-token: write) under the io.github.hapheus/* namespace, and publishes via mcp-publisher.
  • Structural CI Tests: Extended tests/unit/test_ci_workflows.py to verify publish-mcp.yml constraints.
  • Version Bump: Bumped version to 2.7.1 across all synchronized single-source-of-truth files (pyproject.toml, docker/Dockerfile, server.json, uv.lock, CHANGELOG.md, and docs/releases.md).

Closes #134

@MustermenschAlex MustermenschAlex left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 kuenstlichedummheit-sys left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
majorungustl previously approved these changes Nov 10, 2026

@majorungustl majorungustl left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automating this right off release tags saves us from having to run local CLI scripts every release. Simple and effective.

@MustermenschAlex MustermenschAlex left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-reviewed after syncing with main and bumping to 2.7.2. Manifest, workflow, and release notes are consistent. Approved.

@kuenstlichedummheit-sys kuenstlichedummheit-sys left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rebase onto latest main and bump to 2.7.2 checked out fine. LGTM!

@majorungustl majorungustl left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still looking good. Re-approved for 2.7.2.

@hapheus
hapheus merged commit 341b688 into main Nov 10, 2026
17 of 18 checks passed
@hapheus
hapheus deleted the feat/mcp-publish-workflow branch November 10, 2026 19:28
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.

feat(ci): add MCP Registry automated publish workflow

4 participants