Skip to content

[V0 Deprecation] Remove VLLM_USE_V1 from docs and scripts#26336

Merged
DarkLight1337 merged 1 commit intovllm-project:mainfrom
DarkLight1337:remove-vllm-use-v1-doc
Oct 7, 2025
Merged

[V0 Deprecation] Remove VLLM_USE_V1 from docs and scripts#26336
DarkLight1337 merged 1 commit intovllm-project:mainfrom
DarkLight1337:remove-vllm-use-v1-doc

Conversation

@DarkLight1337
Copy link
Copy Markdown
Member

@DarkLight1337 DarkLight1337 commented Oct 7, 2025

Purpose

Remove VLLM_USE_V1 flag from all docs and scripts, apart from those that don't support V1:

Test Plan

Test Result


Essential Elements of an Effective PR Description Checklist
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
@DarkLight1337 DarkLight1337 added the ready ONLY add when PR is ready to merge/full CI is needed label Oct 7, 2025
@mergify mergify bot added documentation Improvements or additions to documentation ci/build deepseek Related to DeepSeek models performance Performance-related issues tpu Related to Google TPUs tool-calling kv-connector labels Oct 7, 2025
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request is a good step towards deprecating the V0 engine by removing the VLLM_USE_V1 environment variable from various documentation files and scripts. The changes are correct and align with the goal of making V1 the default engine.

However, the deprecation appears to be incomplete. The core Python logic for selecting the engine version and falling back to V0 still exists in the codebase, for instance in vllm/engine/arg_utils.py. This could be misleading, as it suggests V0 is still a fallback option. For example, the _raise_or_fallback function still contains the message "Falling back to V0".

To complete the deprecation, I recommend creating a follow-up pull request to remove this V0/V1 switching logic. This would likely involve simplifying create_engine_config to always use the V1 engine and updating _is_v1_supported_oracle to raise errors for unsupported features instead of attempting a fallback.

The changes within this pull request are correct for its stated scope, and I have no further comments on the modified files.

Copy link
Copy Markdown
Member

@hmellor hmellor left a comment

Choose a reason for hiding this comment

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

LGTM, one nit about TPU test naming

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maybe also rename these files to remove the V1? Also the job names in test pipeline?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I think that is just to keep the same naming convension as the "V1 Tests" we have now. We can move them in another PR.

@DarkLight1337 DarkLight1337 merged commit 7e4cd07 into vllm-project:main Oct 7, 2025
25 of 27 checks passed
@DarkLight1337 DarkLight1337 deleted the remove-vllm-use-v1-doc branch October 7, 2025 08:46
@github-project-automation github-project-automation bot moved this from In Progress to Done in V0 Deprecation Oct 7, 2025
Dhruvilbhatt pushed a commit to Dhruvilbhatt/vllm that referenced this pull request Oct 14, 2025
…ject#26336)

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
Signed-off-by: Dhruvil Bhatt <bhattdbh@amazon.com>
lywa1998 pushed a commit to lywa1998/vllm that referenced this pull request Oct 20, 2025
…ject#26336)

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
alhridoy pushed a commit to alhridoy/vllm that referenced this pull request Oct 24, 2025
…ject#26336)

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
rtourgeman pushed a commit to rtourgeman/vllm that referenced this pull request Nov 10, 2025
…ject#26336)

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
devpatelio pushed a commit to SumanthRH/vllm that referenced this pull request Nov 29, 2025
…ject#26336)

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci/build deepseek Related to DeepSeek models documentation Improvements or additions to documentation kv-connector performance Performance-related issues ready ONLY add when PR is ready to merge/full CI is needed tool-calling tpu Related to Google TPUs

Projects

Status: Done
Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants