Skip to content

chore: sync model developers data#1675

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

chore: sync model developers data#1675
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 force-pushed the sync-model-developers branch from 5ab4762 to b88666d Compare May 17, 2026 03:52
@github-actions github-actions Bot added automated dependencies Pull requests that update a dependency file labels May 17, 2026
@greptile-apps

greptile-apps Bot commented May 17, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This automated PR syncs the local providers.json snapshot with the upstream PublicProviderConf source. The file serves as both the fallback for useDevelopersData() and the remotely-fetched data once merged into unstable.

  • Provider ordering changed (now zaimistralopenai → …), models were added to nvidia (+16), and models were removed from xai (−11, including grok-3, grok-4, grok-4-fast, grok-code-fast-1) and bytedance (−5).
  • A new top-level model field interleaved (e.g. {"field": "reasoning_content"}) appears on many Z.AI and GLM models; this field is absent from providerModelSchema and will be silently dropped by Zod's default strip behavior, so no runtime error occurs but the field is never surfaced to the UI.
  • Several NVIDIA and Meta models carry all-zero pricing, which may be intentional (free-tier / research access) but should be confirmed against the upstream source.

Confidence Score: 4/5

Safe 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 interleaved field will be silently discarded by the Zod schema on every parse, and 11 xai model IDs that may appear in saved user configs have been removed. Neither is a hard blocker, but both merit acknowledgment.

The single changed file frontend/src/features/models/data/providers.json is the only file that needs attention, specifically the xai model removals and the unrecognized interleaved field.

Important Files Changed

Filename Overview
frontend/src/features/models/data/providers.json Automated upstream sync replacing 341 model entries across 16 providers; all-zero pricing on many new NVIDIA and Meta models, notable model removals in xai (11 models) and bytedance (5 models), and new top-level interleaved field that the Zod schema silently strips.

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
Loading

Comments Outside Diff (2)

  1. frontend/src/features/models/data/providers.json, line 1 (link)

    P2 New interleaved field silently dropped by schema

    The sync introduces a top-level model field interleaved (e.g. {"field": "reasoning_content"}) on Z.AI glm-5v-turbo, glm-5.1, glm-5-turbo, glm-5, glm-4.7, and a number of other models. providerModelSchema in providers.schema.ts does not declare this field, so Zod's default object parsing strips it silently — both from the remote fetch path and from the local placeholder. If downstream UI or model-configuration logic needs to know the interleaved reasoning field name, it will receive undefined rather than "reasoning_content".

  2. frontend/src/features/models/data/providers.json, line 1 (link)

    P2 Significant xai model removals may break saved user configurations

    This sync removes 11 xai (Grok) models that were present in the previous version: grok-3, grok-3-fast, grok-3-latest, grok-3-mini, grok-3-mini-fast, grok-4, grok-4-fast, grok-4-1-fast, grok-4-fast-non-reasoning, grok-4-1-fast-non-reasoning, and grok-code-fast-1. If any users have saved provider configurations referencing these model IDs, those configurations will silently lose the model entry after this merge. Whether the application handles missing model IDs gracefully (e.g. with a fallback or a warning) is worth verifying.

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

@looplj looplj merged commit aab5159 into unstable May 18, 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