Skip to content

fix(moonshot): deactivate retired kimi-k2-thinking line - #2849

Merged
steebchen merged 2 commits into
mainfrom
monterrey-v5
Jun 28, 2026
Merged

steebchen merged 2 commits into
mainfrom
monterrey-v5

Conversation

@steebchen

@steebchen steebchen commented Jun 28, 2026 •

Copy link
Copy Markdown
Member

Context

The e2e job on #2835 failed on six provider/model mappings. I reproduced each failure locally against the live providers (gateway on :4001, real keys) to find the root cause. The CI "33s / retry x5" is just retry backoff over fast errors, so the local errors match what CI hit.

Findings

Model Reproduced error Root cause Action
moonshot/kimi-k2-thinking 404 resource_not_found Moonshot retired the kimi-k2-thinking line (live /v1/models only lists k2.5/k2.6/k2.7); BytePlus Ark dropped every snapshot too Fixed here
sakana/fugu-ultra 403 Forbidden (HTML, via: 1.1 google) Google edge/WAF blocks all requests incl. unauthenticated / — geo/WAF block from test infra, not a mapping/URL bug Infra (see below)
azure-ai-foundry/grok-4-1-fast-reasoning 404 DeploymentNotFound Foundry resource has no grok deployment (404 for every name) Infra (unprovisioned)
azure/gpt-oss-120b 404 DeploymentNotFound Azure resource has zero deployments (data: []) Infra (unprovisioned)
together-ai/gpt-oss-120b 503 Service Unavailable Provider-side outage (single/multi-turn passed in CI; the tool-call test caught the blip) Transient
aws-bedrock/claude-sonnet-4-6 Works now (valid tool_call) CI failure was a ~32s cold-start timeout, not an error Transient flake

Change

Only the Moonshot failure is a real, code-fixable mapping bug. This PR deactivates the retired kimi-k2-thinking mappings:

  • moonshot/kimi-k2-thinking → deactivatedAt
  • bytedance/kimi-k2-thinking (-251104) → deactivatedAt
  • moonshot/kimi-k2-thinking-turbo → deactivatedAt

The model keeps its alibaba provider (test: skip, active until its own 2026-07-08 deactivation), so it is not orphaned.

The other five are not mapping bugs: two are unprovisioned Azure resources (deployments need creating), one is a geo/WAF block on Sakana's endpoint, and two are transient provider hiccups. None are fixable by editing model definitions — flagging for an infra decision (provision the Azure deployments; confirm whether Sakana is reachable from gateway infra, else mark test: "skip").

Verification

  • turbo run build — 17/17 ✓
  • providers.spec / model-metadata.spec / compliance.spec — 36/36 ✓
  • Live re-test: moonshot/bytedance kimi-k2-thinking all 404; mappings now excluded from e2e

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Bug Fixes
    • Updated Moonshot model availability by deactivating select offerings.
    • Added a deactivation timestamp for the kimi-k2-thinking family providers (including kimi-k2-thinking-251104 and kimi-k2-thinking-turbo) as of 2026-06-28.
    • Ensures affected options clearly reflect their unavailability date.

Moonshot dropped the kimi-k2-thinking models from its API (live
/v1/models now only lists k2.5/k2.6/k2.7), and BytePlus Ark dropped
every kimi-k2-thinking snapshot too. Both 404 in e2e. Deactivate the
moonshot + bytedance kimi-k2-thinking mappings and the moonshot
kimi-k2-thinking-turbo mapping. The model keeps its alibaba provider
(test: skip), so it is not orphaned.

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

coderabbitai Bot commented Jun 28, 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: b3981857-a879-401e-9f67-75db4bc82997

📥 Commits

Reviewing files that changed from the base of the PR and between 7d4fa48 and c0acbbf.

📒 Files selected for processing (1)
  • packages/models/src/models/moonshot.ts
💤 Files with no reviewable changes (1)
  • packages/models/src/models/moonshot.ts

Walkthrough

Adds deactivatedAt: new Date("2026-06-28") to three provider entries in moonshot.ts: two under kimi-k2-thinking and one under kimi-k2-thinking-turbo.

Changes

Moonshot model deactivation

Layer / File(s) Summary
Provider deactivation dates
packages/models/src/models/moonshot.ts
Adds deactivatedAt: new Date("2026-06-28") to the moonshot and bytedance providers for kimi-k2-thinking, and to the moonshot provider for kimi-k2-thinking-turbo.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

🚥 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 clearly matches the change: deactivating retired Moonshot kimi-k2-thinking model lines.
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.
✨ 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 monterrey-v5

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.

@steebchen
steebchen enabled auto-merge June 28, 2026 15:26
@steebchen
steebchen added this pull request to the merge queue Jun 28, 2026
Merged via the queue into main with commit 4af4c11 Jun 28, 2026
17 checks passed
@steebchen
steebchen deleted the monterrey-v5 branch June 28, 2026 15:46
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