Skip to content

Cap Gemini CLI below 0.45 and prefer newest model version#149

Merged
rohita5l merged 2 commits into
mainfrom
fix/gemini-045-version-cap
Jun 10, 2026
Merged

Cap Gemini CLI below 0.45 and prefer newest model version#149
rohita5l merged 2 commits into
mainfrom
fix/gemini-045-version-cap

Conversation

@rohita5l

Copy link
Copy Markdown
Collaborator

Gemini CLI 0.45 introduced a "Gemini 3.5 Flash GA" router that rewrites any forced flash model id (e.g. databricks-gemini-3-5-flash) to Google's canonical gemini-3.5-flash, which the Databricks AI Gateway rejects as an invalid Unity Catalog endpoint name. 0.44.x passes the configured model through verbatim and works.

  • Cap the supported Gemini version below 0.45 and check it on every launch (a too-new build runs but misbehaves, so it's a correctness blocker).
  • Warn and offer a y/n downgrade to the latest working release rather than forcing it; honor --skip-upgrade by warning without prompting.
  • Steer update prompts toward the newest version below the broken ceiling instead of npm's latest tag, which points at the broken line. Adds published_versions() and latest_version_below() helpers.
  • Order discovered Gemini models newest-version-first so default_model() launches gemini-3.5-flash rather than gemini-2.5-flash. Codex and the generic discovery path keep their alphabetical default.
  • Re-enable the e2e Gemini launch test with a version-aware skip.

Co-authored-by: Isaac

Gemini CLI 0.45 introduced a "Gemini 3.5 Flash GA" router that rewrites
any forced flash model id (e.g. databricks-gemini-3-5-flash) to Google's
canonical gemini-3.5-flash, which the Databricks AI Gateway rejects as an
invalid Unity Catalog endpoint name. 0.44.x passes the configured model
through verbatim and works.

- Cap the supported Gemini version below 0.45 and check it on every launch
  (a too-new build runs but misbehaves, so it's a correctness blocker).
- Warn and offer a y/n downgrade to the latest working release rather than
  forcing it; honor --skip-upgrade by warning without prompting.
- Steer update prompts toward the newest version below the broken ceiling
  instead of npm's `latest` tag, which points at the broken line. Adds
  published_versions() and latest_version_below() helpers.
- Order discovered Gemini models newest-version-first so default_model()
  launches gemini-3.5-flash rather than gemini-2.5-flash. Codex and the
  generic discovery path keep their alphabetical default.
- Re-enable the e2e Gemini launch test with a version-aware skip.

Co-authored-by: Isaac
@rohita5l rohita5l requested a review from AarushiShah-db June 10, 2026 00:11
@rohita5l rohita5l merged commit 678bd8b into main Jun 10, 2026
2 checks passed
@rohita5l rohita5l deleted the fix/gemini-045-version-cap branch June 10, 2026 00:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants