Update MiniMax provider defaults for MiniMax-M3#1056
Conversation
Signed-off-by: octo-patch <266937838+octo-patch@users.noreply.github.com>
|
@octo-patch is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
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 (8)
📝 WalkthroughWalkthroughMiniMax configuration now defaults to MiniMax-M3, documents global and China endpoints, normalizes ChangesMiniMax provider update
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Supersedes #1032 with a clean signed-off commit from current main.
Summary
MiniMax-M3the default while retainingMiniMax-M2.7as a documented override./v1/messagessuffix.Testing
npm test -- test/minimax-provider.test.ts test/fallback-model-resolution.test.ts test/fetch-timeout.test.tsnpm run buildnpm test -- --exclude test/hook-project.test.tsnpm test -- test/hook-project.test.tswith the expected checkout basenameSummary by CodeRabbit
New Features
Documentation
Bug Fixes
/v1/messagesendpoint.