v0.0.144 release prep (recovery — should have been in #649) by aallan · Pull Request #651 · aallan/vera

aallan · 2026-05-11T10:39:49Z

Summary

Recovery release PR for v0.0.144 — the release-prep work that should have been part of #649 (Tier A bug burn-down) but was missed. Per the project's established pattern since v0.0.8: release prep belongs in the feature PR; post-merge is tag + release ONLY. I broke that rule on #649; this PR is the recovery.

The substantive bug-fix work (#633 / #634 / #556 / #591) already landed in #649 → 75a3982. This PR contains only the release-prep + opportunistic limitations sweep — no code changes.

Release prep

Version bump across the six tracked sites (0.0.143 → 0.0.144):
- vera/__init__.py (__version__ + version)
- pyproject.toml
- README.md (active-development line: 143 → 144 releases, 3,796 → 3,803 tests)
- docs/index.html (hero version-link span)
- HISTORY.md (new row + "58 active development days" + "144 tagged releases")
- uv.lock
CHANGELOG cut — renamed ## [Unreleased] to ## [0.0.144] - 2026-05-11, added a fresh empty ## [Unreleased], and added the [0.0.144] link reference plus bumped the [Unreleased] link comparison base.

Limitations sweep

Live-state-verified all KNOWN_ISSUES.md, vera/README.md, and spec/* limitation entries via scripts/check_limitations_sync.py --check-states. Found three stale entries:

KNOWN_ISSUES.md — #595 Bug row removed (closed 2026-05-07 as completed). The runtime-workaround entry referencing it has been reworded to drop the now-redundant "closes macOS malloc abort during wasmtime cleanup after Ctrl-C-in-host-import #595" parenthetical (the workaround removal is now gated only on the upstream wasmtime-py PyPI release, not on macOS malloc abort during wasmtime cleanup after Ctrl-C-in-host-import #595 being closed since macOS malloc abort during wasmtime cleanup after Ctrl-C-in-host-import #595 is already closed).
KNOWN_ISSUES.md — #605 Documentation row removed (closed 2026-05-07 as completed; the decreases doc gap was fixed).
spec/00-introduction.md — #226 Typed holes row removed from the "Future Features" table (closed; typed holes shipped).

vera/README.md and all spec/* limitation tables (spec/06-contracts.md, spec/08-modules.md, spec/12-runtime.md) verified — no stale entries.

Validation

python scripts/check_version_sync.py — Version 0.0.144 is consistent across 6 files.
python scripts/check_doc_counts.py — Documentation counts are consistent (3803 tests, 29 files, 86 conformance, 34 examples, 25 hooks, 7 CI jobs).
python scripts/check_limitations_sync.py --check-states — Limitation tracking is consistent (with state check) (34 in KNOWN_ISSUES.md, 18 in vera/README.md, 4 across spec chapters).

Lesson learned (memory update)

feedback_git_workflow.md in long-term memory has been strengthened with absolute-rule language about release prep belonging in the feature PR, and explicit history of the two times this rule has been broken (v0.0.95 and v0.0.144). Future feature PRs will include version bump + CHANGELOG cut + HISTORY row + README/docs/index.html bump + uv.lock as the final commit before requesting review.

🤖 Generated with Claude Code

Summary by CodeRabbit

Bug Fixes
- Resolved compiler, interpolation, Unicode, HTTP and inference issues.
Chores
- Version bumped to v0.0.144.
- Test suite increased to 3,803 tests.
Documentation
- Changelog, HISTORY and README updated for v0.0.144.
- Roadmap trimmed: "Typed holes" removed from planned features and known-issues list pruned.

Recovery PR for the release-prep work that should have been part of #649 (Tier A bug burn-down) but was missed. Per the project's established pattern since v0.0.8: release prep belongs in the feature PR; post-merge is tag + release ONLY. I broke that rule on #649; this PR is the recovery. Release prep: - **Version bump** across the six tracked sites (0.0.143 → 0.0.144): `vera/__init__.py` (`__version__` + `version`), `pyproject.toml`, `README.md` (active-development line: 143 → 144 releases, 3,796 → 3,803 tests), `docs/index.html` (hero version-link span), `HISTORY.md` (new row + "58 active development days" + "144 tagged releases"), and `uv.lock`. - **CHANGELOG cut** — renamed `## [Unreleased]` to `## [0.0.144] - 2026-05-11`, added a fresh empty `## [Unreleased]`, and added the `[0.0.144]` link reference plus bumped the `[Unreleased]` link comparison base. Limitations sweep (KNOWN_ISSUES.md, vera/README.md, spec/*): - **KNOWN_ISSUES.md** — removed the `#595` Bug row (closed 2026-05-07; the runtime-workaround entry referencing it has been reworded to drop the now-redundant "closes #595" parenthetical, since #595 was closed independently of the workaround being removed). Removed the `#605` Documentation row (closed 2026-05-07; `decreases` doc gap fixed). - **spec/00-introduction.md** — removed the `#226 Typed holes` row from the "Future Features" table (closed; typed holes shipped). - **vera/README.md** — checked, no stale references. - **spec/06-contracts.md**, **spec/08-modules.md**, **spec/12-runtime.md** limitation tables — all entries verified open via `scripts/check_limitations_sync.py --check-states`. All consistency checks green: - `python scripts/check_version_sync.py` — 0.0.144 consistent across 6 files - `python scripts/check_doc_counts.py` — counts consistent - `python scripts/check_limitations_sync.py --check-states` — 34 in KNOWN_ISSUES.md, 18 in vera/README.md, 4 across spec chapters; all live-state-verified No code changes. Pure release-prep + limitations-table sweep. Co-Authored-By: Claude <noreply@anthropic.invalid>

coderabbitai · 2026-05-11T10:40:02Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 83eea6f6-a7c2-46d2-979e-295ce27ab3f7

📥 Commits

Reviewing files that changed from the base of the PR and between 27198d2 and 3499fe4.

📒 Files selected for processing (1)

HISTORY.md

📝 Walkthrough

Walkthrough

Release Vera v0.0.144: bumped version metadata, added a v0.0.144 changelog and HISTORY entry (2026-05-11), removed bug #595 from KNOWN_ISSUES and its closure note, deleted "Typed holes" from spec, and updated README project-status metrics.

Changes

Release v0.0.144 documentation and version bump

Layer / File(s)	Summary
Version metadata constants `vera/__init__.py`, `pyproject.toml`	`__version__` and `version` updated from `0.0.143` → `0.0.144`.
Changelog release entry and reference links `CHANGELOG.md`	Inserted `## [0.0.144] - 2026-05-11` below `## [Unreleased]`; updated bottom compare links so `[Unreleased]` compares `v0.0.144...HEAD` and added `[0.0.144]` for `v0.0.143...v0.0.144`.
Release history and timeline `HISTORY.md`	Incremented active development days (57 → 58), added concise Stage 12 `v0.0.144` entry, and shortened preceding `v0.0.142`/`v0.0.143` text.
Known issues and specification updates `KNOWN_ISSUES.md`, `spec/00-introduction.md`	Removed bug `#595` from Bugs table; removed "closes `#595`" from `host_sleep` workaround row; deleted "Typed holes" future-feature row.
Project status line `README.md`	Updated project status metrics: v0.0.143 → v0.0.144 and adjusted release/test counts accordingly.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related PRs

aallan/vera#477: Release/version bump with coordinated documentation changes (pyproject.toml, vera/init.py, CHANGELOG, HISTORY, README).
aallan/vera#600: Edits to KNOWN_ISSUES.md runtime-workarounds for host_sleep / wasmtime-py KeyboardInterrupt trampoline handling.
aallan/vera#339: Release documentation PR modifying CHANGELOG.md, README.md, pyproject.toml, and vera/init.py for version consistency.

Suggested labels

compiler, spec, docs

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the primary change: a v0.0.144 release preparation that was inadvertently omitted from PR `#649`.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch release-v0.0.144

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

codecov · 2026-05-11T10:41:37Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.95%. Comparing base (75a3982) to head (3499fe4).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #651   +/-   ##
=======================================
  Coverage   90.95%   90.95%           
=======================================
  Files          59       59           
  Lines       23197    23197           
  Branches      259      259           
=======================================
  Hits        21098    21098           
  Misses       2092     2092           
  Partials        7        7

Flag	Coverage Δ
javascript	`57.36% <ø> (ø)`
python	`94.73% <100.00%> (ø)`

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

☔ View full report in Codecov by Sentry.
📢 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.

The three recent Stage 12 entries (added during v0.0.142, v0.0.143, and now v0.0.144) drifted into multi-paragraph mechanism descriptions — that level of detail belongs in CHANGELOG, not HISTORY. Compare against Stage 1 through Stage 8 entries (and the earlier v0.0.139 / v0.0.140 / v0.0.141 entries in Stage 12 itself) — those are all short one-sentence "what shipped at a glance" cells linking the closing issues. Trimmed: - v0.0.142: "Closed the #602 bug class structurally across four sites — [#630], [#632], [#635], [#636]." - v0.0.143: "Windows added to CI matrix as fully-strict — closes [#640], [#641], [#642]." - v0.0.144: "Tier A bug burn-down — closes [#633], [#634], [#556], [#591]." The detailed rationale for each (mechanism, scope, CodeRabbit findings, etc.) is already in CHANGELOG under its respective `## [0.0.X]` section, where it belongs. Co-Authored-By: Claude <noreply@anthropic.invalid>

aallan merged commit a983a00 into main May 11, 2026
23 checks passed

aallan deleted the release-v0.0.144 branch May 11, 2026 11:03

This was referenced May 11, 2026

Small docs sweep: #557 + #561 + #560 + #607 + #608 + #512 #650

Merged

Fix mono-suffix bug for FnType-alias SlotRef args + release v0.0.145 #659

Merged

This was referenced May 19, 2026

Release v0.0.156 #688

Merged

Release v0.0.157 #690

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

v0.0.144 release prep (recovery — should have been in #649)#651

v0.0.144 release prep (recovery — should have been in #649)#651
aallan merged 2 commits into
mainfrom
release-v0.0.144

aallan commented May 11, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented May 11, 2026 •

edited

Loading

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested labels

Uh oh!

codecov Bot commented May 11, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

aallan commented May 11, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Release prep

Limitations sweep

Validation

Lesson learned (memory update)

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented May 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested labels

Uh oh!

codecov Bot commented May 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

aallan commented May 11, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented May 11, 2026 •

edited

Loading

codecov Bot commented May 11, 2026 •

edited

Loading