feat: upgrade MiniMax default model to M3#543
Merged
Conversation
- Update sample test models from MiniMax-M2 / MiniMax-M2.7 to MiniMax-M3 - Extend capabilities test to cover M3 alongside M2.7 / M2.7-highspeed - M3 introduces a 512K context window, 128K max output, and image input support - Older models (M2.5/M2.1/M2/M1) are no longer first-class targets
vaskoyudha
added a commit
to vaskoyudha/deeptutor-for-programmer-fork
that referenced
this pull request
Jul 25, 2026
feat: refresh MiniMax model identifiers in tests to M3 MiniMax-M3 is the current default on the MiniMax platform; refresh the model-id strings used in the capability/runtime tests and add M3/M2.7 assertions. Provider capability resolution is keyed on the 'minimax' prefix, so this is behavior-neutral (no production code changed). Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
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 MiniMax model references in tests to use MiniMax-M3 as the current default, while still asserting capability behavior for the M2.7 family that remains supported.
Changes
tests/services/llm/test_capabilities.py— extendtest_minimax_openai_compat_supports_tools_without_response_formatto coverMiniMax-M3andMiniMax-M2.7in addition to the existingMiniMax-M2.7-highspeedassertions.tests/services/config/test_provider_runtime.py— update the sample MiniMax model fromMiniMax-M2.7toMiniMax-M3intest_llm_minimax_binding_uses_minimaxi_endpointso the test exercises the new default model.tests/core/test_agentic_client_provider_kwargs.py— update theminimax_anthropicnative-tool-calling assertion fromMiniMax-M2toMiniMax-M3. (MiniMax-M2is no longer a first-class target on the MiniMax side.)Why
MiniMax-M3 is the current default model on the MiniMax platform. It introduces:
DeepTutor's MiniMax /
minimax_anthropicproviders already accept arbitrary model strings, so the only meaningful in-tree change is to refresh the model identifiers used in tests so they match what users will actually configure today. The provider capability matrix (noresponse_format, tools enabled, etc.) is unchanged.Test Plan
MiniMax-M2.7-highspeedbehavior.MiniMax-M3andMiniMax-M2.7get the same capability flags via the existing provider entry (supports_tools=True,supports_response_format=False).