release: v0.1.7 — SQL injection won't compile + docs sweep - #1151
Conversation
Cut v0.1.7 — the SQL-injection-as-a-compile-time-error release: the built-in `<DB>` effect (#229) plus the literal-provenance checker (#309) that makes SQL injection a compile-time error (E207/E208/E209), the bare-effect-op routing check (#1148, E217), and the Float64 rounding-assertion CI-flake fix (#1121). Release machinery: - Version 0.1.6 -> 0.1.7 across pyproject.toml, vera/__init__.py, README.md, docs/index.html, and uv.lock (the check_version_sync 6-file surface). - CHANGELOG [Unreleased] -> [0.1.7] (2026-07-24), fresh empty [Unreleased], and the compare-link references updated. - HISTORY v0.1.7 one-liner row in the current Stage 19/20 table. - Regenerated site assets (llms.txt, llms-full.txt, index.md, docs/SKILL.md). Documentation sweep: - spec/09 built-in-effects summary aligned with the shipped set (Async, Inference, HttpServer, DB), replacing the stale "future effects for concurrency and LLM inference" wording. - Removed the now-shipped #309 (contract-verified SQL) from the ROADMAP standard-library horizon. - Dropped the fixed #1121 row from the KNOWN_ISSUES bugs table (it ships in this release; caught by check_limitations_sync --check-states). - Filed #1150 for the drifted, ungated vera/README module-map line counts and tracked it under ROADMAP compiler-internals. No compiler behaviour changes — docs, version metadata, and generated site assets only. Co-Authored-By: Claude <noreply@anthropic.invalid>
📝 WalkthroughWalkthroughVera is updated from v0.1.6 to v0.1.7 across package metadata and project status. Release history, changelog references, standard-library documentation, roadmap entries, and the known-issues snapshot are aligned with the new release. Changesv0.1.7 release alignment
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 6 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (6 passed)
✨ 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 #1151 +/- ##
=======================================
Coverage 93.80% 93.80%
=======================================
Files 99 99
Lines 33434 33434
Branches 458 458
=======================================
Hits 31364 31364
Misses 2057 2057
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:
|
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 `@spec/09-standard-library.md`:
- Line 11: Update the built-in effects description in the standard-library
specification to describe Async as supporting asynchronous or concurrent
computation while explicitly noting that the reference executor currently
evaluates it eagerly and sequentially, without runtime concurrency.
🪄 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: 889d4e7b-1393-4bc7-915b-518790cbf28d
⛔ 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 (8)
CHANGELOG.mdHISTORY.mdKNOWN_ISSUES.mdREADME.mdROADMAP.mdpyproject.tomlspec/09-standard-library.mdvera/__init__.py
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
aallan/vera-bench(manual)
💤 Files with no reviewable changes (1)
- KNOWN_ISSUES.md
v0.1.7 — SQL injection won't compile
The sprint-closing release. The headline is the flagship guarantee: SQL injection is a compile-time error. Everything that ships in it already merged to
mainon its own PR; this PR cuts the version and does the release-wide documentation sweep.What's in the release
<DB>effect (#229) —query/executeagainst a host SQLite database,Array<Option<String>>positional parameters (SQLNULL=None), host-backed and configured byVERA_DB_URL.DB.query/DB.executemust be literal-provenance; a runtime-derived query isE207, a placeholder/parameter mismatchE208, a numbered/named placeholderE209. A deterministic type error, no solver. Hardened across three external adversarial reviews and two self-authored workflow rounds (a SEVERE generic-parameter launder caught before merge).E217) — a bare op the backend can't route is now a clean checker error instead of a confusingvera compilefailure.verifieda hard failure.Release machinery
0.1.6→0.1.7across thecheck_version_syncsurface (pyproject,vera/__init__.py, README,docs/index.html,uv.lock).[Unreleased]→[0.1.7](2026-07-24) + fresh[Unreleased]+ compare-link refs.llms.txt,llms-full.txt,index.md,docs/SKILL.md).Documentation sweep
Async,Inference,HttpServer,DB) — the "future effects for concurrency and LLM inference" wording predated them.#309from the ROADMAP standard-library horizon.#1121row from KNOWN_ISSUES (caught bycheck_limitations_sync --check-states).docs/index.html, SKILL, and the spec, with current limitation rows; no stale example/test workarounds.vera/READMEmodule-map line counts (tracked under ROADMAP compiler-internals rather than hand-patched).No compiler behaviour changes — docs, version metadata, and generated site assets only.
Merge is yours; the release tag + PyPI publish are handled by the GitHub Actions release workflow on the version bump.
🤖 Generated with Claude Code
Summary by CodeRabbit
DBbuilt-in effect.