chore: migrate from poetry to uv - #103
Conversation
|
@CodeRabbit review |
✅ Action performedReview finished.
|
|
Warning Review limit reached
Next review available in: 51 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe project migrates from Poetry-based management to uv, Ruff, mypy, and Task. Docker builds use Python 3.13 and locked uv dependencies, while CI, Dependabot, pre-commit, Compose, and development documentation are updated. ChangesTooling and Container Workflow
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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 @.github/workflows/python.yml:
- Line 23: Update the actions/checkout step to disable credential persistence by
setting persist-credentials to false, and retain the workflow’s job permissions
at contents: read unless a documented write operation requires broader access.
In `@Dockerfile`:
- Around line 1-16: Update the Dockerfile to create a dedicated unprivileged
runtime user, grant that user ownership or necessary read/write access to /code
and required runtime paths after copying and dependency setup, then add a USER
directive before the application runs so the container no longer defaults to
root.
🪄 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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 0e5bf7fa-2362-43fd-a868-8a1c01689837
⛔ Files ignored due to path filters (2)
poetry.lockis excluded by!**/*.lockuv.lockis excluded by!**/*.lock
📒 Files selected for processing (10)
.dockerignore.github/dependabot.yml.github/workflows/python.yml.pre-commit-config.yamlDockerfileMakefileREADME.mdTaskfile.ymldocker-compose.ymlpyproject.toml
💤 Files with no reviewable changes (2)
- docker-compose.yml
- Makefile
Summary by CodeRabbit
Developer Experience
Build & Deployment
Documentation