feat: upgrade MiniMax model references to M3#571
Conversation
Update the MiniMax example agent and related fallback samples to use the new MiniMax-M3 model as the default, while keeping M2.7 (including M2.7-highspeed) as supported options for backward compatibility. - examples/beginner/minimax_example.py: switch default id to MiniMax-M3 - tests/unit/test_minimax_example.py: assert M3 usage and refresh the known-models set - gateway/.env.example, gateway/src/config/loader.ts: update OpenRouter fallback example to minimax/minimax-m3 - gateway/tests/provider/openrouter-body-injection.test.ts: refresh test fixture to use the new model id
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThis PR updates the MiniMax model reference from M2.7 to M3 across the beginner example, configuration documentation, and all test fixtures. The agent example now uses MiniMax-M3 by default, with matching updates to environment examples, loader documentation, and test assertions to validate consistent usage. ChangesMiniMax Model Version Upgrade
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
examples/beginner/minimax_example.pyor the OpenRouter fallback snippets get the older model unless they edit by hand. Documentation and tests were also out of sync.MiniMax-M3, refresh the OpenRouter fallback snippet tominimax/minimax-m3, update related fixtures and the model-allowlist test. KeepMiniMax-M2.7andMiniMax-M2.7-highspeedas still-supported options for backward compatibility.MINIMAX_API_KEY), Anthropic / OpenAI providers, anything outside MiniMax model identifiers.Change Type
Scope
User-Visible / Behavior Changes
examples/beginner/minimax_example.pynow talks toMiniMax-M3by default (previouslyMiniMax-M2.7). Users on M2.7 can still passid="MiniMax-M2.7"explicitly.minimax/minimax-m3.Security Impact
NoNoNo(samehttps://api.minimax.io/v1endpoint, sameMINIMAX_API_KEY)NoNoVerification
Steps to Test
rg -n "MiniMax-M" examples/beginner/minimax_example.py tests/unit/test_minimax_example.py— confirmsMiniMax-M3is the default andMiniMax-M2.7(-highspeed)is still allow-listed.uv run pytest tests/unit/test_minimax_example.py— static checks on the example pass against the new model id.rg -n "minimax/minimax-m" gateway/.env.example gateway/src/config/loader.ts gateway/tests/provider/openrouter-body-injection.test.ts— fallback fixture aligned.Expected Behavior
test_example_uses_minimax_m3and the OpenRouter fallback unit test pass.test_valid_minimax_modelsaccepts the refreshed allow-list.Compatibility / Migration
Yes— M2.7 / M2.7-highspeed still work; only the default identifier changed.NoNoRisks and Mitigations
MiniMax-M2.7won't be affected (we kept it allow-listed); only the example default changed.Checklist
Summary by CodeRabbit
Documentation
Tests