Skip to content

build: Upgrade vLLM to 0.17.0 #610

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vivekkalyan merged 1 commit into from
Mar 11, 2026
Merged

build: Upgrade vLLM to 0.17.0 #610

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ backend = [
"pytest>=8.4.1",
"nbmake>=1.5.5",
"gql<4",
"vllm==0.15.1 ; sys_platform == 'linux'",
"vllm==0.17.0 ; sys_platform == 'linux'",
]
megatron = [
"torch>=2.8.0",
Expand Down Expand Up @@ -120,8 +120,8 @@ asyncio_mode = "auto"
[tool.uv]
required-version = ">=0.6.15"
# Override numpy to <2.0 for compatibility with megatron-core in the training
# environment. vLLM 0.15.1 pulls opencv-python-headless>=4.13 which wants
# numpy>=2 on Python 3.9+, but megatron-core requires numpy<2.
# environment. vLLM pulls opencv-python-headless>=4.13 which wants numpy>=2 on
# Python 3.9+, but megatron-core requires numpy<2.
override-dependencies = ["transformer-engine>=2.11.0", "numpy<2"]
# Keep apex build isolation enabled so uv can inject torch from
# `extra-build-dependencies` during lock/sync on non-GPU client machines.
Expand Down
Loading
Loading