fix(policy): allow uv in pypi preset#3368
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PyPI network preset configuration is updated to authorize the ChangesPyPI Preset Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
|
@pandas-studio can you add a DCO, please? |
|
Opened signed-off replacement PR #4569 with the same one-line policy change. This avoids rewriting the contributor branch to satisfy DCO. |
Summary
/usr/local/bin/uvto the pypi preset's allowed binaries so sandboxes using thepypinetwork preset can runuvdirectly.python3/pipunder/usr/binand/usr/local/binand complements the/sandbox/.uv/...paths already present.Motivation
The pypi preset already allows
python3andpipfrom/usr/local/bin, and references/sandbox/.uv/python/**/python*, butuvitself was missing. Sandboxes that installuvto/usr/local/bin/uv(per theuv_installoperational note: symlinks into/root/are unreachable, so the binary is copied to/usr/local/bin) were blocked from invoking it under this preset.Test plan
make checkpasses (policy YAML lint)pypipreset in a sandbox, runuv --versionand auv pip install— both should be permitted🤖 Generated with Claude Code
Summary by CodeRabbit
Release Notes
uvpackage manager alongside existing Python tooling.