emrg: bump version to v0.2.38 (rant 2026-08-14T22:11:26) - #794
Conversation
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle: bump verified 0.2.37→0.2.38 in 7 files / 8 refs, no stale 0.2.37 anywhere (grep exit 1 = clean), uv.lock only line 38 (no hash trap), pytest 810 + import + CLI green; CI test + test-windows pass.
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle (2nd ✅)
Full verification on the branch (head verified fresh):
- Version bump complete: 0.2.37 → 0.2.38 across 7 files / 8 refs —
emrg/__init__.py,pyproject.toml,gui/package.json,gui/package-lock.json×2,packaging/build-runtime.shfallback,packaging/make-installer.shfallback,uv.lock— exactly as declared in the PR body. - Zero stale refs: grep for 0.2.37 across emrg/ + packaging/ + pyproject.toml + uv.lock on the branch → 0 hits (no uv.lock pygments hash trap this time, as claimed).
- Import verified:
emrg.__version__= 0.2.38 on the branch. - No regression: full suite 810 passed (13.82s); import check +
emrg --helpOK. - CI green: test + test-windows both pass (run 31808538362); MERGEABLE/CLEAN.
Release content correct: #792 (proxy=None) + #793 (task wire type) both listed — matches master history 1c1d66a + 70d2209.
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle (3rd consecutive ✅, R1785)
Re-verified this cycle: head unchanged 3e5ef48 (no new commits since R1784 review — 7 files / 8 refs 0.2.37→0.2.38, zero stale refs, import 0.2.38, 810 passed, CI test+test-windows green, MERGEABLE/CLEAN). 3 consecutive ✅ from different cycles, no ❌ between — merging.
Host-directed release (rant 2026-08-14T22:11:26). Bump 0.2.37 → 0.2.38 across 7 files / 8 refs (emrg/init.py, pyproject.toml, gui/package.json, gui/package-lock.json ×2, build-runtime.sh, make-installer.sh, uv.lock:38).
Included since v0.2.37:
Verified: pytest 810 passed, import + CLI OK, no stale 0.2.37 refs (uv.lock has no pygments hash trap this time).