Skip to content

feat(providers): add Alibaba (China) provider for the dashscope China endpoint - #3329

Open
me2seeks wants to merge 1 commit into
apache:mainfrom
me2seeks:feat/alibaba-china-provider
Open

feat(providers): add Alibaba (China) provider for the dashscope China endpoint#3329
me2seeks wants to merge 1 commit into
apache:mainfrom
me2seeks:feat/alibaba-china-provider

Conversation

@me2seeks

Copy link
Copy Markdown
Contributor

Summary

Maka's alibaba provider is pinned to the international Model Studio endpoint (dashscope-intl.aliyuncs.com), leaving no access path for the China platform. This PR registers models.dev alibaba-cn as a first-class provider bound to https://dashscope.aliyuncs.com/compatible-mode/v1, so China-platform users can connect with keys from bailian.console.aliyun.com. The catalog carries 81 tool-calling models and defaults to qwen3.8-max (1M context, 128k output, vision/pdf input, thinking toggle + low/medium/xhigh efforts). Hosted web-search handling mirrors the international alibaba provider, and the desktop picker gains display copy (Alibaba 中国站 / Alibaba (China)) plus the Alibaba brand mark.

The models.dev sync now ingests alibaba-cn. The generated metadata and pricing snapshots gain only the alibaba-cn blocks (spliced from a full live regeneration): a full regen is currently blocked by unrelated upstream drift — e.g. models.dev renamed the opencode free model north-mini-code-free, which would break an existing registry pin — and that drift deserves its own sync pass rather than riding along here.

Fixes #3323

Verification

  • node --test packages/core/dist/__tests__/**/*.test.js — 553/553 pass (includes new catalog + web-search assertions)
  • node --test packages/runtime/dist/__tests__/**/*.test.js — 2843 pass, 0 fail (includes new wire-contract assertion keeping qwen3.8-max on openai-chat)
  • @maka/desktop typecheck — clean (all four tsconfigs)
  • biome format / biome lint on all touched files — clean
  • Registry smoke check: PROVIDER_REGISTRY['alibaba-cn'] → label Alibaba (China), China endpoint, fallbackModels[0] === 'qwen3.8-max'
  • Not run: desktop e2e / real-network call against the China endpoint (no China-platform key available in this environment)

AI use

Select exactly one:

  • No generative tool made a substantive contribution
  • Generative tooling made a substantive contribution

Tool(s) and scope: Maka — investigation, implementation, and tests; commit carries the Generated-by: Maka trailer.

Checklist

  • Tests cover the change and fail without it
  • Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

  • Yes — described under Summary above
  • No

… endpoint

Register models.dev alibaba-cn as a first-class provider so China-platform
users can connect to https://dashscope.aliyuncs.com/compatible-mode/v1 with
keys from bailian.console.aliyun.com. The catalog carries 81 tool-calling
models and defaults to qwen3.8-max, with hosted web-search parity to the
international alibaba provider.

The models.dev sync ingests alibaba-cn; the generated metadata and pricing
snapshots gain only the alibaba-cn blocks because a full regeneration is
currently blocked by unrelated upstream drift (e.g. opencode free-model
renames) that deserves its own sync pass.

Closes apache#3323

Generated-by: Maka
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(providers): add Alibaba (China) provider for the dashscope China endpoint

1 participant