Problem
The package version is defined in two places with different values:
minimax_mcp/__init__.py: __version__ = "0.0.17"
pyproject.toml: version = "0.0.18"
Exact location
minimax_mcp/__init__.py:3 — __version__ = "0.0.17"
pyproject.toml:3 — version = "0.0.18"
Impact
importlib.metadata.version("minimax-mcp") returns 0.0.18 (from pyproject.toml)
minimax_mcp.__version__ returns 0.0.17 (from init.py)
- Confusing for debugging and version tracking
Proposed solution
Use a single source of truth for versioning. Two options:
Option A (recommended): Use importlib.metadata in __init__.py:
from importlib.metadata import version
__version__ = version("minimax-mcp")
Option B: Sync manually — update __init__.py to 0.0.18 and add a CI check that both match.
Acceptance criteria
minimax_mcp.__version__ matches the version in pyproject.toml
- Only one source of truth for the version number
Problem
The package version is defined in two places with different values:
minimax_mcp/__init__.py:__version__ = "0.0.17"pyproject.toml:version = "0.0.18"Exact location
minimax_mcp/__init__.py:3—__version__ = "0.0.17"pyproject.toml:3—version = "0.0.18"Impact
importlib.metadata.version("minimax-mcp")returns0.0.18(from pyproject.toml)minimax_mcp.__version__returns0.0.17(from init.py)Proposed solution
Use a single source of truth for versioning. Two options:
Option A (recommended): Use
importlib.metadatain__init__.py:Option B: Sync manually — update
__init__.pyto0.0.18and add a CI check that both match.Acceptance criteria
minimax_mcp.__version__matches the version inpyproject.toml