Skip to content

chore: retire Alibaba snapshot model mappings - #2603

Merged
steebchen merged 1 commit into
mainfrom
chore/retire-alibaba-snapshots
Jun 9, 2026
Merged

steebchen merged 1 commit into
mainfrom
chore/retire-alibaba-snapshots

Conversation

@steebchen

@steebchen steebchen commented Jun 9, 2026 •

Copy link
Copy Markdown
Member

Summary

Alibaba Cloud Model Studio is retiring a set of legacy snapshot models on 2026-07-08. This marks the affected alibaba provider mappings with deactivatedAt: new Date("2026-07-08") so they stay live until the retirement date and then auto-deactivate (the gateway treats a mapping as deactivated only once new Date() > deactivatedAt).

Affected alibaba mappings

Only mappings whose externalId exactly matches a retiring snapshot are touched:

File Model (externalId)
alibaba.ts qwen3-next-80b-a3b-thinking
alibaba.ts qwen3-next-80b-a3b-instruct
alibaba.ts qwen3-vl-235b-a22b-instruct
alibaba.ts qwen3-vl-235b-a22b-thinking
alibaba.ts qwen3-max-2026-01-23
deepseek.ts deepseek-v3.2
zai.ts glm-4.7
zai.ts glm-4.6
moonshot.ts Moonshot-Kimi-K2-Instruct
moonshot.ts kimi-k2-thinking

Notes

  • Models also served through other providers (nebius, novita, embercloud, bytedance) keep working via those mappings — only the alibaba mapping is deactivated.
  • Aliases like qwen3-coder-plus and qwen3-vl-flash are not dated snapshots and continue resolving to current versions on Alibaba, so they are intentionally left untouched.
  • Recommended replacements from the notice (qwen3.7-max, qwen3.7-plus) already exist in the catalog.

Testing

  • pnpm format
  • pnpm test:unit — 1919 passed, 2 skipped
  • pnpm build — all 17 tasks pass

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

  • Chores
    • Multiple AI model configurations have been scheduled for deactivation beginning July 8, 2026, affecting specific variants across multiple providers.

Alibaba Cloud Model Studio retires a set of legacy snapshot models on
2026-07-08. Mark the affected `alibaba` provider mappings as
deactivatedAt that date so they auto-deactivate on retirement while
staying live until then. Models also served via other providers
(nebius/novita/embercloud/bytedance) keep working through those.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 9, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 1211d429-a99f-4250-800a-3b3c3095c6a7

📥 Commits

Reviewing files that changed from the base of the PR and between 61216a5 and 7913cad.

📒 Files selected for processing (4)
  • packages/models/src/models/alibaba.ts
  • packages/models/src/models/deepseek.ts
  • packages/models/src/models/moonshot.ts
  • packages/models/src/models/zai.ts

Walkthrough

Five model definition files are updated to add deactivatedAt: new Date("2026-07-08") timestamps to specific Alibaba and related provider entries. Changes span Qwen, DeepSeek, Moonshot, and Zhipu model configurations, deactivating those provider combinations starting July 8, 2026.

Changes

Alibaba Provider Deactivation

Layer / File(s) Summary
Deactivate model-provider entries on 2026-07-08
packages/models/src/models/alibaba.ts, packages/models/src/models/deepseek.ts, packages/models/src/models/moonshot.ts, packages/models/src/models/zai.ts
Alibaba provider entries are marked with deactivatedAt: new Date("2026-07-08") for qwen3-next-80b-a3b-thinking, qwen3-next-80b-a3b-instruct, qwen3-vl-235b-a22b-instruct, qwen3-vl-235b-a22b-thinking, qwen3-max-2026-01-23, deepseek-v3.2 Alibaba, kimi-k2 and kimi-k2-thinking skip provider, and glm-4.7 and glm-4.6 Alibaba provider entries.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • theopenco/llmgateway#2527: Updates model-provider entries across files by adding deactivatedAt timestamps for Google Gemini providers on 2026-10-02, following the same deactivation pattern as this PR.
  • theopenco/llmgateway#2482: Updates packages/models/src/models/deepseek.ts to add deactivatedAt for the deepseek-v3.2 provider entries on 2026-05-01, sharing the same file and model with this PR's DeepSeek update.
  • theopenco/llmgateway#2539: Modifies packages/models/src/models/moonshot.ts to update deactivatedAt for kimi-k2 provider mappings, overlapping with the same model entries updated in this PR.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore: retire Alibaba snapshot model mappings' accurately summarizes the main change: marking Alibaba provider model mappings with deactivation dates.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/retire-alibaba-snapshots

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@steebchen
steebchen added this pull request to the merge queue Jun 9, 2026
Merged via the queue into main with commit ffb9213 Jun 9, 2026
17 of 18 checks passed
@steebchen
steebchen deleted the chore/retire-alibaba-snapshots branch June 9, 2026 16:33
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.

1 participant