Skip to content

[Klaud Cold] Update minimaxm2.5-fp4-b200-vllm vLLM image to v0.21.0#1448

Merged
functionstackx merged 3 commits into
mainfrom
update-minimaxm2.5-fp4-b200-vllm-v0.21.0
May 18, 2026
Merged

[Klaud Cold] Update minimaxm2.5-fp4-b200-vllm vLLM image to v0.21.0#1448
functionstackx merged 3 commits into
mainfrom
update-minimaxm2.5-fp4-b200-vllm-v0.21.0

Conversation

@functionstackx
Copy link
Copy Markdown
Collaborator

Summary

  • Bumps minimaxm2.5-fp4-b200-vllm from vllm/vllm-openai:v0.19.0-cu130 (25 days old) to vllm/vllm-openai:v0.21.0.

Test plan

  • Full sweep passes with full-sweep-enabled label.

🤖 Generated with Claude Code

@github-actions
Copy link
Copy Markdown
Contributor

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.

@github-actions
Copy link
Copy Markdown
Contributor

@functionstackx functionstackx changed the title Update minimaxm2.5-fp4-b200-vllm vLLM image to v0.21.0 [Klaud Cold] Update minimaxm2.5-fp4-b200-vllm vLLM image to v0.21.0 May 17, 2026
Copy link
Copy Markdown
Contributor

@claude claude Bot left a comment

Choose a reason for hiding this comment

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

LGTM — straightforward vLLM image version bump for minimaxm2.5-fp4-b200-vllm with corresponding perf-changelog entry.

Extended reasoning...

Overview

This PR bumps the Docker image for the minimaxm2.5-fp4-b200-vllm recipe from vllm/vllm-openai:v0.19.0-cu130 to vllm/vllm-openai:v0.21.0 in .github/configs/nvidia-master.yaml and adds a corresponding entry in perf-changelog.yaml. Only two lines of meaningful change.

Security risks

None. The change is a Docker image tag bump pointing to an official upstream vLLM image, consistent with several recent similar PRs in this repo (#1404, #1394, #1416).

Level of scrutiny

Low. This is a mechanical config change following an established pattern of version bumps. The PR is labeled full-sweep-enabled so the full perf sweep will validate runtime correctness.

Other factors

No bug hunting findings. The recipe-reminder bot comment is the standard auto-posted notice and not a blocker. Matches the pattern of prior approved image-bump PRs.

@github-actions
Copy link
Copy Markdown
Contributor

@functionstackx
Copy link
Copy Markdown
Collaborator Author

/reuse-sweep-run

@functionstackx functionstackx merged commit 82914ea into main May 18, 2026
3 of 5 checks passed
@functionstackx functionstackx deleted the update-minimaxm2.5-fp4-b200-vllm-v0.21.0 branch May 18, 2026 05:25
@github-actions
Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Development

Successfully merging this pull request may close these issues.

1 participant