chore: bump version to 0.2.0.dev0 after 0.1.0 release - #906
Merged
Conversation
Post-release development-version bump (Step 14). Opens the 0.2.0 development cycle. uv.lock is included alongside pyproject.toml because the lock pins the package's own version and must match, or uv lock --check fails CI.
potiuk
marked this pull request as ready for review
July 19, 2026 02:49
potiuk
added a commit
to potiuk/magpie
that referenced
this pull request
Jul 30, 2026
Every plugin manifest claimed version `0.2.0` while `pyproject.toml` sits at `0.2.0.dev0` (the post-0.1.0 bump, apache#906). Only `0.1.0` is tagged, so the manifests were advertising a release that does not exist yet — and the docs claimed they were "kept in sync with pyproject.toml", which they were not. Make `pyproject.toml`'s `project.version` the single authority and mirror it verbatim, `.devN` suffix included. The version now flows outward in two hops, neither hand-edited: pyproject.toml -> .claude-plugin/plugin.json, .codex-plugin/plugin.json, gemini-extension.json, apm.yml -> the 10 generated family manifests + 11 marketplace entries `check` fails on drift at either hop; `--fix` propagates both. A release bump is now one edit plus one command. Mirroring the PEP 440 string rather than translating it to a semver prerelease (`0.2.0-dev.0`) is deliberate: `release-prepare` step 2a bumps `version_manifest_files` by literal search/replace, which only works if every manifest carries the identical string — and dev versions are never published to a marketplace, so the suffix never reaches a consumer. `claude plugin validate --strict` accepts it, and hooks/check-upgrade.sh compares versions as opaque strings. Version rewrites are textual substitutions, not json.dumps() round-trips, so bumping does not reformat these hand-authored manifests (escaping em-dashes, expanding inline objects); each write is verified by re-parsing. Verified: `claude plugin validate . --strict` passes; simulating a bump to 0.3.0 propagates to all 25 version sites and is idempotent; prek passes (end-of-file-fixer skipped locally — sandbox denies it a write to an unrelated file).
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.
Post-release version bump after Apache Magpie 0.1.0 (Step 14 of the release-management lifecycle). Opens the 0.2.0 development cycle.
Changes
Version bump
pyproject.toml:0.1.0→0.2.0.dev0uv.lock:0.1.0→0.2.0.dev0(the lock pins the package's own version; it must matchpyproject.tomloruv lock --checkfails CI)Note on scope
version_manifest_filesinprojects/magpie/release-management-config.mdcurrently lists onlypyproject.toml, butuv.lockmust move in lockstep. Suggest addinguv.locktoversion_manifest_filesso future post-release bumps pick it up automatically — happy to do that in a follow-up (or here, if preferred).Opened as a draft per the release-prepare convention; ready for maintainer review.
Generated by
release-prepare(magpie-release-prepare).