chore: remove stale alias pointing to deepseek-flash - #1219
Merged
Conversation
Contributor
|
✅ OpenCodeReview: Review complete: 0 finding(s) across 2 selected item(s). |
Contributor
Author
|
@Qiyuanqiii I have considered all of the points you made upon creation, but I still created this. But we will see and get this reopened when that route is removed. I created this despite knowing the compatibility route. And I belief DeepSeek will not serve LLM goes forwards, not backwards. This is a part of the OCR concept. The timeout is 15 days. |
Contributor
Author
|
@Qiyuanqiii I think you have a misunderstanding of the compatibility route. Or is it me?
Which one is yours? |
Contributor
Author
|
What models list? I had problem understanding. |
Contributor
Author
|
@Qiyuanqiii Please 👍 if you don't have any doubts or questions. Let me know, thanks. |
stay-foolish-forever
approved these changes
Sep 14, 2026
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.
Description
There is a stale pointer named

deepseek-v4-flashpointing to the newdeepseek-flash.Per the docs:
Therefore the
deepseek-v4-flashshould be removed, because it will always points towards to the new model.The last PR updating the models list is incomplete.
deepseek-v4-prois not effected because per the docs deepseek said it still supports v4 pro modelType of Change
How Has This Been Tested?
make testpasses locallyChecklist
go fmt,go vet)No AI used in any way
Related Issues
N/A