chore(release): v0.5.2 — publish the PyPI ownership marker for the MCP Registry - #6
Merged
Merged
Conversation
…P Registry Documentation and metadata only. No code, no schema, no dependency changes; install behaviour is identical to 0.5.1. The MCP Registry verifies ownership of a PyPI package by looking for an `mcp-name: <server name>` string in the package description, which is generated from README.md when the distribution is built. The marker and `server.json` landed on main after v0.5.1 was already tagged, so the published 0.5.1 description does not carry it and registry validation would reject the submission. This release exists solely to get the marker onto PyPI. `server.json` version fields are bumped in lockstep, since the registry entry must name a published version that carries the marker. Claude-Session: https://claude.ai/code/session_01Us8nLW5XexX1N28nb3dgUp
There was a problem hiding this comment.
🟢 Approval recommended
Changes are limited to consistent version/metadata updates and a changelog entry, with no functional code modifications.
Pull request overview
This PR prepares the v0.5.2 release by bumping version metadata across the Python package, MCP Registry server.json, and the changelog so the already-merged PyPI ownership marker/registry metadata can be published to PyPI.
Changes:
- Bump package version to
0.5.2inpyproject.tomlandsrc/topicforge/__init__.py. - Bump
server.jsonversion fields to0.5.2to match the release. - Add a
0.5.2changelog entry and update compare links.
File summaries
| File | Description |
|---|---|
| src/topicforge/init.py | Updates __version__ constant to 0.5.2. |
| server.json | Bumps registry metadata version fields to 0.5.2. |
| pyproject.toml | Updates project version to 0.5.2 for packaging. |
| CHANGELOG.md | Adds 0.5.2 release notes and updates compare links. |
Review details
- Files reviewed: 4/4 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Documentation and metadata only. No code, no schema, no dependency changes — install behaviour is identical to 0.5.1.
Why this release exists
The MCP Registry verifies ownership of a PyPI package by looking for an
mcp-name: <server name>string in the package description, which is generated fromREADME.mdat build time.The marker and
server.jsonlanded onmainafterv0.5.1was already tagged, so the published 0.5.1 description does not carry it — registry validation would reject the submission. Cutting this version is the mechanical prerequisite for getting TopicForge listed.Contents
pyproject.toml/__version__→0.5.2server.jsonversion fields bumped in lockstep (the registry entry must name a published version carrying the marker)[0.5.2]sectionserver.jsonand the README marker themselves are already onmain(commitfb18deb); this PR only publishes them.Verification
python -m ruff check src tests→ All checks passedpython -m pytest→ 484 passed, 24 skipped (unchanged)server.jsonre-validated against the registry's published JSON schema after the bumpAfter merge
v0.5.2→ PyPI publish (gated on thepypienvironment approval)mcp-publisher login github— device flow, requires entering a code on github.commcp-publisher publishThird-party directories (Glama, PulseMCP, mcp.so) largely harvest the official registry, so they come after this, not before.
https://claude.ai/code/session_01Us8nLW5XexX1N28nb3dgUp