chore: bump to v0.2.0 — first Phase-6 publish#8
Merged
Conversation
Bumps every version-bearing surface to 0.2.0 so the next `v0.2.0` tag push fires the release.yml workflow (built in PR #7) end-to-end: GH-Release with wheel attached, PyPI publish via Trusted Publisher OIDC, MCP-registry publish via GitHub OIDC. * pyproject.toml: version 0.1.0 → 0.2.0 * src/m_dev_tools_mcp/__init__.py: __version__ → "0.2.0" * server.json: top-level `version` + packages[0].version → "0.2.0" (release.yml rewrites both at publish time too, so the in-repo copy stays a current-state snapshot rather than a moving target) * dist/mcp-tools.json regen — the version field embeds the package version, so the drift gate catches a forgotten bump ### Verified locally * make check — ruff + mypy + 41/41 pytest + manifest + check-agents drift gates all clean * make build — produces dist/m_dev_tools_mcp-0.2.0-py3-none-any.whl * Fresh-venv install of the wheel exposes `m-dev-tools-mcp --version` → 0.2.0 ### What lands next (after merge) Push a v0.2.0 tag on main. release.yml fires.
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
Bumps every version-bearing surface to 0.2.0 so the next
v0.2.0tag push firesrelease.yml(built in PR #7) end-to-end: GH-Release with wheel attached, PyPI publish via Trusted Publisher OIDC, MCP-registry publish via GitHub OIDC.Changes
pyproject.toml:version0.1.0 → 0.2.0src/m_dev_tools_mcp/__init__.py:__version__→"0.2.0"server.json: top-levelversion+packages[0].version→"0.2.0"(the release workflow rewrites both at publish time too — keeping the in-repo copy current makes the snapshot honest)dist/mcp-tools.jsonregen — theversionfield embeds the package version, so the drift gate catches a forgotten bumpVerified locally
make checkclean — ruff + mypy + 41/41 pytest + manifest + check-agents drift gatesmake build→dist/m_dev_tools_mcp-0.2.0-py3-none-any.whlm-dev-tools-mcp --version→0.2.0Test plan
After merge
Push
v0.2.0tag onmain.release.ymlfires.Prereq:
m-dev-tools-mcpconfigured as a PyPI Trusted Publisher pointing at thisrelease.yml. Without it, the PyPI publish step fails visibly (not catastrophic — wheel still attaches to the GH Release;mcp-publisherstep may also fail because PyPI hasn't received the package).