fix: bump pinned uv from 0.11.29 to 0.12.1 - #44
Conversation
The central org coverage-evidence pipeline (ContextualWisdomLab/.github) hardcodes and hash-verifies exactly uv 0.12.1 as its trusted exporter. uv export --frozen refuses to run whenever the invoking uv's version does not match a project's own [tool.uv] required-version, so every coverage-evidence run against RankWeave failed with "Required uv version ==0.11.29 does not match the running version 0.12.1" regardless of the PR's own diff (ContextualWisdomLab/.github#1234) -- producing repeated false CHANGES_REQUESTED reviews on unrelated PRs (#40, #36, #41, #42, all dismissed with evidence this session). Bumps pyproject.toml and all four astral-sh/setup-uv workflow steps to match. uv.lock regenerated byte-identical under 0.12.1 (RankWeave has zero runtime dependencies, so the resolved closure is unaffected). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K8VWdPkLwNYHGAKWowfueJ
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough프로젝트의 필수 uv 버전을 Changesuv 버전 동기화
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This PR updates the pinned uv version used by project configuration and CI workflows, with the lockfile unchanged and the listed checks passing; no actionable merge-blocking risk remains beyond normal review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Summary
ContextualWisdomLab/.github) hardcodes and hash-verifies exactlyuv 0.12.1as its trusted exporter (scripts/ci/materialize_base_python_requirements.py,TRUSTED_UV_VERSION = "0.12.1").uv export --frozenrefuses to run whenever the invokinguv's version does not match a project's own[tool.uv] required-version-- realuvCLI behavior, not a bug in that script.==0.11.29, a structural (not transient) mismatch: every coverage-evidence run against this repo failed withRequired uv version ==0.11.29 does not match the running version 0.12.1, regardless of the PR's own diff. Precisely root-caused and tracked at ContextualWisdomLab/.github#1234 after it produced 4 falseCHANGES_REQUESTEDreviews on unrelated open PRs this session (Rewrite RankWeave README for customers and operators #40, fix(ci): restore executable hourly governance #36, docs: add product/technical gap baseline #41, docs: add ADR 0005 versioned public-API compatibility policy #42 -- all dismissed with evidence).pyproject.toml's[tool.uv] required-versionand all fourastral-sh/setup-uvworkflow steps (ci.ymlx2,create-release.yml,publish.yml) from0.11.29to0.12.1.uv.lockregenerated withuv 0.12.1and is byte-identical to the prior lock -- RankWeave has zero runtime dependencies (dependencies = []), so the resolved closure is unaffected by the uv version.Test plan
uv lockwithuv 0.12.1produces a byte-identicaluv.lock(git diff uv.lockis empty)python -m ruff check .cleanpython -m coverage run -m pytest -q && python -m coverage report-- 661 passed, 100% statement/branch coverageactionlinton all three modified workflow files -- no new findings (pre-existing shellcheck style nits only, unrelated to this diff)🤖 Generated with Claude Code
https://claude.ai/code/session_01K8VWdPkLwNYHGAKWowfueJ
Summary by CodeRabbit