[Bugfix] Fix MoE BNB version

[jeejeelee]

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.

Purpose

Test Plan

Test Result

(Optional) Documentation Update

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[gemini-code-assist]

Code Review

This pull request updates the minimum required version of the bitsandbytes library for MoE models from 0.45.3 to 0.46.1. I recommend refactoring the duplicated version check logic to improve code maintainability and prevent future inconsistencies.

[gemini-code-assist]

This version check logic is duplicated in BitsAndBytesLinearMethod.__init__ (lines 172-174). This duplication makes maintenance harder, as a version bump requires changes in two places. This could lead to inconsistencies if one location is missed during an update. To improve maintainability and adhere to the DRY (Don't Repeat Yourself) principle, I recommend extracting this logic into a shared helper function.

import bitsandbytes
if bitsandbytes.__version__ < "0.46.1":
    raise ImportError("bitsandbytes version is wrong. Please install bitsandbytes>=0.46.1.")