chore: release prep 0.2.0 — sync __version__, fold CHANGELOG - #13
Merged
Merged
Conversation
__version__ was still 0.1.0 while pyproject said 0.2.0, which release.yml refuses (it requires the two to match before tagging). 0.2.0 was never published to PyPI, so the background-CLI and Dockerfile work sitting under [Unreleased] folds into the 0.2.0 entry rather than taking a version of its own — 0.3.0 is reserved for the breaking fold in #11. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EMQxc7WjBTqdUJu18LAskK
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.
Release prep for
agentplane-control-plane0.2.0.control_plane/__version__was still0.1.0whilepyproject.tomlsaid0.2.0.release.yml:45refuses to tag when those disagree, so the release could not have run as-is.start/stop/status) and Dockerfile work under[Unreleased]folds into the 0.2.0 entry rather than claiming a version. 0.3.0 stays reserved for the breaking fold in 0.3.0: destructive cleanup — fold run_registrations, remove create_run + legacy ledger wrappers #11.[0.2.0]heading dated and retitled to match its contents.Verified the workflow's version gate with its own grep/sed: passes, tag resolves to
v0.2.0.🤖 Generated with Claude Code
https://claude.ai/code/session_01EMQxc7WjBTqdUJu18LAskK