chore: remove deprecated models from the catalog#986
chore: remove deprecated models from the catalog#986github-actions[bot] wants to merge 1 commit into
Conversation
6c6051f to
3e94c8c
Compare
|
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: 3e94c8cd2d
ℹ️ 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".
| "magistral-small-2506", | ||
| "meta-llama/Meta-Llama-3-8B-Instruct-Turbo", | ||
| "meta-llama/llama-4-maverick-17b-128e-instruct", | ||
| "meta-llama/llama-4-scout-17b-16e-instruct", |
There was a problem hiding this comment.
Keep enterprise-scoped Groq models routeable
When the proxy is used with Groq enterprise/committed-spend credentials, this model is still documented as available after the July 17, 2026 free/developer-tier shutdown: Groq's deprecation page says enterprise customers with a committed-spend contract are not affected, and the model card still shows a Quick Start for meta-llama/llama-4-scout-17b-16e-instruct (https://console.groq.com/docs/deprecations, https://console.groq.com/docs/model/meta-llama/llama-4-scout-17b-16e-instruct). Adding it to the sync exclusion list, together with removing it from model_list.json/AvailableEndpointTypes, makes getModelEndpointTypes(...) return no Groq route and prevents future syncs from restoring it, so those enterprise requests are incorrectly blocked instead of merely deprecated for non-enterprise use.
Useful? React with 👍 / 👎.
| "qwen-2.5-32b", | ||
| "qwen-2.5-coder-32b", | ||
| "qwen-qwq-32b", | ||
| "qwen/qwen3-32b", |
There was a problem hiding this comment.
Do not blacklist enterprise-available Qwen on Groq
When the proxy is used with Groq enterprise/committed-spend credentials, this ID is not a definitive provider-wide removal: Groq's deprecation page scopes the July 17, 2026 shutdown to free/developer usage and says committed-spend enterprise customers are not affected, while the model card still documents qwen/qwen3-32b usage (https://console.groq.com/docs/deprecations, https://console.groq.com/docs/model/qwen/qwen3-32b). Because this addition keeps sync_models from re-adding the catalog entry and the commit also removes its Groq endpoint mapping, enterprise users who can still access the model lose routing through the proxy.
Useful? React with 👍 / 👎.
Model deprecation audit
Each model below returned a definitive not-found / deprecated response from its provider (a single 404 / not-found is treated as authoritative). Account/region-scoped providers (bedrock, vertex, databricks) are surfaced for manual review, not auto-removed.
{ "deprecations": [ { "model": "meta-llama/llama-4-scout-17b-16e-instruct", "provider": "groq", "reason": "absent from list + probe not-found", "status": 404, "detail": "{\"error\":{\"message\":\"The model `meta-llama/llama-4-scout-17b-16e-instruct` does not exist or you do not have access to it.\",\"type\":\"invalid_request_error\",\"code" }, { "model": "qwen/qwen3-32b", "provider": "groq", "reason": "absent from list + probe not-found", "status": 404, "detail": "{\"error\":{\"message\":\"The model `qwen/qwen3-32b` does not exist or you do not have access to it.\",\"type\":\"invalid_request_error\",\"code\":\"model_not_found\"}}\n" } ], "reportOnly": [ { "provider": "bedrock", "modelCount": 117 }, { "provider": "databricks", "modelCount": 36 }, { "provider": "fireworks", "modelCount": 266 }, { "provider": "vertex", "modelCount": 117 } ], "skipped": [ { "provider": "lepton", "reason": "no adapter" }, { "provider": "replicate", "reason": "no adapter" } ] }