feat: upgrade MiniMax default model to M3#85
Merged
Conversation
- Set MiniMax-M3 as the default model in the configuration example - Update the available models list to put M3 first while keeping M2.7 and M2.7-highspeed for backward compatibility - Drop M2.5 / M2.5-highspeed from the documented model list since they are superseded by the M2.7 / M3 generations - Update test fixtures and assertions in test_minimax_client.py to use MiniMax-M3 as the default test model
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrade the documented default MiniMax model from
MiniMax-M2.7to the newerMiniMax-M3, and clean the legacy M2.5 generation out of the published model list.Changes
docs/configuration.mdmodelvalue fromMiniMax-M2.7toMiniMax-M3MiniMax-M3first and dropMiniMax-M2.5/MiniMax-M2.5-highspeed(still keepingMiniMax-M2.7andMiniMax-M2.7-highspeedas compatible options)tests/test_minimax_client.py_make_configdefault and the two model-name assertions fromMiniMax-M2.7toMiniMax-M3No other code paths reference the model ID (the
OpenAIClientusesconfig.modelopaquely), so the runtime behavior for users who already setmodelexplicitly is unchanged. Only the documented default and the test fixture are updated.Notes
api.minimax.io/v1), API key env var (MINIMAX_API_KEY),_NO_RESPONSE_FORMATand_TEMP_CLAMPlists are untouched — M3 inherits the same OpenAI-compatible quirks as M2.7.Test plan
pytest tests/test_minimax_client.py— 21 passed (all OpenAIClient init / completion / factory tests green after the model-name update)