Fix stale v0.0.100 version string and add README to version sync check#375
Merged
Conversation
Co-Authored-By: Claude <noreply@anthropic.invalid>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated README content (version bump, roadmap formatting, example invocation) and augmented the CI script Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested labels
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #375 +/- ##
=======================================
Coverage 90.30% 90.30%
=======================================
Files 49 49
Lines 19100 19100
Branches 220 220
=======================================
Hits 17248 17248
Misses 1848 1848
Partials 4 4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The issue links carry the meaning — strikethroughs are visual noise in prose. Co-Authored-By: Claude <noreply@anthropic.invalid>
Co-Authored-By: Claude <noreply@anthropic.invalid>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Line 603: The README states v0.0.101 but the project must keep version numbers
synchronized across all version-bearing files; open vera/__init__.py and set the
module __version__ to "0.0.101", open pyproject.toml and update the project
version = "0.0.101", and update CHANGELOG.md so the latest release header (and
any internal references) show v0.0.101 to match README.md; after editing run a
quick grep for "0.0." to ensure no other files still reference a different patch
version.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 3c7da5ac-5140-46cd-b9af-4561b71be272
📒 Files selected for processing (1)
README.md
The "active development at vX.Y.Z" string in README.md was not covered, which is how the v0.0.100 string slipped through to PR #375. Co-Authored-By: Claude <noreply@anthropic.invalid>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@scripts/check_version_sync.py`:
- Around line 44-50: The README version extraction currently logs a warning and
continues when no match is found; change this to fail the script: in the block
that reads README.md (variables readme, match, and versions["README.md"]), when
match is None print an error to stderr and call sys.exit(1) (or raise
SystemExit(1)) so the CI returns non-zero instead of omitting README.md from
versions.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: c33ad71e-1be9-42c0-a53d-51ae3825969e
📒 Files selected for processing (1)
scripts/check_version_sync.py
WARNING + continue means a missing match silently skips README.md from the version set, so the check can pass with a gap. Return 1 instead, matching the behaviour of the other required-file checks. Co-Authored-By: Claude <noreply@anthropic.invalid>
6 tasks
8 tasks
This was referenced May 6, 2026
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.
Two related fixes:
v0.0.100→v0.0.101scripts/check_version_sync.py: README.md was not included in the version sync check, which is how the stale string slipped through in the first place. Now checks all four version-bearing files:pyproject.toml,vera/__init__.py,docs/index.html, andREADME.mdMarkdown,Json,Http,Inferencesentence — the issue links carry the meaning, strikethroughs are visual noise in proseSummary by CodeRabbit
Documentation
Chores