Skip to content

chore: sync model developers data#1588

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

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

Conversation

@github-actions

@github-actions github-actions Bot commented May 3, 2026

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 3, 2026
@greptile-apps

greptile-apps Bot commented May 3, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This automated PR syncs model provider data from the upstream PublicProviderConf source. Changes include adding new models (Qwen3.6 variants, Grok 4.3, GPT-5.5 Pro, Nemotron 3 Nano Omni, Mistral Medium 3.5), updating existing model metadata (costs, limits, modalities, open_weights flags), relocating the xai provider block, and fixing model families (mimo-v2.5-promimo).

Confidence Score: 4/5

Safe to merge — purely a data file sync from a trusted upstream source; no logic changes.

All changes are confined to a single JSON data file. The sync is automated from a versioned upstream source. One observation worth noting is the MiMo-V2.5-Pro / MiMo-V2.5 modality swap, but this originates from upstream and may be intentional; no code paths are affected. No P0/P1 issues identified.

frontend/src/features/models/data/providers.json — particularly the MiMo-V2.5-Pro and MiMo-V2.5 modality and open_weights changes.

Important Files Changed

Filename Overview
frontend/src/features/models/data/providers.json Automated data sync adding new models (Qwen3.6, Grok 4.3, GPT-5.5 Pro, Nemotron 3 Nano Omni, Mistral Medium 3.5/latest), updating costs/limits/modalities for existing models, and correcting MiMo family names; the MiMo-V2.5 and MiMo-V2.5-Pro modality sets are swapped relative to the previous data, which may reflect upstream corrections or an upstream data error.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Upstream PublicProviderConf all.json] -->|weekly sync workflow| B[providers.json]
    B --> C[Provider: Alibaba]
    B --> D[Provider: xAI]
    B --> E[Provider: Nvidia]
    B --> F[Provider: OpenAI]
    B --> G[Provider: Mistral]
    B --> H[Provider: MiMo / others]

    C -->|Added| C1[qwen3.6-27b]
    C -->|Added| C2[qwen3.6-max-preview]
    C -->|Added| C3[qwen3.6-35b-a3b]
    C -->|Added| C4[qwen3.5-122b-a10b]
    C -->|Updated specs| C5[qwen3.5-397b-a17b]

    D -->|Added| D1[grok-4.3]
    D -->|Repositioned| D2[xai provider block moved]

    E -->|Added| E1[nemotron-3-nano-omni-30b]

    F -->|Added| F1[gpt-5.5-pro]
    F -->|Updated limits| F2[existing OpenAI models]

    G -->|Added| G1[mistral-medium-2604]
    G -->|Replaced| G2[mistral-medium-latest new specs]

    H -->|family rename + spec update| H1[mimo-v2.5-pro]
    H -->|family rename + spec update| H2[mimo-v2.5]
Loading

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

Comment on lines 13132 to +13145
"last_updated": "2026-04-22",
"modalities": {
"input": [
"text"
"text",
"image",
"audio",
"video",
"pdf"
],
"output": [
"text"
]
},
"open_weights": true,
"open_weights": false,

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.

P2 MiMo-V2.5-Pro / MiMo-V2.5 modalities appear swapped

The upstream data swapped the input modality sets between these two models: mimo-v2.5-pro now lists text + image + audio + video + pdf while mimo-v2.5 (the non-Pro) is now text only. The previous data had the opposite assignment. At the same time, both models flipped from open_weights: true to false and moved from zero-cost to paid tiers. It is worth confirming with the upstream source that this is intentional and not a data entry error, since the Pro model gaining broader modality support than the base model is plausible, but the reversal from the prior state is a meaningful breaking change for any consumer relying on these fields.

@looplj looplj merged commit 1641097 into unstable May 3, 2026
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