Release v0.1.8

[aallan]

Cuts v0.1.8 so tonight's VeraBench sweep — all 60 problems rather than 36 — runs against an anchored, published release rather than a moving main.

Release machinery

• Version bumped across the six files scripts/check_version_sync.py binds: pyproject.toml, vera/__init__.py, README.md, both values in the docs/index.html badge, and uv.lock. Gate reports "Version 0.1.8 is consistent across 6 files."
• CHANGELOG [Unreleased] → [0.1.8] - 2026-07-27, a fresh empty [Unreleased] opened above it, [Unreleased] compare link retargeted to v0.1.8...HEAD, and a new [0.1.8]: v0.1.7...v0.1.8 reference added.
• HISTORY gains its row in the Stage 19/20 table.
• Site assets regenerated.

Deliberately not changed: the benchmark caveat on the landing page still reads "against Vera v0.1.7". That line records which release the currently-published VeraBench figures were measured on, not which release is current. It moves when a sweep against v0.1.8 has actually run — which is the point of cutting this tag first.

What v0.1.8 contains

59 commits since v0.1.7. No compiler behaviour changes beyond two checker fixes; this is largely a hygiene and tooling release.

Added	Vim and Neovim support (#1155, contributed by @chromy) — the only one of the three editor grammars that knows all ten effects
Changed	The ruff rule set is declared rather than inherited, with five defect-class rules adopted (#1166)
Security	brace-expansion 5.0.7 → 5.0.8 in the VS Code extension, closing GHSA-mh99-v99m-4gvg (high, DoS)
Fixed	E208 follows a let chain as E207 already did (#1160); the Binding provenance invariant is enforced rather than documented (#1164)
Documentation	The VS Code extension reaches the Marketplace (#1106); landing-page facts, the vera/README.md module map, and diagnostic since fields all gated against live sources

Gate

check_version_sync, check_doc_counts, check_site_assets, check_limitations_sync, check_conformance, check_examples, check_corpus_canonical, check_walker_coverage, check_diagnostic_fields, check_explicit_encoding, check_licenses — all pass. ruff check . and ruff check --select S vera/ clean, mypy vera/ clean, tests/test_release.py 47 passed, and the full suite via pre-commit.

check_doc_counts earned its place here: the first draft of the HISTORY row carried five issue links and the gate rejected it, since a version row takes one and secondary links belong in the CHANGELOG.

After merge

release.yml detects the version increase, builds, and pauses at the pypi environment for your approval; it then publishes, verifies the registry hashes, and creates the v0.1.8 tag and GitHub Release at the merge SHA. No manual tag, upload, or release command is part of this.

Summary by CodeRabbit

• Release
  • Released version 0.1.8.
  • Updated project version information and release references across public documentation.
  • Documented editor tooling, rule-set updates, and improved SQL checking behaviour in the release history.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 652da5d1-075e-4e2c-a5a9-528a9e6c0727

📥 Commits

Reviewing files that changed from the base of the PR and between d97a2c3 and 001bc6c.

⛔ Files ignored due to path filters (5)

• docs/index.html is excluded by !docs/**
• docs/index.md is excluded by !docs/**
• docs/llms-full.txt is excluded by !docs/**
• docs/llms.txt is excluded by !docs/**
• uv.lock is excluded by !**/*.lock, !uv.lock

📒 Files selected for processing (5)

• CHANGELOG.md
• HISTORY.md
• README.md
• pyproject.toml
• vera/__init__.py

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• aallan/vera-bench (manual)

---

📝 Walkthrough

Walkthrough

The release metadata is bumped from 0.1.7 to 0.1.8 across package declarations and documentation. Changelog comparison references, release history, and README status information are updated accordingly.

Changes

Release metadata

Layer / File(s)	Summary
Version declarations pyproject.toml, vera/__init__.py	The package metadata and runtime __version__ constant are updated to 0.1.8.
Release documentation CHANGELOG.md, HISTORY.md, README.md	Release entries, comparison links, project status, and the Stage 19/20 history row are updated for v0.1.8.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• aallan/vera#327: Updates the same runtime version constant used by version-dependent site assets.
• aallan/vera#750: Performs a similar release metadata update across package declarations and changelog documentation.
• aallan/vera#1151: Updates the same version and release documentation locations.

Suggested labels: compiler, docs

🚥 Pre-merge checks | ✅ 8

✅ Passed checks (8 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: a v0.1.8 release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Changelog Covers Public-Surface Changes	✅ Passed	PASS: git diff shows no changes under vera/cli.py, vera/errors.py, spec/, vera/lsp/, or vera/codegen/api.py; the new changelog section covers the release/docs-only edits.
Spec And Implementation Move Together	✅ Passed	Only version/docs metadata changed; no parser, checker, verifier, codegen, or spec files were modified.
Diagnostics Carry An Error Code	✅ Passed	No diagnostic definitions changed; the only touched diagnostic text cites existing E208/E207 codes, so nothing new lacks a stable code.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.1.8

---

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.81%. Comparing base (d97a2c3) to head (001bc6c).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1168   +/-   ##
=======================================
  Coverage   93.81%   93.81%           
=======================================
  Files          99       99           
  Lines       33457    33457           
  Branches      458      458           
=======================================
  Hits        31389    31389           
  Misses       2055     2055           
  Partials       13       13           

Flag	Coverage Δ
javascript	78.61% <ø> (ø)
python	95.54% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.