feat(models): add Atlas Cloud provider - #335
binyangzhu000-sudo wants to merge 2 commits into
Conversation
Signed-off-by: binyangzhu000-sudo <224954946+binyangzhu000-sudo@users.noreply.github.com>
Both conflicts were registries where upstream and this branch each added entries in the same place: - hermes_providers.rs: kept P_ATLASCLOUD alongside upstream's new P_OPENAI_API and P_FIREWORKS, set the registry-length assertion to 40 (upstream's 39 plus this one), and kept both model-lookup assertions. They don't collide: upstream matches the bare "deepseek-v4-pro" while this provider only claims the prefixed "deepseek-ai/deepseek-v4-pro", and find_provider_by_model requires a unique hit. - scripts/dev-api.js: took upstream's provider lines verbatim, including its updated base URLs and transports for anthropic/gemini/deepseek, and re-appended only the atlascloud line. Verified the two registries stay in sync: both list exactly 40 providers with identical id sets. Signed-off-by: binyangzhu000-sudo <binyangzhu000@gmail.com>
|
Synced with
The part worth a second look was the model-lookup test. You changed it to assert
I also checked the two registries stay in sync, since they're maintained separately: both list exactly 40 providers with identical id sets. Verification — Disclosure: I work at Atlas Cloud. |
变更描述
新增 Atlas Cloud 的中性技术接入:
atlascloudOpenAI-compatible 预设和默认模型ATLASCLOUD_API_KEYdeepseek-ai/deepseek-v4-pro的完整嵌套模型 ID,修复默认模型诊断对带/模型 ID 的解析未修改 README、Logo、赞助位或推广内容。
变更类型
测试清单
node --test tests/*.test.js(525 passed,1 skipped)npm run buildcargo fmt --all -- --checkcargo test --locked hermes_providers(5 passed)相关 Issue
N/A
截图
无 UI 布局变更。