Skip to content

chore(deps): widen crewai-cli uv pin - #7644

Open
FanouZeng-TT wants to merge 1 commit into
crewAIInc:mainfrom
FanouZeng-TT:fix/cli-uv-runtime-dependency
Open

FanouZeng-TT wants to merge 1 commit into
crewAIInc:mainfrom
FanouZeng-TT:fix/cli-uv-runtime-dependency

Conversation

@FanouZeng-TT

Copy link
Copy Markdown

Related issue

Fixes #7633

Summary

  • align crewai-cli's runtime uv requirement with the workspace's existing uv>=0.11.15,<1 constraint
  • remove the <0.12 ceiling imposed by uv~=0.11.6
  • keep the workspace lock metadata in sync

The previous CLI requirement allowed uv versions below the repository's GHSA-4gg8-gxpx-9rph security floor and capped every consumer environment below uv 0.12. Reusing the workspace constraint preserves uv as an installed CLI prerequisite while applying the security floor and compatibility range already selected by this repository.

Verification

  • Tests added or updated for the changed behavior — not applicable; this is dependency metadata only, verified through lock resolution and built wheel metadata

  • Relevant tests and quality checks pass locally

  • uv lock --check — passed

  • uv run pre-commit run --files lib/cli/pyproject.toml uv.lockuv-lock passed; Python-only hooks skipped these metadata files

  • uv build --package crewai-cli --out-dir /tmp/crewai-cli-dist — passed

  • built wheel metadata contains Requires-Dist: uv<1,>=0.11.15

  • uv export --package crewai-cli --no-dev --no-emit-project --no-annotate --no-header resolves uv==0.11.19 under the repository's pinned package cutoff

Additional context

No functional Python code changed. The generated uv.lock diff only updates the crewai-cli requirement; it does not upgrade unrelated packages or change the lockfile cutoff.

🤖 Generated with Claude Code

Align the CLI package requirement with the workspace's patched uv floor. The old compatible-release pin capped consumer environments below uv 0.12 and allowed releases below the security floor.
@FanouZeng-TT

Copy link
Copy Markdown
Author

Per the contribution guide's AI-generated contribution requirement, could a maintainer please add the llm-generated label? External contributors cannot apply repository labels directly.

@coderabbitai

coderabbitai Bot commented Sep 20, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 3d595e7f-7656-48e0-ae1a-d0d67435e56d

📥 Commits

Reviewing files that changed from the base of the PR and between 0374c63 and d4d4b81.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • lib/cli/pyproject.toml

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.


📝 Walkthrough

Walkthrough

The CLI’s uv dependency now requires version 0.11.15 or newer and remains below version 1.0. A comment records the related security advisory.

Changes

UV dependency constraint

Layer / File(s) Summary
Update CLI uv requirement
lib/cli/pyproject.toml
The requirement changes from uv~=0.11.6 to uv>=0.11.15,<1. The declaration includes a comment referencing GHSA-4gg8-gxpx-9rph.

Suggested reviewers: lorenzejay

Priority: ➖ Normal

Severity of issue fixed: Medium

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the primary change: widening the crewai-cli uv dependency constraint.
Description check ✅ Passed The description includes the required related issue, summary, verification results, and additional context. It explains why the dependency constraint changed and documents the completed checks.
Linked Issues check ✅ Passed The change satisfies issue #7633's minimum coding objective. lib/cli/pyproject.toml changes uv~=0.11.6 to uv>=0.11.15,<1. This removes the <0.12 cap and applies the security floor while retain…
Out of Scope Changes check ✅ Passed The reviewed change is limited to the uv dependency declaration and its explanatory comment in lib/cli/pyproject.toml, both of which directly support issue #7633. No unrelated Python code or featu…
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@david-long1

Copy link
Copy Markdown

Issue author here — this matches the minimum fix I proposed in #7633 exactly. I independently got the same result: uv lock --check clean with uv 0.11.3 (the version CI pins) and Requires-Dist: uv<1,>=0.11.15 in the built wheel. Happy to see this land.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] crewai-cli's runtime pin uv~=0.11.6 installs a second, capped uv into every consumer .venv

2 participants