Repository navigation
chore: add model to catalog - #1713
github-actions[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9560624f42
ℹ️ 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.
The add-model workflow requires every provider surface established by earlier models in the family (.github/workflows/add-model.yaml:256-264), and moonshotai/Kimi-K3 already establishes that this shared slug is served by both Baseten and Together. Listing only baseten here—and likewise only Baseten in AvailableEndpointTypes—means K3.1 Pro cannot be selected or routed through Together despite that required family convention; add together to both mappings.
Useful? React with 👍 / 👎.
| "fallback_models": [ | ||
| "databricks-kimi-k3-1-pro", | ||
| "global.moonshotai.kimi-k3.1-pro", | ||
| "moonshotai.kimi-k3.1-pro", | ||
| "moonshotai/kimi-k3.1-pro", | ||
| "us.moonshotai.kimi-k3.1-pro" |
There was a problem hiding this comment.
The same workflow requires all established family provider companions to be added and linked as fallbacks, while the catalog already has Fireworks companions for Kimi K2.x and Kimi K3. A repo-wide search finds no Fireworks entry or index mapping for K3.1 Pro, and this fallback list therefore cannot expose Fireworks through getModelEndpointTypes; add the family-derived Fireworks companion, its mapping, and its fallback link.
Useful? React with 👍 / 👎.
Automated targeted model-catalog addition from the model-drop workflow.