release: bump version to 0.2.0#12
Merged
Merged
Conversation
Promote CHANGELOG [Unreleased] -> [0.2.0] (2026-06-01) and bump the version string in pyproject.toml, __init__.py, the server module docstring and the epl_server_info envelope. Prepares main for the v0.2.0 GitHub release, which triggers publish.yml -> PyPI (build reads the version from pyproject, so the bump must land before tagging). https://claude.ai/code/session_01CokY47qCb5iHuAfAEWdCvU
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.
Prepares
mainfor the v0.2.0 GitHub release.Changes
pyproject.toml:version0.1.0→0.2.0CHANGELOG.md: promote## [Unreleased]→## [0.2.0] - 2026-06-01(fresh empty[Unreleased]kept on top)src/bag_epl_mcp/__init__.py, theserver.pymodule docstring, and theepl_server_infoenvelopeWhy this must merge before tagging
.github/workflows/publish.ymltriggers on release published and builds withpython -m build, which reads the version frompyproject.toml— not the Git tag. Without this bump av0.2.0release would publish a0.1.0artifact to PyPI.Verification
python -m buildnow producesbag_epl_mcp-0.2.0-py3-none-any.whlAfter merge — manual release steps
v0.2.0(create on publish, targetmain).publish.yml→ PyPI (bag-epl-mcp 0.2.0).v1.0.0tag already exists (2026-03-31) — higher thanv0.2.0. Consider deleting/clarifying it so "latest release" isn't confusing.https://claude.ai/code/session_01CokY47qCb5iHuAfAEWdCvU
Generated by Claude Code