fix: add Databricks models databricks-gemini-3-1-pro +2 more#648
Open
github-actions[bot] wants to merge 1 commit into
Open
fix: add Databricks models databricks-gemini-3-1-pro +2 more#648github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
requested review from
Alex Z (CLowbrow),
aswink,
Caitlin Pinn (cpinn),
Erin McNulty (erin2722) and
Ken Jiang (knjiang)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
4 tasks
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
1 participant
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.
fix: add Databricks models databricks-gemini-3-1-pro +2 more
Closes #639
Source issue: #639
Summary
databricks-gemini-3-1-prodatabricks-gemini-2-5-prodatabricks-gemini-2-5-flashdatabricks-gemini-3-1-prodatabricks-gemini-2-5-prodatabricks-gemini-2-5-flash2
Verified metadata
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.