-
Notifications
You must be signed in to change notification settings - Fork 186
[Klaud Cold] Update kimik2.5-int4-b300-vllm vLLM image to v0.21.0 #1457
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
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 changelog entry's description includes an inconsistent
(14d old)parenthetical that doesn't appear in any other entry inperf-changelog.yaml. Every other description in the file uses the clean patternUpdate {vLLM,SGLang,vLLM ROCm} image from vA to vB, and the14dage is relative to PR creation time so it becomes meaningless after merge. Suggest changing the description to"Update vLLM image from v0.20.0-cu130 to v0.21.0"for consistency.Extended reasoning...
What the issue is
The new entry added at
perf-changelog.yamllines 2632–2637 contains the description:- "Update vLLM image from v0.20.0-cu130 (14d old) to v0.21.0"The
(14d old)parenthetical is unique to this entry. Every other description inperf-changelog.yamlfollows the clean patternUpdate {vLLM,SGLang,vLLM ROCm} image from vA to vBwith no age annotation — see for example the immediately preceding entries at lines 2581, 2587, 2593, 2599, 2605, 2611, 2618, 2624, and 2630.Proof / verification
Running
grep -nE '\([0-9]+d old\)' perf-changelog.yamlreturns exactly one match: the new line 2636 added by this PR. The same(14d old)phrasing appears in the PR description ("Bumpskimik2.5-int4-b300-vllmfromvllm/vllm-openai:v0.20.0-cu130(14d old) to ..."), strongly suggesting it leaked into the changelog from the automated PR-generation pipeline that produces both the PR body and the changelog entry.Why it doesn't belong here
perf-changelog.yamlis a persistent, user-facing record of image bumps. "14 days old" is a value measured relative to PR creation time on 2026-05-17 — once merged, the relative age becomes meaningless and even misleading (a reader six months from now has no way to interpret it). The PR body is the right place for that context; the durable changelog should match the established pattern.Impact
Cosmetic / consistency only — no runtime effect. Worth fixing because the changelog is the canonical reference for these bumps and it's a one-line edit.
Fix
Change line 2636 to:
- "Update vLLM image from v0.20.0-cu130 to v0.21.0"