Skip to content

Bump vllm from 0.7.2 to 0.23.0 in the pip group across 1 directory #693

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

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump vllm from 0.7.2 to 0.23.0 in the pip group across 1 directory #693

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
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ dependencies = [
dev = ["black~=25.1.0", "isort~=6.0.1", "pre-commit~=4.2.0"]
test = ["pytest~=8.4.0"]
evolve = ["ray", "cma", "lm_eval", "wandb"]
vllm = ["vllm==0.7.2", "lm_eval[vllm]"]
vllm = ["vllm==0.23.0", "lm_eval[vllm]"]

@cursor cursor Bot Jun 17, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vllm pin breaks in-memory evolve

High Severity

Pinning vllm==0.23.0 moves installs to the V1-only engine, while InMemoryMergeEvaluator still unwraps the legacy llm_engine layout (model_executor / driver_worker and model_runner.model) to hot-swap merged weights. With --vllm and in-memory scheduling, evaluation can fail with Unknown LLM engine type or broken weight updates.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit f483987. Configure here.


[project.urls]
repository = "https://github.com/cg123/mergekit"
Expand Down
Loading