chore: update vLLM to 0.10.0

[ptarasiewiczNV]

Overview:

Use newest vLLM release: https://github.com/vllm-project/vllm/releases/tag/v0.10.0

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• Chores
  • Updated the default vLLM version used in the build process and installation scripts to v0.10.0.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[ptarasiewiczNV]

/ok to test 7305cc9

[coderabbitai]

Walkthrough

The changes update the default vLLM version reference from a specific commit hash to the version tag "v0.10.0" in both the Dockerfile and the installation script. No other logic, structure, or exported entities were modified.

Changes

File(s)	Change Summary
container/Dockerfile.vllm, container/deps/vllm/install_vllm.sh	Updated default VLLM_REF from commit hash to "v0.10.0" tag

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A version tag, so crisp and clean,
Replaces hashes rarely seen.
Now vLLM builds with ease,
On "v0.10.0"—what a breeze!
The rabbit hops, the code is bright,
Simpler builds—what pure delight!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

🔭 Outside diff range comments (1)

container/deps/vllm/install_vllm.sh (1)

80-83: Help-text default is now stale.
The usage string still advertises the old commit hash (059d4cd). Update it to the same default you set in the variable so users are not misled.

-  --vllm-ref REF    Git reference to checkout (default: 059d4cd)
+  --vllm-ref REF    Git reference to checkout (default: v0.10.10)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ff92053 and 7305cc9.

📒 Files selected for processing (2)

• container/Dockerfile.vllm (1 hunks)
• container/deps/vllm/install_vllm.sh (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Mirror Repository to GitLab
• GitHub Check: Build and Test - vllm

[alec-flowers]

FYI @ptarasiewiczNV I rebased this, so if you need to pull it make sure to overwrite your local.