Skip to content

fix: infer MiniMax vendor for MiniMax models - #6164

Merged
Calcium-Ion merged 2 commits into
QuantumNous:mainfrom
fux-dev:fix/minimax-vendor-inference
Jul 14, 2026
Merged

fix: infer MiniMax vendor for MiniMax models#6164
Calcium-Ion merged 2 commits into
QuantumNous:mainfrom
fux-dev:fix/minimax-vendor-inference

Conversation

@fux-dev

@fux-dev fux-dev commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

⚠️ PR Notice

Important

Models following the MiniMax-* naming convention were not correctly associated with the MiniMax vendor in Model Square. As a result, models such as MiniMax-M3 could be displayed without a provider.

Description

Models using the MiniMax-* naming convention were not correctly mapped to the MiniMax vendor in Model Square. Consequently, models such as MiniMax-M3 could appear without an associated provider.

Previously, the default vendor mapping only recognized MiniMax's legacy abab* model names. This change adds minimax as an additional case-insensitive matching pattern for the existing MiniMax vendor mapping.

A focused regression test has been added to verify that MiniMax-M3 correctly resolves to the MiniMax vendor.

This change does not modify the MiniMax channel's default model list.

The issue was reproduced using the Docker image:

calciumion/new-api:v1.0.0-rc.21

🚀 Type of Change

  • 🐛 Bug fix

📸 Proof of Work

channel-minimax minmax-fixed model-minimax-m3

Summary by CodeRabbit

  • New Features
    • Added vendor recognition for MiniMax models, including MiniMax-M3.
    • MiniMax models now receive the appropriate vendor association and default presentation where configured.

@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

The default vendor rules now recognize models containing minimax as belonging to the MiniMax vendor. A test verifies that MiniMax-M3 resolves to the seeded vendor with the expected exact name rule.

Changes

MiniMax vendor mapping

Layer / File(s) Summary
Add MiniMax rule and validation
model/pricing_default.go, model/pricing_default_test.go
The default vendor rules map minimax to MiniMax, and a test verifies that MiniMax-M3 maps to vendor ID 99 with NameRuleExact.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

Poem

A bunny hops through model names,
“MiniMax!” it softly proclaims.
A rule points the way,
Tests guard the array,
And vendor IDs settle their claims.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: inferring the MiniMax vendor for MiniMax models.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@Calcium-Ion
Calcium-Ion merged commit a63364d into QuantumNous:main Jul 14, 2026
1 check passed
JacksonsY added a commit to JacksonsY/new-api that referenced this pull request Jul 15, 2026
上游 7c28993..a63364d:
- fix: purge authentication data on hard user deletion (QuantumNous#6168) —— 硬删用户时清理
  2FA/备份码/Passkey/Token/OAuth 绑定 + 缓存失效(安全修复,跟上游)。后端文件
  (model/user.go、token.go、twofa.go、controller/user.go、telegram.go) 自动合并为
  并集:上游清理逻辑 + fork 供应商字段/隐藏敏感字段均完整保留(逐文件校验新增行数与
  上游一致)。
- fix: infer MiniMax vendor for MiniMax models (QuantumNous#6164) —— 常规修复,跟上游。
- fix(users): prevent large quota values from overflowing (QuantumNous#6134) —— 纯前端「单元格文本
  溢出」的显示修复(非整数溢出)。冲突文件 users-columns.tsx 按「界面归我们」保留 fork 版
  (语义色 token bg-destructive/warning/success + StatusBadge children API + 卡片式
  meta cardRole/cardSpan/contentMode),未采用上游抽出的 user-quota-cell.tsx(其用
  base 时代的硬编码色/label API,与 fork 设计系统已分叉),该新组件在本合并中删除。

go build ./... 通过;model/controller 测试(含上游新增 user_authentication/telegram/
task_cas 测试)全绿;前端树与 fork HEAD 等价。

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@fux-dev
fux-dev deleted the fix/minimax-vendor-inference branch July 17, 2026 05:44
fux-dev added a commit to fux-dev/new-api that referenced this pull request Jul 19, 2026
* fix: infer MiniMax vendor for MiniMax models

* Delete model/pricing_default_test.go

---------

Co-authored-by: duanxufu <duanxufu@rededa.com>
zhaodechao2008 pushed a commit to zhaodechao2008/new-api that referenced this pull request Jul 27, 2026
* fix: infer MiniMax vendor for MiniMax models

* Delete model/pricing_default_test.go

---------

Co-authored-by: duanxufu <duanxufu@rededa.com>
MinTiang pushed a commit to MinTiang/new-api that referenced this pull request Aug 6, 2026
* fix: infer MiniMax vendor for MiniMax models

* Delete model/pricing_default_test.go

---------

Co-authored-by: duanxufu <duanxufu@rededa.com>
biubiubiu125 pushed a commit to biubiubiu125/newapi that referenced this pull request Aug 8, 2026
* fix: infer MiniMax vendor for MiniMax models

* Delete model/pricing_default_test.go

---------

Co-authored-by: duanxufu <duanxufu@rededa.com>
330079598 pushed a commit to 330079598/new-api that referenced this pull request Aug 19, 2026
* fix: infer MiniMax vendor for MiniMax models

* Delete model/pricing_default_test.go

---------

Co-authored-by: duanxufu <duanxufu@rededa.com>
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.

2 participants