Skip to content

fix(llm): use gemini-3.5 flash models in place of retired 2.5 defaults - #1220

Open
ShaanGS wants to merge 1 commit into
OWASP:stagingfrom
ShaanGS:fix/staging-retired-gemini-defaults
Open

ShaanGS wants to merge 1 commit into
OWASP:stagingfrom
ShaanGS:fix/staging-retired-gemini-defaults

Conversation

@ShaanGS

@ShaanGS ShaanGS commented Nov 10, 2026

Copy link
Copy Markdown

Fixes #1218.

Google no longer serves the gemini-2.5 flash models to new API keys, so on staging the OIE noise filter, chat and the other helpers fail with a 404 for anyone setting up fresh. #1151 fixed the noise-filter default on main; this does the same on staging for every gemini-2.5-flash-lite and gemini-2.5-flash default in the app code, .env.example, the README examples and the Module B runbook. They become gemini-3.5-flash-lite, which the API error suggests, and gemini-3.5-flash (the suggested 3.8-flash returned 503 for me).

Left as they are:

I ran the pipeline on staging with a new key: before this, Module B got a 404 on every batch and the run stopped there. With this branch and no overrides, it classifies the staged records. The unit tests give the same result as on staging.

@coderabbitai

coderabbitai Bot commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review: 1

  • main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

This branch has not been deployed

No deployments
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.

1 participant