Skip to content

bump flashinfer to v0.2.8 #21385

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.

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
merged 2 commits into from
Jul 24, 2025
Merged

bump flashinfer to v0.2.8 #21385

merged 2 commits into from
Jul 24, 2025

Conversation

cjackal
Copy link
Contributor

@cjackal cjackal commented Jul 22, 2025

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

Purpose

Bump flashinfer version in official vllm docker image to v0.2.8, the latest stable release.

flashinfer==0.2.8 includes a QoL update for nonstandard NVSHMEM location support, which is especially useful for vllm users experimenting with expert parallelism by stacking EP libraries on top of vllm docker image.

Test Plan

docker build CI is green

Test Result

TBD

Copy link

👋 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.

🚀

Signed-off-by: cjackal <44624812+cjackal@users.noreply.github.com>
Copy link
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 updates the flashinfer dependency version from a release candidate (v0.2.8rc1) to the final stable release (v0.2.8) within the Dockerfile. The change is minimal, correct, and aligns with the stated purpose of using the latest stable version of the library. I see no issues with this update.

@mergify mergify bot added the ci/build label Jul 22, 2025
@mgoin mgoin added the ready ONLY add when PR is ready to merge/full CI is needed label Jul 22, 2025
@mgoin
Copy link
Member

mgoin commented Jul 22, 2025

Thank you for the bump!

@cjackal
Copy link
Contributor Author

cjackal commented Jul 22, 2025

CI failures in basic model tests are fixed in #21375.

@cjackal
Copy link
Contributor Author

cjackal commented Jul 24, 2025

@mgoin It seems TPU test has timed out and all other tests pass.

@vllm-bot vllm-bot merged commit 526078a into vllm-project:main Jul 24, 2025
98 of 100 checks passed
@cjackal cjackal deleted the bump-flashinfer branch July 25, 2025 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/build ready ONLY add when PR is ready to merge/full CI is needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants