-
Notifications
You must be signed in to change notification settings - Fork 171
[Klaud Cold] Update minimaxm2.5-fp4-b300-vllm vLLM image to v0.21.0 #1453
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
functionstackx
merged 3 commits into
main
from
update-minimaxm2.5-fp4-b300-vllm-v0.21.0
May 18, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 The new perf-changelog entry's description contains an automation-metadata annotation "(26d old)" that does not appear in any other entry in this file. All ~50+ other "Update image from to " entries follow the strict format without an age suffix; consider stripping the parenthetical so this line reads "Update vLLM image from v0.19.0-cu130 to v0.21.0" for consistency.
Extended reasoning...
What the bug is
The new entry added to
perf-changelog.yaml(line 2636) reads:The parenthetical
(26d old)is a freshness/age annotation produced by the automation that opened this PR — the same string appears verbatim in the PR description ("Bumps minimaxm2.5-fp4-b300-vllm from vllm/vllm-openai:v0.19.0-cu130 (26d old) to vllm/vllm-openai:v0.21.0"). It is automation metadata that escaped into the human-readable, version-controlled changelog.Why this is inconsistent with the rest of the file
perf-changelog.yamlhas a strong convention: every "Update …" description follows the shapeUpdate <framework> image from <oldver> to <newver>with no annotations. A grep for\(\d+d old\)across the entire file returns exactly one match — this new entry. Concrete comparison with the immediately preceding analogous entries:Update SGLang image from v0.5.11-cu130 to v0.5.12-cu130Update SGLang image from v0.5.10-rocm720-mi30x to v0.5.12-rocm720-mi30xUpdate SGLang image from v0.5.11-cu130 to v0.5.12-cu130Update vLLM image from v0.15.1 to v0.20.2Update vLLM ROCm image from v0.18.0 to v0.21.0None of these carry an age suffix.
Step-by-step proof
perf-changelog.yamland grep forUpdate vLLM image from— 19 matches across recent history.Update vLLM image from <oldver> to <newver>with no parenthetical.(26d old).(26d old)substring appears there, confirming it is automation freshness metadata copied verbatim rather than intentional changelog prose.Impact
Purely cosmetic. The file is YAML and the field is a free-text description, so this does not affect parsing, runtime, CI, or any downstream tooling I'm aware of. The only cost is a small inconsistency in a changelog that is otherwise uniformly formatted.
Suggested fix
Strip the parenthetical so the description reads:
Going forward, the automation that generates these changelog entries should strip the
(Nd old)suffix before emitting the description string.