fix: add Together models Qwen/Qwen3.5-397B-A17B +8 more#495
fix: add Together models Qwen/Qwen3.5-397B-A17B +8 more#495github-actions[bot] wants to merge 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6f7682b2ac
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".
| "available_providers": [ | ||
| "baseten" | ||
| ] |
There was a problem hiding this comment.
Add endpoint mapping for newly added Baseten Gemma models
These new entries declare available_providers: ["baseten"], but no corresponding keys were added to AvailableEndpointTypes in packages/proxy/schema/index.ts; getModelEndpointTypes() therefore falls back to the OpenAI default (["openai", "azure"]) for these model names. In the edge fallback path (edge/index.ts), that makes the proxy choose an OpenAI/Azure secret for Gemma 4 Baseten models when key lookup fails, causing requests to be routed with the wrong provider credentials.
Useful? React with 👍 / 👎.
fix: add Together models Qwen/Qwen3.5-397B-A17B +8 more
Closes #476
Source issue: #476
Summary
Qwen/Qwen3.5-397B-A17BQwen/Qwen3.5-9BQwen/Qwen3-Coder-Next-FP8Qwen/Qwen3-Coder-480B-A35B-Instruct-FP8MiniMaxAI/MiniMax-M2.7google/gemma-3n-E4B-itLiquidAI/LFM2-24B-A2Bdeepcogito/cogito-v2-1-671bessentialai/rnj-1-instructQwen/Qwen3.5-397B-A17BQwen/Qwen3.5-9BQwen/Qwen3-Coder-Next-FP8Qwen/Qwen3-Coder-480B-A35B-Instruct-FP8MiniMaxAI/MiniMax-M2.7google/gemma-3n-E4B-itLiquidAI/LFM2-24B-A2Bdeepcogito/cogito-v2-1-671bessentialai/rnj-1-instruct2
3
Verified metadata
sync_models vs proposed update
sync_models cross-check found differences. Official provider verification was used for the applied values, and sync_models discrepancies are listed below for review.
2
3
2
3
2
3
2
3
2
3
2
3
2
3