No functional change. Two release-plumbing defects, both found by publishing 2.0.0 for real rather than by reading the specification.
The MCP registry ownership marker was missing. The registry proves that a publisher controls a PyPI package by finding mcp-name: <server-name> in the package README. 2.0.0 shipped without it, and PyPI versions cannot be re-uploaded — so the fix costs a version. The publish workflow now checks for the marker before it waits on the release, not after.
The publish workflow assumed a tag ref. workflow_dispatch runs on a branch, so GITHUB_REF_NAME was main and every manual run died comparing a branch name against a version number. Tag and manual paths are handled separately now, and both verify that server.json, its package entry and pyproject.toml agree.
Both were verified against the published schema and a parsed workflow file before 2.0.0 went out. Neither check exercised the path that failed.
If you are on 2.0.0 there is nothing to do — the package behaves identically.