chore: update model catalog from bot issues#797
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Codex (@codex) review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: efb8bf94c3
ℹ️ 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".
| "databricks" | ||
| ] | ||
| }, | ||
| "databricks-claude-fable-5": { |
There was a problem hiding this comment.
Don't advertise the unavailable Databricks Fable endpoint
As of June 16, 2026, Databricks' own Fable 5 announcement has an update saying the model is currently unavailable, and Anthropic's announcement says access was suspended on June 12. Adding it to the static catalog makes clients discover and route requests to /serving-endpoints/databricks-claude-fable-5/invocations, so selecting this newly exposed Databricks model will fail until access is restored; please hold this entry or mark it unavailable/deprecated rather than listing it as an available provider. Sources checked: Databricks blog, Anthropic announcement.
Useful? React with 👍 / 👎.
efb8bf9 to
76c1ab4
Compare
Codex Review ResponsePR: #797 Action taken: Added Why: Verified via both Anthropic's announcement (access suspended June 12, 2026) and Databricks' blog post (marked "currently unavailable"). Marking the entry deprecated prevents clients from discovering and routing requests to the non-functional endpoint, while preserving the catalog entry for when access is restored. Files changed: |
Automated daily batch of model catalog updates from bot issues.
Included issues
Summary
databricks-claude-fable-5databricks-claude-fable-52
3
Verified metadata
#796: [BOT ISSUE] Databricks: add missing databricks-claude-fable-5 model
Verification notes
No LLM verification step ran; model metadata was already complete in the issue.
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.