chore: bump to v0.2.1 — retry Phase-6 publish after Trusted Publisher config#9
Merged
Conversation
… config v0.2.0 fired release.yml end-to-end and successfully built the wheel + cut the GH Release, but the PyPI step failed with `invalid-publisher` because the Trusted Publisher wasn't yet configured. Maintainer has now registered the Pending Publisher on PyPI; this bump re-fires the workflow on `v0.2.1` (PyPI versions are immutable — can't retry 0.2.0). Same three version-bearing surfaces as the prior bumps: * pyproject.toml: version 0.2.0 → 0.2.1 * src/m_dev_tools_mcp/__init__.py: __version__ → "0.2.1" * server.json: top-level version + packages[0].version → "0.2.1" * dist/mcp-tools.json regen (version field embed) Verified locally: * make check — ruff + mypy + 41/41 pytest + manifest + check-agents drift gates all clean. After merge: push v0.2.1 tag. release.yml fires; PyPI step should succeed this time, mcp-publisher publish runs after.
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
1 participant
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.
Summary
v0.2.0 (PR #8 /
6993cc2) firedrelease.ymlend-to-end and:v0.2.0live, wheel attached)invalid-publisher— TP not yet configuredmcp-publisher publishMaintainer has now registered the Pending Publisher on PyPI:
m-dev-tools-mcpm-dev-toolsm-dev-tools-mcprelease.ymlreleaseGitHub
releaseenvironment confirmed present on the repo.PyPI versions are immutable — can't retry
0.2.0, so this bump moves to v0.2.1.Changes
pyproject.toml:version0.2.0 → 0.2.1src/m_dev_tools_mcp/__init__.py:__version__→"0.2.1"server.json:version+packages[0].version→"0.2.1"dist/mcp-tools.jsonregen (theversionfield embeds the package version)Verified locally
make checkclean — ruff + mypy + 41/41 pytest + manifest + check-agents drift gates.Test plan
v0.2.1tag →release.ymlfires. Expected outcome: all four publish steps succeed;m-dev-tools-mcp0.2.1 live on PyPI + the MCP registry.