Add MiniMax M3 and M2.7 model metadata#2438
Open
octo-patch wants to merge 1 commit into
Open
Conversation
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
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.
Description
Add MiniMax-M3 and MiniMax-M2.7 metadata to GraphRAG's model cost registry. The metadata covers context windows, supported modalities, reasoning, prompt caching, and current token pricing, including MiniMax-M3 long-context and priority tiers.
This replaces #2428 with a clean branch based on the latest
mainand complete target coverage.Proposed Changes
Validation
uv run poe checkuv run pytest tests/unit/model_cost_registry/test_model_cost_registry.py tests/integration/language_model/test_factory.py -q(12 passed)uv run poe test_unit(310 passed)uv run poe builduv run poe build_docsChecklist