Skip to content
Source
Sign inSign up
TanStack/schemas

huggingface: state the upstream model from the repo owner in the id #727

Mergedtombeckenhammerged 1 commit intomain fromfeat/718-upstream-huggingfacemerged by tombeckenham View on GitHub

tombeckenhamcommented

Part of #718.

Rule: a router id (router.huggingface.co/v1/models data[].id) is the Hub repo, owner/name; the owner is the namespace and the name the upstream raw id, source { derivation: listing, sourceUrl: https://router.huggingface.co/v1/models, path: data[].id }. The listing's owned_by repeats the owner on every row (159 of 159 on 2026-11-21), so the id and the field say the same thing; the id is read, as Perplexity and Lovable do. An id with no owner states nothing. No per-model table.

Examples: CohereLabs/command-a-vision-07-2025 -> cohere command-a-vision-07-2025; inclusionAI/Ling-3.1-flash -> ant-ling Ling-3.1-flash; MiniMaxAI/MiniMax-M3 -> minimax MiniMax-M3 once #723 lands.

Namespaces added: CohereLabs on cohere, inclusionAI on ant-ling. MiniMaxAI for minimax is in #723 (Together uses it too) so the two PRs do not edit the same line.

Counts against the live listing (2026-11-21): 159 rows, all 159 state an upstream. 10 have a target row with this PR alone (7 CohereLabs/*, 3 inclusionAI/*); 12 once #723's MiniMaxAI claim is in.

Unlinked, and why: most repos are open weights whose maker has no API row here, or whose Hub name differs from the maker's API id (Qwen/Qwen3.8-27B vs Model Studio qwen3.8-27b, zai-org/GLM-5, moonshotai/Kimi-K3, deepseek-ai/DeepSeek-V4..., meta-llama/...). Matching those by name is #719. The owner is the repo's publisher, not always the original maker: a quantised re-upload such as cyankiwi/Qwen3.5-9B-AWQ-4bit states its uploader, which no provider claims, so it resolves to nothing. The listing carries no base-model field to say otherwise.

Checks: typecheck, lint, check, huggingface.test.ts, model-namespaces.test.ts, model-identity.worker.test.ts pass.

    1. ⚠️ No Changeset found

      Latest commit: 3616f1d859bc28b387c60f3865267536a1d66ac9

      Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

      This PR includes no changesets

      When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

      Click here to learn what changesets are, and how to add one.

      Click here if you're a maintainer who wants to add a changeset to this PR

    2. Warning

      Review limit reached

      You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

      Next included review available in 32 minutes.

      Check out review usage here.

      View limit details

      Limit details: You’ve used the included review currently available.

      Learn how review limits work.

      Review configuration:

      Run configuration

      • Source mode: Auto
      • Repository: Unavailable
      • Branch: Unavailable
      • File: No configuration file from this repository applied
      • Commit: Unavailable
      • Layers: defaults
      • Review profile: CHILL
      • Plan: Advanced
      • Run ID: 0cbeb9ab-2403-4631-a473-77d64a4c7421
      Commits

      Reviewing files that changed from the base of the PR and between 3cd28b65a3b40ec3143f48410a4a6fc3dc9fcc38 and 3616f1d859bc28b387c60f3865267536a1d66ac9.

      Files selected for processing: 4

      • src/server/providers/adapters/ant-ling.ts
      • src/server/providers/adapters/cohere.ts
      • src/server/providers/adapters/huggingface.test.ts
      • src/server/providers/adapters/huggingface.ts
      • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

      Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

      Share

    3. tombeckenham merged thise4fe4a8

    4. tombeckenham closed this

Sign in to join this conversation.