chore: sync model developers data#1675
Conversation
5ab4762 to
b88666d
Compare
Greptile SummaryThis automated PR syncs the local
Confidence Score: 4/5Safe to merge; the JSON is valid and all 16 providers are structurally intact, but two observations are worth a second look before landing. The sync is mechanically clean — valid JSON, schema-compatible structure, same provider set — but the new The single changed file Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Weekly Sync Workflow] -->|fetches| B[upstream all.json\nThinkInAIXYZ/PublicProviderConf]
B -->|writes| C[providers.json\nfrontend/src/features/models/data/]
C -->|merged to unstable| D[GitHub Raw URL\nDEVELOPERS_URL]
E[useDevelopersData hook] -->|fetch| D
D -->|ok| F[providersDataSchema.parse\nZod strips unknown fields]
D -->|error| G[fallback: local providers.json\nprovidersDataSchema.parse]
F --> H[ProvidersData in UI]
G --> H
subgraph Fields silently dropped by Zod
I[interleaved]
J[extra_capabilities]
K[structured_output at model level]
end
F -.->|strips| I
F -.->|strips| J
F -.->|strips| K
|
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.