docs: update README current version#155
Draft
vku2018 wants to merge 1 commit into
Draft
Conversation
se-jo-ma
self-requested a review
July 7, 2026 02:08
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
2 participants
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.
Closes #85.
Summary
Current versionline from0.1.5to0.2.4Validation
git tag | sort -V | Select-Object -Last 1reportedv0.2.4git diff --checkNote
The issue title/body mentioned
0.2.1, but the latest tag at edit time is nowv0.2.4, so this uses0.2.4with the leadingvstripped per the acceptance criteria. I also agree with the issue note that dropping the hardcoded line later may avoid future drift because the PyPI badge already auto-tracks the published package version.