Skip to content

feat(models): retire mimo-v2.5 from the site catalogue - #110

Merged
sre-helmcode merged 1 commit into
mainfrom
feat/retire-mimo-v25
Sep 28, 2026
Merged

sre-helmcode merged 1 commit into
mainfrom
feat/retire-mimo-v25

Conversation

@sre-helmcode

Copy link
Copy Markdown
Contributor

What

mimo-v2.5 removed from every member-facing enumeration: home table
(modelos.json), /docs/models cards (en/es), choose-a-model (en/es),
opencode/vscode/pi guides (en/es, LLM counts 8 -> 7), OpenAPI reference
(chat-models/vision lists + Model catalog row), rate-limit tables and
the canonical mdxToText fixture. The examples page now demonstrates
mimo-v2.6-flash (same API shape; the old id still works through the
alias during the window).

Why

Owner order: retire mimo-v2.5 one day after mimo-v2.6-flash shipped with
identical limits. The legacy name keeps working via the
model_group_alias in the proxy (nan-devops PR); it is no longer
published as a model.

Test evidence

  • npm test: 1305/1305 (the cross-surface consistency tests drive every enumeration).
  • npm run build: exit 0.

mimo-v2.5 was retired from the community on 2026-09-25 and now routes
through a model_group_alias onto mimo-v2.6-flash (one-week window).
Drop it from every member-facing enumeration: home table, /docs/models
cards (en/es), choose-a-model, the opencode/vscode/pi guides (counts
8 -> 7), the OpenAPI reference, and the per-model limit tables/fixture.
The examples now point at the surviving mimo-v2.6-flash id. Internal
metering keeps the legacy name capped for the window (cloud-api and the
hooks are unchanged in this repo).
@sre-helmcode
sre-helmcode merged commit e1fd64b into main Sep 28, 2026
2 checks passed
@sre-helmcode
sre-helmcode deleted the feat/retire-mimo-v25 branch September 28, 2026 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants