ci: Update vllm to 0.14.1 and override conflict

[thomasdhc]

Description

Usage

# Add snippet demonstrating usage

Checklist

• I am familiar with the Contributing Guide.
• New or Existing tests cover these changes.
• The documentation is up to date with these changes.

[greptile-apps]

_{2 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (2)

pyproject.toml
Global NumPy override risk

override-dependencies pins numpy>=2.0.0,<=2.2.0 unconditionally, which forces NumPy 2.x for all installs (not just the vLLM extra). That’s a much broader behavioral change than the PR title suggests and can break environments/dependencies that still require NumPy <2. If the intent is only to unblock a specific extra (e.g., vLLM/Numba), consider scoping the override via markers/extras or documenting that Curator now requires NumPy 2.x across the board.

---

uv.lock
Lockfile now enforces NumPy 2.x

The new override { name = "numpy", specifier = ">=2.0.0,<=2.2.0" } means the resolved environment will prefer NumPy 2.x (and in this lock it becomes numpy==2.2.0). If any supported runtime/extra still relies on NumPy 1.x ABI/API (common for compiled deps), installs using this lock will fail at import/build time. Before merging, it would be good to confirm the project’s supported dependency set is NumPy-2-compatible or to narrow the override to only the extras that need it.

[praateekmahajan]

@suiyoubi to verify before we merge

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}