chore(tui): sync uv.lock with pyproject dev extras (hw-05g2) - #258
Conversation
tui/uv.lock had drifted from pyproject.toml: the dev extras ruff==0.15.17, mypy==1.14.1, and types-PyYAML>=6.0 (added when the lint/typecheck gates landed in #44/#45/#48) were never locked, so a fresh `uv sync --extra dev` resolved outside the lockfile and CI/local environments could diverge. Regenerated with `uv lock` from tui/. The diff is purely additive: mypy 1.14.1, mypy-extensions 1.1.0, ruff 0.15.17, types-pyyaml 6.0.12.20260518. No pyproject changes were needed. Validation: `uv lock --check` passes; `uv sync --extra dev` resolves clean in a fresh venv; canonical unit suite (pytest -m "not terminal_e2e", 136 passed) plus ruff and mypy from the synced venv are all green.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
1 participant
Factory-authored (bead hw-05g2, polecat-discovered). tui/uv.lock had drifted from pyproject's dev extras — mypy, ruff, and types-PyYAML were missing from the lock, so a fresh
uv sync --extra devdidn't match CI's toolchain. Lock regenerated; refinery gates:uv lock --checkclean + 136 TUI unit tests pass.🤖 Generated with Claude Code
https://claude.ai/code/session_01EjWqH4FMkdczkSagzXw3dQ