chore: remove old Gemini models and keep Gemini 3.0 set#64
Open
Phong940253 wants to merge 1 commit intoAmm1rr:masterfrom
Open
chore: remove old Gemini models and keep Gemini 3.0 set#64Phong940253 wants to merge 1 commit intoAmm1rr:masterfrom
Phong940253 wants to merge 1 commit intoAmm1rr:masterfrom
Conversation
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.
Summary: Remove legacy Gemini models (1.5/2.0/2.5) and standardize project to Gemini 3.0 models only.
Changes:
Updated model lists in config templates and documentation.
Updated default Gemini model to gemini-3.0-flash.
Kept only: gemini-3.0-pro, gemini-3.0-flash, gemini-3.0-flash-thinking.
Why: Avoid confusion and keep API/config aligned with currently supported models.
Verification:
Impact: Breaking for users still sending old model IDs (they must migrate to Gemini 3.0 names).