-
[OPIK-5723] [SCRIPTS] feat: surface Gemma 4 + clean dead Gemma in Gemini sync (#6701)
发布于
2026-05-14 11:34:30 +00:00 Updates
scripts/sync_provider_models.pyso the daily provider-sync
workflow exposes Gemma chat models on the Gemini provider going forward.Generated artifacts (Java enum, TS types, dropdown YAML, llm-models YAML)
are intentionally NOT in this PR — the daily cron will produce them on
the next scheduled run and upload them to the CDN through the existing
workflow path.Script changes
- Drop
^gemmaand^gemini-gemmafromGEMINI_EXCLUDE_PATTERNSso
Gemma models surfaced bygenerativelanguage.googleapis.com/v1beta/models
are no longer filtered out. Verified live: the Gemini API today exposes
gemma-4-31b-itandgemma-4-26b-a4b-itwithgenerateContent
support. Gemma 2 / Gemma 3 were retired by Google in April 2026. - Add
-tts,^gemma-(2|3)-, and^gemini-gemma-to
GEMINI_DROPDOWN_EXCLUDE. Keepsgemini-3.1-flash-tts-previewout of
the picker, and hides the dead Gemma 2 / 3 IDs that still ship in the
LiteLLM prices JSON (theirgemini/route returns 404 from Google).
Models stay in the backend enum so older traces can still resolve. - Extend
_gemini_sort_keywith a family tier (Gemini=0, Gemma=1) so
Gemma sorts after Gemini in the dropdown, ordered by generation desc
and parameter size asc, with*nvariants after their base. - Collapse the legacy
gemini-gemma-label prefix togemma-in
generate_gemini_labelso any future Gemma row reads "Gemma N …" not
"Gemini Gemma N …".
Implements OPIK-5723: add Gemma models to Gemini provider.
下载附件
- Drop