Repository navigation
[CI] Consolidate per-version model labels into vendor/family labels - #65753
Merged
WoosukKwon merged 2 commits intoNov 5, 2026
Merged
Conversation
Track models under their vendor (or family, for Kimi) instead of maintaining a label per model version: - Drop the DSv4 / DSv4.1 rules; DSv4 mentions now fold into the existing deepseek vendor label (file rules already covered the deepseek_v4 / deepseek_v41 trees). - Drop the k3 launch-triage rule; K3 mentions now fold into the kimi family label. - Apply the same changes to the issue_autolabel workflow. The DSv4, DSv4.1, k3 and Qwen3.5+ labels themselves (unused by automation after this change) can be deleted from the repo settings.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
The repo currently tracks a mix of vendor/family labels (
deepseek,qwen,minimax,kimi, …) and per-model-version labels (DSv4,DSv4.1,k3,Qwen3.5+). Every new model iteration requires new label automation, which has become diminishing returns. This consolidates labeling onto vendor/family labels (matching what SGLang does for new-model tracking):DSv4/DSv4.1rules —DSv4mentions in titles now fold into thedeepseekvendor label. The existingdeepseekfile rules already cover thevllm/models/deepseek_v4*/trees, so no coverage is lost.k3launch-triage rule —K3mentions now fold into thekimifamily label (the rule was already marked "retire after ramp-down").issue_autolabelworkflow for issues.mrv1-only/mrv2are Model Runner V1/V2 (engine internals), not model versions — left untouched.Qwen3.5+has no automation; it is a manual label only.Post-merge action for a maintainer
Delete the now-unused labels from repo settings:
DSv4,DSv4.1,k3,Qwen3.5+.Test Plan
node --check.DSv4 serving crash→deepseek,Deepseek V4.1 MTP regression→deepseek,K3 MTP acceptance rate low→kimi,Kimi K3 reasoning parser bug→kimi.