feat: add MiniMax provider configurations#738
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.
Reason: add MiniMax-M3 and MiniMax-M2.7 to the existing provider registry.
This adds four selectable MiniMax configurations covering global and China regions across the supported protocol paths. It also adds shared API key handling, endpoint overrides, Docker defaults, and captured request-path tests.
Checks:
.venv/bin/python -m pytest -q tests/test_minimax_provider.py.venv/bin/python -m ruff check --select E9,F63,F7,F82 src/utils/config.py src/utils/llm_provider.py tests/test_minimax_provider.py.venv/bin/python -m compileall -q src/utils/config.py src/utils/llm_provider.py tests/test_minimax_provider.pydocker compose config -q