Gemini CLI fix: explicit gemini-3-pro-preview IDs no longer silently rewritten to 3.1
FanouZeng-TT · ghdev · 2026-09-20
A community PR (#29420) fixes a routing bug in google-gemini/gemini-cli where an explicit --model gemini-3-pro-preview was silently rewritten to gemini-3.1-pro-preview whenever the 3.1 rollout flag was enabled. Only auto/pro aliases should follow the rollout; pinned versions must stay pinned.
Key changes:
- The legacy resolveModel grouped the explicit ID with the auto case in one switch branch; it now has its own pinning case.
- Dynamic defaultModelConfigs no longer remaps the explicit key through rollout contexts, and the pro classifier tier gets a requestedModels anchor.
- Two call sites that used the explicit ID as a placeholder for the rollout target (availability catalog, preview chains) now derive it inline or use aliases.
Includes targeted regression tests; fixes issue #29417.
More from coding & agent
- Could MCP-powered copy-trading disrupt ETFs? Investor floats paying 0.5% for trade signals — MartinGTobias · 2026-11-12
- minpts-check: one-run predictor tells if your HDBSCAN clusters survive min_samples changes — leland_mcinnes · 2026-11-12
- Ten wild Gemini 4 Carbon demos in 24 hours: CUDA meadows, V8 engines, mech stomps — socialwithaayan · 2026-11-12
- How to cut Fable 5.2 token costs by 90%: Arc routing plus a lean CLAUDE.md — EXM7777 · 2026-11-12
- Hamel Husain's complete AI evals framework for PMs and engineers — aakashgupta · 2026-11-12
- AI coding in one year: from unusable to full automation with no code review — angelaqdai · 2026-11-12