Update vLLM version support to 0.18.0 - #5547
Conversation
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 85ed61e. Configure here.
albertvillanova
left a comment
There was a problem hiding this comment.
Thanks.
I know it used not to be case some time ago, but it seems all the latest vLLM releases work out of the box. What about removing the upper bound instead?
We should give it a try, yes (once we've caught up). Although I'm aware of future breaking changes for us, see vllm-project/vllm#39583 (bitsandbytes deprecation) |

it seems to work:
nothing special from the https://github.com/vllm-project/vllm/releases/tag/v0.18.0
Note
Low Risk
Low risk: updates version bounds and user-facing warnings/docs only, with no behavioral changes beyond allowing installs up to vLLM
0.18.0.Overview
Updates TRL’s vLLM support window to include vLLM
0.18.0by raising the max version in thetrl[vllm]optional dependency and aligning the runtimeis_vllm_availablecompatibility check/warning message.Documentation and a related compatibility patch comment are updated to reflect the new supported range (
0.11.0–0.18.0).Reviewed by Cursor Bugbot for commit 9a4e62f. Bugbot is set up for automated code reviews on this repo. Configure here.