Repository navigation
docs(whats-new): add release notes for v2.2.0 - #308
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Document v2.2.0 changes docs/whats-new.md |
Adds release notes for indexing and query options, watch behavior, stale-index warnings, index cleanup, reliability fixes, and the Tokio update. |
Priority:
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Other
Possibly related PRs
- VeraTools/vera#307: The release notes document the global directory option, grep context shorthand, watch index-root resolution, stale-index hints, and MCP
repoargument introduced in this PR. - VeraTools/vera#304: The release notes describe full-text-only indexing and removal of an index when a rebuild finds no indexable files.
- VeraTools/vera#305: The release notes describe quiet handling of early-closed output pipes on Linux and macOS.
Merge Risk: 
Minimal · up to 129b7
-
No actionable merge-blocking risk remains.
Pre-merge checks: 
5
-
Full details: Title check
-
Explanation
The title "docs(whats-new): add release notes for v2.2.0" matches the single changeset, which adds v2.2.0 release notes to docs/whats-new.md (+12 lines, no declaration changes). It names the file scope and the version, and it states the primary change. It does not list every covered item, which is expected for a title.
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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 @coderabbitai help to get the list of available commands.
Revera reviewStatus: complete — no accepted findings Checked: Checked each new release-note claim against the linked feature/MCP documentation, implementation references and tests, and the Tokio lockfile version; no introduced documentation defect found. Timing: total 67s · index 2.2s · lanes 65s · 1 phase(s) skipped revera · strategy baseline · models: investigator=gpt-6.1-sol@high |
Release notes for #303 to #307 and #309: keyword-only indexes,
vera index --dry-run,vera -Cand the MCPrepoargument (from @ple1n's use case in #302), grep-C,vera watchfrom subdirectories, the emptied-directory reindex fix, the BM25 writer lock fix, the broken-pipe fix, and the tokio advisory update. The heading assumes the next tag is v2.2.0 (new flags, no breaking changes). Merge after #309.Summary by CodeRabbit