Skip to content

[BOT ISSUE] Mistral: add deprecation markers for retired pixtral-large-2411 and mistral-large-2411 #885

Description

@github-actions

Summary

Two Mistral models were officially deprecated on February 27, 2026, and retired on May 31, 2026, but lack deprecation_date markers in the catalog. Both retirement dates have already passed (today is June 30, 2026). The pixtral-large-latest alias still points to the deprecated pixtral-large-2411.

Without the deprecation_date field, markModelsPastDeprecationDate() in packages/proxy/schema/models.ts will not auto-flag these as deprecated, and they will continue appearing as active models in the UI.

Affected Models

Model ID Current deprecation_date Correct Value Deprecated Retired Line
pixtral-large-2411 (missing) 2026-05-31 2/27/2026 5/31/2026 ~4344
mistral-large-2411 (missing) 2026-05-31 2/27/2026 5/31/2026 ~4306

Both entries otherwise have correct pricing, format, and token limits. Only the deprecation marker is missing.

Note: pixtral-large-latest (line ~4331) still points to the deprecated pixtral-large-2411. Its pricing and metadata remain correct, but it may also warrant a deprecation marker since its target is retired.

Verification

Check Status Detail
Cross-source (deprecation) Mistral models index deprecation table lists both with "Deprecation: 2/27/2026, Retirement: 5/31/2026" AND official replacements (Mistral Medium 3.5 for both)
Already fixed Confirmed both entries lack deprecation_date in model_list.json
Retirement past 5/31/2026 retirement date is 30 days ago
Duplicate check No open issue covers Mistral deprecation markers

Verification Notes

Field Source Notes
Deprecation date 2/27/2026 Mistral models index Listed in the deprecation table
Retirement date 5/31/2026 Mistral models index Both models share the same timeline
Replacement: Mistral Medium 3.5 Mistral models index Official replacement for both

Local Files Inspected

  • packages/proxy/schema/model_list.jsonpixtral-large-2411 (line ~4344) and mistral-large-2411 (line ~4306) both lack deprecation_date
  • packages/proxy/schema/models.tsmarkModelsPastDeprecationDate() (line ~217) checks deprecation_date per entry
{
  "kind": "stale_metadata",
  "provider": "mistral",
  "models": ["pixtral-large-2411", "mistral-large-2411"],
  "status": "deprecated",
  "model_specs": {
    "pixtral-large-2411": {
      "format": "openai",
      "flavor": "chat",
      "multimodal": true,
      "input_cost_per_mil_tokens": 2,
      "output_cost_per_mil_tokens": 6,
      "parent": "pixtral-large-latest",
      "max_input_tokens": 128000,
      "max_output_tokens": 128000,
      "deprecation_date": "2026-05-31",
      "available_providers": ["mistral"]
    },
    "mistral-large-2411": {
      "format": "openai",
      "flavor": "chat",
      "input_cost_per_mil_tokens": 2,
      "output_cost_per_mil_tokens": 6,
      "parent": "mistral-large-latest",
      "fallback_models": ["publishers/mistralai/models/mistral-large-2411"],
      "max_input_tokens": 128000,
      "max_output_tokens": 128000,
      "deprecation_date": "2026-05-31",
      "available_providers": ["mistral"]
    }
  },
  "source_urls": [
    "https://docs.mistral.ai/getting-started/models"
  ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions