Skip to content

chore: bump version to 0.2.1 for first published release - #85

Merged
Liohtml merged 1 commit into
mainfrom
claude/repo-issues-features-3ZLdb
Jun 11, 2026
Merged

chore: bump version to 0.2.1 for first published release#85
Liohtml merged 1 commit into
mainfrom
claude/repo-issues-features-3ZLdb

Conversation

@Liohtml

@Liohtml Liohtml commented Jun 11, 2026

Copy link
Copy Markdown
Owner

Prepares the first published release, v0.2.1.

Why 0.2.1 (not re-tagging 0.2.0)

The v0.2.0 tag failed to publish — the release workflow referenced a non-existent setup-uv@v8, so the build aborted before any PyPI/GHCR upload (nothing was published under 0.2.0). Rather than force-move the public v0.2.0 tag, we bump to 0.2.1, which also picks up everything that landed on main since the tag:

Changes

  • pyproject.toml + src/medcheck/__init__.py: 0.2.00.2.1
  • CHANGELOG.md: new [0.2.1] section (notes that 0.2.0 never published, lists i18n + the release fix), compare links updated
  • The CLI --version test reads __version__ dynamically, so no test change needed.

After merge

Tag v0.2.1 on main (and optionally delete the stale v0.2.0 tag/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

    • Released version 0.2.1
  • Documentation

    • Updated changelog for version 0.2.1

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
@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This PR bumps the MedCheck package version from 0.2.0 to 0.2.1 across all version declarations: the public __version__ constant, the pyproject.toml project metadata, and the CHANGELOG.md documentation with updated release comparison links.

Changes

Version 0.2.1 Release

Layer / File(s) Summary
Version bump and changelog update
src/medcheck/__init__.py, pyproject.toml, CHANGELOG.md
Public __version__ constant and pyproject.toml version field updated to 0.2.1; CHANGELOG.md sections restructured to move 0.2.1 release from Unreleased, and compare-link references updated from v0.2.0...HEAD to v0.2.1...HEAD with new [0.2.1] link added.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • Liohtml/MedCheck#77: Both PRs update the package version in pyproject.toml/src/medcheck/__init__.py and adjust CHANGELOG.md compare-link ranges as part of sequential release bumps.

Poem

🐰 A version bump, so clean and neat,
From 0.2.0 to 0.2.1 complete,
The changelog dances, links align,
Each file in sync—a design so fine! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: bumping the version to 0.2.1 for the first published release, which is the primary objective of the changeset.
Description check ✅ Passed The description is comprehensive and covers the reason for the version bump, changes made, and post-merge actions. However, it does not follow the repository's PR template structure with sections like Summary, Changes, Testing, and Additional Notes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/repo-issues-features-3ZLdb

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov

codecov Bot commented Jun 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@Liohtml
Liohtml merged commit 10fcde8 into main Jun 11, 2026
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants