Skip to content

pin LMCache to v0.3.9 or greater with vLLM v0.15.0 #33440

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
mgoin merged 2 commits into from
Feb 1, 2026
Merged

pin LMCache to v0.3.9 or greater with vLLM v0.15.0 #33440

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
325a18e
pin LMCache to v0.3.9 or greater with vLLM v0.15.0
Gregory-Pereira Jan 30, 2026
87332f8
Merge branch 'main' into pin-lmcache-version-for-vllm-v0.15.0-compat
mgoin Feb 1, 2026
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 requirements/kv_connectors.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
lmcache
lmcache >= 0.3.9

@gemini-code-assist gemini-code-assist Bot Jan 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

To prevent potential future breakages, it's safer to constrain the upper bound of the lmcache version. A new major release of lmcache (e.g., 0.4.0) could introduce backward-incompatible API changes, similar to the issue this PR is fixing. I suggest pinning the version to the current minor release series to improve dependency stability.

lmcache >= 0.3.9, < 0.4.0

nixl >= 0.7.1 # Required for disaggregated prefill
Loading