Add Gemini 3.7 Flash premium model support - #419
Merged
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
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
gemini-3.7-flashthrough the stateless Gemini Interactions API with response storage disabled, exact structured-tool continuation replay, provider-observed identity/usage telemetry, and no silent cross-provider substitutionValidation
google-genai==2.6.0optional call-ID contract and transport suite verifiedpdm lock --check, andgit diff --checkpassedgemini-3.7-flashlisted and persisted as allowed, and the exact live-test control enabledgemini-3.7-flashvia Interactions withstore=falseand provider-reported usage.envremains ignored; the 52-file commit contains no key-shaped secret or Sol-model referenceRelease boundary
The represented model-registry bundle remains dormant until an authenticated global semantic authority publishes it and canonical read-back succeeds. That does not block Settings or Gemini API execution. Local server deployment/restart will follow merge and successful required CI.