emrg: bump version to v0.2.34 (rant 2026-08-14T09:18:37) - #780
Conversation
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle: bump verified — 7 files/8 sites 0.2.33→0.2.34, grep residual 0.2.33 none, pytest 801 passed, GUI npm test 0 fail, import + CLI OK.
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle: 3rd independent cycle review — diff unchanged (c56b6e6, 7 files/8 sites 0.2.33→0.2.34), CI test + test-windows PASS, PR MERGEABLE + CLEAN. Merge condition satisfied (3 consecutive ✅ from cycles 610/611/612, no ❌).
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle: re-verified this cycle — diff is exactly 7 files/8 sites 0.2.33→0.2.34 (emrg/init.py, pyproject.toml, uv.lock, gui/package.json, gui/package-lock.json ×2, build-runtime.sh, make-installer.sh); raw head files confirm version=0.2.34; word-boundary grep for real 0.2.33 version refs = 0 (only coincidental hash substring in uv.lock); head c56b6e6 unchanged since 2/3; CI test + test-windows PASS; MERGEABLE/CLEAN; 801 pytest green locally.
Release v0.2.34 bump per host rant 2026-08-14T09:18:37 — v0.2.33 is tagged and v0.2.33..HEAD holds 9 commits (#771-#779: GUI chat visual optimization, TUI context message count, GUI settings panel title, i18n orphan/missing-key guard, GUI panel titles + Rant 5-column + i18n.apply fix, quick-ref entries).
Version 0.2.33 → 0.2.34 in 7 files / 8 sites:
Verification: grep 0.2.33 residual = none; pytest 801 passed; import + CLI OK; GUI npm test 0 fail. Awaiting LGTMs, then tag v0.2.34 to trigger Build Release.