chore: bump version to 0.2.1 for first published release - #85
Conversation
The 0.2.0 tag failed to publish (release workflow referenced a non-existent setup-uv@v8, so the build aborted before PyPI/GHCR upload). Rather than re-point the public v0.2.0 tag, bump to 0.2.1 — which also now includes the i18n reports feature (#16) and the release-workflow fix (#84) that landed on main since. - pyproject.toml + __init__.py: 0.2.0 -> 0.2.1 - CHANGELOG: new [0.2.1] section noting i18n + the release fix, with a note that 0.2.0 never published; compare links updated. After merge, tag v0.2.1 on main to trigger the (now fixed) release pipeline. https://claude.ai/code/session_01KYcUxCGAHaTPrRHTzJCWQz
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThis PR bumps the MedCheck package version from 0.2.0 to 0.2.1 across all version declarations: the public ChangesVersion 0.2.1 Release
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Prepares the first published release,
v0.2.1.Why 0.2.1 (not re-tagging 0.2.0)
The
v0.2.0tag failed to publish — the release workflow referenced a non-existentsetup-uv@v8, so the build aborted before any PyPI/GHCR upload (nothing was published under 0.2.0). Rather than force-move the publicv0.2.0tag, we bump to 0.2.1, which also picks up everything that landed onmainsince the tag:Changes
pyproject.toml+src/medcheck/__init__.py:0.2.0→0.2.1CHANGELOG.md: new[0.2.1]section (notes that 0.2.0 never published, lists i18n + the release fix), compare links updated--versiontest reads__version__dynamically, so no test change needed.After merge
Tag
v0.2.1onmain(and optionally delete the stalev0.2.0tag/release) to trigger the now-fixed release pipeline → PyPI + GHCR.Validation
ruff✅ · CLI/version tests green. Version-only change.https://claude.ai/code/session_01KYcUxCGAHaTPrRHTzJCWQz
Generated by Claude Code
Summary by CodeRabbit
Chores
Documentation