Release v0.1.9 - #1195
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (5)
📒 Files selected for processing (11)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
📝 WalkthroughWalkthroughThe release updates Vera to version 0.1.9. It updates package metadata, release records, diagnostics, conformance coverage, documentation metrics, and documentation-count validation. ChangesVera 0.1.9 release preparation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 8✅ Passed checks (8 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Adversarial review record (release machinery)Verdict: the diff is exactly release machinery plus one gated oracle hardening; no stray changes.
Per the standing instruction, this PR is converged and left for the maintainer to merge. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1195 +/- ##
=======================================
Coverage 93.79% 93.79%
=======================================
Files 99 99
Lines 34134 34134
Branches 458 458
=======================================
Hits 32017 32017
Misses 2104 2104
Partials 13 13
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/check_doc_counts.py`:
- Around line 841-852: Update the FAQ test-count validation around the regex
match in the check function so a missing headline pattern appends an explicit
error instead of silently skipping validation; retain the existing mismatch
error for matched counts. Add regression coverage for both a mismatched
documented count and an absent headline pattern, writing the failing tests
before implementing the check change.
🪄 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 Plus
Run ID: f842c484-f83c-4f9d-b52a-50ec7b97ad98
⛔ Files ignored due to path filters (5)
docs/index.htmlis excluded by!docs/**docs/index.mdis excluded by!docs/**docs/llms-full.txtis excluded by!docs/**docs/llms.txtis excluded by!docs/**uv.lockis excluded by!**/*.lock,!uv.lock
📒 Files selected for processing (6)
CHANGELOG.mdHISTORY.mdREADME.mdpyproject.tomlscripts/check_doc_counts.pyvera/__init__.py
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
aallan/vera-bench(manual)
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 266: Update the release total in the README description near the
active-development version from 205 to match the 203 tagged releases reported by
HISTORY.md, while preserving the existing v0.1.9 and other metrics. Validate the
documented 8,840-test count by running scripts/check_doc_counts.py in the
documented virtual environment.
🪄 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 Plus
Run ID: 0545bd83-7dc1-4b66-b1c6-ebfe932a20c3
⛔ Files ignored due to path filters (5)
docs/index.htmlis excluded by!docs/**docs/index.mdis excluded by!docs/**docs/llms-full.txtis excluded by!docs/**docs/llms.txtis excluded by!docs/**uv.lockis excluded by!**/*.lock,!uv.lock
📒 Files selected for processing (6)
CHANGELOG.mdHISTORY.mdREADME.mdpyproject.tomlscripts/check_doc_counts.pyvera/__init__.py
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
aallan/vera-bench(manual)
Converged — ready for your mergeFinal state at head
Per your instruction I have not merged this one. On your merge (merge commit, per the release convention), |
Cut the [Unreleased] section as 0.1.9: the declarable-trap purge. The reserved-name family completes (E153 grammar keywords with the handle carve-out, E152 built-in effects, E154 Vera-prefixed type names), `vera run` refuses dropped entries, imported functions' diagnostics and trap source maps name their own module, `decreases` is enforced at run time, and codegen skips propagate to transitive callers. Also hardens scripts/check_doc_counts.py: FAQ.md's headline test count is now pinned (it drifted silently through two releases because only the conformance half of the sentence was checked). Version 0.1.8 -> 0.1.9 across the check_version_sync.py surface; HISTORY row added to the Stage 19/20 table; site assets regenerated. Co-Authored-By: Claude <noreply@anthropic.invalid>
Re-converged at
|
1 participant
Release v0.1.9 — the declarable-trap purge
Cuts the accumulated
[Unreleased]section (16 fixes + 1 tooling addition) as v0.1.9. Everything in this release already merged tomainthrough its own reviewed PR; this PR carries only the release machinery plus one oracle hardening.What ships
The reserved-name family completes. A declarable-but-uncallable function is refused at its source: the grammar-keyword class joins
old/newunderE153with a named host-invoked carve-out forhandle(#1187, #1181), built-in effects cannot be redeclared (E152, #1149), andVera-prefixed type names are reserved for the prelude (E154).Entry points and attribution.
vera runrefuses a dropped entry instead of silently executing a sibling (#1183);[E602]diagnostics for imported bodies locate in their own module (#1186); runtime traps inside imported functions name the module's file (#1189);old()/new()misuse gets dedicated diagnostics (E030/E031, #1173).Soundness and codegen.
decreasesclauses are enforced at run time (#1172); codegen skips propagate to transitive callers (#1100);call_indirectis never emitted without a function table (#1185); type aliases are module-local in codegen (#1111) and a user alias cannot disable a prelude combinator (#1184).Docs and gates. The site fact gate (#1154), the VeraBench v0.0.18 section, and — new in this PR —
check_doc_counts.pynow pins FAQ.md's headline test count, which had drifted silently through two releases because only the conformance half of that sentence was checked (proven blind before the fix, mutation-validated after).Release machinery
0.1.8→0.1.9across thecheck_version_sync.pysurface (pyproject.toml,vera/__init__.py, docs badge, README status line, uv.lock) — verified: "Version 0.1.9 is consistent across 6 files."[Unreleased]→[0.1.9] - 2026-08-04with compare links updated; fresh empty[Unreleased].build_site.py); doc-counts oracle green (8,840 tests / 136 files / 176 conformance / 42 examples).bug-labelled issues after this release: exactly ch05_closure_nat_return trapped once in a full conformance run (unreproducible in ~960 attempts) — suspected rare runtime/GC flake in a CI gate #996 (the watched conformance flake), matching the KNOWN_ISSUES Bugs table one-to-one.Note for the maintainer
Per the standing instruction this PR is converged but not merged — CI green, CodeRabbit clean, adversarial review posted. Merge is yours (merge commit, per the release convention); the release workflow will detect the version increase on
main, build, pause at thepypienvironment for your approval, then tag and publish.🤖 Generated with Claude Code
Summary by CodeRabbit
Release
Documentation
Tests