You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gemma 4 notebooks were grouped under the Gemma section together with
Gemma 3, Gemma 2, FunctionGemma, EmbeddingGemma and CodeGemma. Split
them out into their own "### Gemma 4 Notebooks" section so the newer
family is visually separated from the legacy Gemma models.
Two changes:
1. ARCHITECTURE_MAPPING gains a "gemma4" -> "Gemma 4" entry. Because
_get_arch in extract_model_info_refined sorts mapping keys by
length descending, "gemma4" (6 chars) is tried before "gemma"
(5 chars). The word-boundary regex \\bgemma4\\b matches the word
in "Gemma4 (E4B)" / "Gemma4 (E2B)" / "Gemma4 (31B)" /
"Gemma4 (26B A4B)" but does NOT match Gemma3, Gemma3N, Gemma2,
FunctionGemma, EmbeddingGemma or CodeGemma -- so only Gemma 4
notebooks move into the new section, and everything else stays
in the existing Gemma section.
2. update_readme reorders list_models so "Gemma 4" appears
immediately before "Gemma". Default alphabetical sort would have
placed it after Gemma (because "Gemma" is a prefix of "Gemma 4"),
but the user wants the newer family on top. Surgical reorder via
list.remove + list.insert at the index of "Gemma".
Result: README now has
### Gemma 4 Notebooks <- 10 rows (E4B / E2B / 31B / 26B A4B
x Vision / Conversational / Audio)
### Gemma Notebooks <- 17 rows (Gemma3N, Gemma3, Gemma2,
FunctionGemma, EmbeddingGemma,
CodeGemma)
0 commit comments