gemini-cli[bot] 45d35ff440 fix(core): fall back to default model for invalid Gemini model IDs ...

This PR implements a validation check in `resolveModel` to ensure that Gemini model IDs are valid before use.

### Problem
Outdated or non-existent Gemini model IDs (like `gemini-pro-latest`) can get persisted in a user's `settings.json` if they were ever used or resolved in previous CLI versions. On subsequent startups, the CLI picks this invalid model from settings, leading to "model not supported" API errors.

### Solution
Modified `resolveModel` in `packages/core/src/config/models.ts` to verify if a Gemini model ID (starting with `gemini-`) is in the `VALID_GEMINI_MODELS` set. If it's not, the function now falls back to `DEFAULT_GEMINI_MODEL`.

Custom (non-Gemini) model IDs are still allowed and returned as-is to maintain flexibility for proxies and other providers.

Fixes: #26971

cc @kevinjwang1

2026-05-15 20:51:44 +00:00

..

scripts

refactor(sandbox): reorganize Windows sandbox files (#23645)

2026-03-24 14:32:20 +00:00

src

fix(core): fall back to default model for invalid Gemini model IDs

2026-05-15 20:51:44 +00:00

vendor/ripgrep

feat: bundle ripgrep binaries into SEA for offline support (#25342)

2026-04-15 06:28:06 +00:00

GEMINI.md

docs: distribute package-specific GEMINI.md context to each package (#22734)

2026-03-17 19:51:23 +00:00

index.ts

feat(core,cli): add support for Gemma 4 models (experimental) (#25604)

2026-04-23 23:02:17 +00:00

package.json

security: update dependencies to fix critical and high vulnerabilities (#27077)

2026-05-15 02:01:38 +00:00

test-setup.ts

…

tsconfig.json

…

vitest.config.ts

…