chore: Migrate to uv; Bump required Python version to 3.14. - #66
Conversation
|
Warning Review limit reached
Next review available in: 54 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
WalkthroughThis PR migrates the docs tooling to Changesuv migration for docs tooling
Estimated code review effort: 3 (Moderate) | ~20 minutes 🚥 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 |
junhaoliao
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@taskfiles/deps/lock.yaml`:
- Around line 4-19: The user-facing tasks check-uv and update-uv in the task
definition should have descriptions so they show up clearly in task --list. Add
a concise desc: entry to each of these task definitions, keeping uv-lock
unchanged since it is internal, and use the task names as the identifying
anchors when updating the taskfile.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 23573a49-f953-42e6-87fc-e01a88aa559c
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (7)
README.mdpyproject.tomlrequirements.txttaskfile.yamltaskfiles/deps/lock.yamltaskfiles/deps/main.yamltaskfiles/docs.yaml
💤 Files with no reviewable changes (1)
- requirements.txt
8f47ff2 to
0f9ebb3
Compare
kirkrodrigues
left a comment
kirkrodrigues
left a comment
There was a problem hiding this comment.
For the PR title, how about adding backticks around uv?
junhaoliao
changed the title
uv; Bump required Python version to 3.14.
…e string Co-authored-by: kirkrodrigues <2454684+kirkrodrigues@users.noreply.github.com>
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
2 participants
Description
Migrate the docs taskchain from
requirements.txt+ ad-hoc venv bootstrap to UV-driven dependency management with behavior aligned to existing CLP/YScope task patterns.Key updates:
[project]and[tool.uv]) and replaced Python dependency source fromrequirements.txtwithpyproject.toml+uv.lockreferences in venv task sourcing.uv run --directory "{{.ROOT_DIR}}" --lockedand kept venv inbuild/venv.uv.requirements.txtfrom docs dependency bootstrapping, added UV lock metadata refresh.Checklist
Validation performed
Scenario 1: Verify modified task surface
Task: Ensure task discovery reflects updated and added uv tasks.
Command:
Output:
Explanation: confirms new lock tasks are present via the new
taskfiles/depsinclude.Scenario 2: Validate docs build path
Task:
docs:build(build+symlink path and dependency gating).Command:
Output:
Scenario 3: Validate docs clean target
Task:
docs:cleanCommand:
Output:
Scenario 4: Validate project-docs download via UV runtime
Task:
docs:download-projectsCommand:
Output:
Scenario 5: Validate UV lock check/update tasks
Task:
deps:lock:check-uvanddeps:lock:update-uvCommand:
Output:
Scenario 6: Validate release tar path after migration
Task:
docs:release-tarCommand:
Output:
Scenario 7: Validate docs serve path (expected timeout while host is live)
Task:
docs:servewith 25s timeout wrapperCommand:
Output:
Explanation: Serve command was expected to run continuously; timeout 25s terminates it once startup succeeded.
Summary by CodeRabbit
New Features
uvwith locked inputs.Chores
pyproject.tomlfor project metadata and documentation dependencies.uvand adjusted the listed Python prerequisites.uvlockfiles.