Repository navigation
Replace retired Qwen models and add DeepSeek - #9
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
DashScope retired
qwen3-maxandqwen-vl-plus, so chat, tools, claim review and image analysis were failing withmodel_not_found. This PR replaces the retired models and adds DeepSeek as its own provider.What changed
qwen3-maxand addedqwen3.8-max, the latest Qwen max modeldeepseekprovider:DEEPSEEK_API_KEY, plusDEEPSEEK_BASE_URLwith a default ofhttps://api.deepseek.com.deepseek-v4-pro, with text and tool capabilities.docker-compose.prod.yml, CI and the README useqwen3.8-max,deepseek-v4-proandqwen3-vl-plusinstead of the retired modelsTesting
qwen3.8-maxresolves.qwen3-maxinCHAT_MODELSnow fails at startup.deepseek-v4-prothroughcomplete_chatwith a real key. It worked and reported reasoning tokens.Deployment
Production was already fixed by changing config only, before this PR (revision 0000017):
CHAT_MODEL,TOOL_MODELandCLAIM_REVIEW_MODELareqwen-plus.VISION_MODELisqwen3-vl-plus.CHAT_MODELSisqwen-plus,qwen-max,kimi-k2.6.After this PR is merged and deployed:
deepseek-api-keyto the Container App, and setDEEPSEEK_API_KEYto read from it.qwen3.8-max,deepseek-v4-protoCHAT_MODELS.complete_chatwithrequested_model="deepseek-v4-pro"inside the container.Deploy the code before changing the config. The running code doesn't know
deepseek-v4-pro, and an unknown id inCHAT_MODELSstops the backend from starting.Follow-ups (not in this PR)
qwenprovider todashscope, since it is the platform and not the model family.🤖 Generated with Claude Code