Repository navigation
Conversation
|
nice work! |
Resolve the provider registry conflict by keeping both nano-gpt and openai, and carry NanoGPT model descriptions so the new TOMLs satisfy the current schema.
|
Conflicts are fixed and PR updated |
|
hopefully this is merged soon! |
|
AUTOMATED REVIEW: The sync implementation has a promising foundation, but I found several issues that should be addressed before merging:
The code is worth continuing, but I recommend splitting the sync implementation from the generated catalog migration and adding focused translator tests before reviewing the full-sync output. |
|
Closing this pull request as stale because it has not been updated since feedback from @rekram1-node was left 7 days ago. Feel free to reopen it or submit a new pull request if the work is resumed. |
Summary
nano-gpt:synchttps://nano-gpt.com/api/v1/models?detailed=truewith nullable field handling, reasoning option inference, cache pricing conversion, and case-only ID normalization--new-onlysync, includingzai-org/glm-5.2,zai-org/glm-5.2:thinking, andTEE/glm-5.2Validation
bun validatebun ./packages/core/script/sync-models.ts nano-gpt --new-only --dry-run-> 0 created, 0 updated, 0 removedbun testcurrently fails in existing repository metadata checks for open-weight canonical models missing weight links, e.g.openai/whisper-large-v3,sarvam/sarvam-30b, and severalnvidia/*entries. The new NanoGPT provider entries generated here useopen_weights = falsefor the affected provider-specific NVIDIA/Cohere additions.