Skip to content

chore: sync model developers data#1706

Merged
looplj merged 1 commit into
unstablefrom
sync-model-developers
May 24, 2026
Merged

chore: sync model developers data#1706
looplj merged 1 commit into
unstablefrom
sync-model-developers

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated sync of model developers data from upstream source.

Source: https://raw.githubusercontent.com/ThinkInAIXYZ/PublicProviderConf/refs/heads/dev/dist/all.json

This PR was automatically created by the weekly sync workflow.

@github-actions github-actions Bot added automated dependencies Pull requests that update a dependency file labels May 24, 2026
@greptile-apps

greptile-apps Bot commented May 24, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This automated PR syncs the providers.json model catalogue from the upstream PublicProviderConf dataset. The bulk of the changes are routine housekeeping — removing older dated preview models, adding newer stable IDs (Gemini 3.5 Flash, Gemini 2.5 Flash, Gemini 2.5 Pro, Gemini Embedding 001, Qwen3.7 Max, Qwen3.6 Flash), and refreshing pricing/limits/capability flags for existing models.

  • New models added: gemini-3.5-flash, gemini-2.5-flash-image, gemini-flash-lite-latest, gemini-embedding-001, gemini-2.5-pro-preview-tts, gemini-2.5-flash-preview-tts, gemini-2.5-flash-image-preview, gemini-2.5-flash-lite-preview-09-2025, qwen3.7-max, qwen3.6-flash.
  • Removed models: A large batch of dated preview slugs (e.g. gemini-2.5-flash-preview-05-20, gemini-2.5-pro-preview-06-05, gemini-live-2.5-flash, legacy Gemma 3/3n variants, older Gemini 1.x models, and several xAI Grok preview entries).
  • Data quality issue: The model gemini-3.1-flash-image-preview was given the placeholder name \"Nano Banana 2\" from the upstream source, which would surface directly to users in the model picker.

Confidence Score: 3/5

The sync is safe to merge for most model entries, but the "Nano Banana 2" display name for gemini-3.1-flash-image-preview would be visible to end-users and should be corrected before merging.

All model data updates look technically consistent (proper JSON structure, valid cost/limit values), but the upstream source contains a clearly bogus display name for gemini-3.1-flash-image-preview that would be rendered in the UI. A downstream name validation step or review gate in the sync workflow would have caught this.

frontend/src/features/models/data/providers.json — specifically lines 7110 and 7142 where "Nano Banana 2" appears as both the name and display_name for gemini-3.1-flash-image-preview.

Important Files Changed

Filename Overview
frontend/src/features/models/data/providers.json Automated sync adds new models (Gemini 3.5 Flash, Qwen3.7 Max, Qwen3.6 Flash, etc.), removes legacy preview models, and updates costs/limits — but also introduces a bogus display name "Nano Banana 2" for gemini-3.1-flash-image-preview that would be shown to users.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Weekly Sync Workflow] -->|fetch| B[PublicProviderConf all.json]
    B -->|automated diff| C[providers.json patch]
    C --> D{Change Types}
    D --> E[New models added\nGemini 3.5 Flash, Qwen3.7 Max, etc.]
    D --> F[Legacy preview models removed\ngemini-2.5-flash-preview-05-20, etc.]
    D --> G[Capability / cost / limit updates\nGemma 4 IT, Grok 4.3, etc.]
    D --> H[⚠️ Bogus name ingested\ngemini-3.1-flash-image-preview\nname = 'Nano Banana 2']
    H -->|displayed in UI| I[Model picker shows\n'Nano Banana 2']
Loading

Reviews (1): Last reviewed commit: "chore: sync model developers data" | Re-trigger Greptile

Comment on lines 7110 to +7142
@@ -7067,14 +7132,14 @@
},
"open_weights": false,
"limit": {
"context": 131072,
"output": 32768
"context": 65536,
"output": 65536
},
"cost": {
"input": 0.5,
"output": 60
},
"display_name": "Gemini 3.1 Flash Image (Preview)",
"display_name": "Nano Banana 2",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Bogus model name "Nano Banana 2" from upstream source

The model gemini-3.1-flash-image-preview has both name and display_name set to "Nano Banana 2" in the upstream source (PublicProviderConf). This appears to be a placeholder or test entry in that dataset. As-is, this string will be displayed to end-users in the model selection UI as if it were a real model name.

@looplj looplj merged commit e1eb711 into unstable May 24, 2026
junjiangao pushed a commit to junjiangao/axonhub that referenced this pull request May 25, 2026
Co-authored-by: looplj <231043908+looplj@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant