feat: upgrade MiniMax default model to M2.7

[octo-patch]

Summary

Upgrade MiniMax model configuration to include the latest M2.7 model as default.

Changes

• Add MiniMax-M2.7 and MiniMax-M2.7-highspeed to the model selection list
• Set MiniMax-M2.7 as the new default model (first in list)
• Retain all previous models (M2.5, M2.5-highspeed) as available alternatives
• Update model documentation with M2.7 pricing
• Add unit tests for M2.7 model configuration

Why

MiniMax-M2.7 is the latest flagship model with enhanced reasoning and coding capabilities. It offers better performance at competitive pricing ($0.3/M input, $1.2/M output).

Testing

• Unit tests updated and passing (17/17)
• All existing tests continue to pass

---

Note

Medium Risk
Changes MiniMax model selection defaults by placing MiniMax-M2.7 first in the supported model list, which can alter runtime model choice for MiniMax users. Otherwise it’s mostly catalog/documentation/test updates with limited code-path changes.

Overview
Upgrades the MiniMax model catalog to include MiniMax-M2.7 and MiniMax-M2.7-highspeed, and makes MiniMax-M2.7 the effective default by putting it first in supported-models.json (while keeping the existing M2.5 options).

Updates docs/models.md with the new MiniMax entries/pricing, adds a changeset for a minor release, and extends minimax provider unit tests to assert the new models exist and are ordered first.

^{Written by Cursor Bugbot for commit 62a1b92. This will update automatically on new commits. Configure here.}

Summary by CodeRabbit

• New Features

  • Added support for MiniMax-M2.7 and MiniMax-M2.7-highspeed models with enhanced reasoning and coding capabilities.

• Documentation

  • Updated model documentation to include pricing and specifications for the new MiniMax models.

• Tests

  • Added test coverage for the new MiniMax models to ensure proper support and configuration.

[changeset-bot]

🦋 Changeset detected

Latest commit: 62a1b92

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds support for two new MiniMax models (M2.7 and M2.7-highspeed) across the codebase. Changes include a changelog entry, documentation updates for model pricing, model configuration entries with specifications, updated source code documentation, and corresponding test validation to ensure the new models are properly registered and available.

Changes

Cohort / File(s)	Summary
Changelog & Documentation .changeset/upgrade-minimax-m27.md, docs/models.md	Added changelog entry for MiniMax model upgrade and documented new M2.7 and M2.7-highspeed models with pricing details (input costs 0.3/0.6, output costs 1.2/2.4 respectively).
Model Configuration scripts/modules/supported-models.json	Registered two new MiniMax models (M2.7 and M2.7-highspeed) in the supported models registry with full specifications including costs, token limits, and role assignments.
Implementation src/ai-providers/minimax.js	Updated class documentation comment to reflect M2.7 as the default MiniMax model instead of M2.5.
Test Coverage tests/unit/ai-providers/minimax.test.js	Added runtime loading of supported-models.json and new test suite validating presence, ordering, and backward compatibility of MiniMax models.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• feat: add MiniMax as a first-class AI provider #1652: Directly related through modifications to MiniMax model entries in supported-models.json and corresponding test updates.

Suggested reviewers

• eyaltoledano
• Crunchyman-ralph

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title accurately summarizes the main objective—upgrading the MiniMax default model to M2.7—which is clearly reflected across all modified files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

docs/models.md (1)

126-127: This file is CI-generated and should not be manually edited.

Based on learnings, docs/models.md is auto-generated by CI from scripts/modules/supported-models.json via the workflow .github/workflows/update-models-md.yml. Manual edits here may cause merge conflicts or be overwritten when CI regenerates this file.

Since scripts/modules/supported-models.json is correctly updated in this PR, consider removing the manual edits to this file and letting CI regenerate it. Based on learnings: "This repo's supported models list is CI-generated into docs/models.md from scripts/modules/supported-models.json... Don't request manual edits to the Markdown; ensure the JSON is correct instead."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/models.md` around lines 126 - 127, The manual edits to docs/models.md
should be removed because this file is CI-generated; revert the changes in
docs/models.md (remove the added MiniMax lines) and ensure the canonical source
scripts/modules/supported-models.json contains the new MiniMax entries, then let
the workflow .github/workflows/update-models-md.yml regenerate docs/models.md
during CI; target files/functions: docs/models.md (revert),
scripts/modules/supported-models.json (verify/update).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docs/models.md`:
- Around line 126-127: The manual edits to docs/models.md should be removed
because this file is CI-generated; revert the changes in docs/models.md (remove
the added MiniMax lines) and ensure the canonical source
scripts/modules/supported-models.json contains the new MiniMax entries, then let
the workflow .github/workflows/update-models-md.yml regenerate docs/models.md
during CI; target files/functions: docs/models.md (revert),
scripts/modules/supported-models.json (verify/update).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 18b1f87d-d8d7-4ce8-9246-50dd8004e0b4

📥 Commits

Reviewing files that changed from the base of the PR and between 8086ff7 and 62a1b92.

📒 Files selected for processing (5)

• .changeset/upgrade-minimax-m27.md
• docs/models.md
• scripts/modules/supported-models.json
• src/ai-providers/minimax.js
• tests/unit/ai-providers/minimax.test.js