LLM API Daily Advisory — 2026-05-18
🚨 Breaking
Nothing today. No forced migrations, no sunset timers ticking across any major provider.
🗑️ Deprecations
No new deprecation notices. Worth watching: Mistral historically issues deprecation notices for prior Small versions 2–3 months after a major release. If you're still pinned to mistral-small-2312 or mistral-small-2409, start your upgrade planning now.
💰 Pricing
No pricing changes announced today. Mistral Small 3.2 ships at the same Small-tier rate as its predecessor — no cost impact on swap.
🆕 Nouveautés
Mistral Small 3.2 — mistral-small-2506 live in the API
Sources: model release · API updated
Mistral shipped Small 3.2 and registered it under the dated identifier mistral-small-2506. If you use mistral-small-latest, the alias already resolves to it — which is the problem in production.
This is a drop-in upgrade: same API contract, same pricing tier, no reported context window change. Relevant if Mistral Small is your cheap routing tier for classification, summarization, or structured extraction at scale.
Pin the dated ID — never run -latest in prod:
# Before — silent alias drift
client.chat.complete(model="mistral-small-latest", messages=[...])
# After — explicit, auditable
client.chat.complete(model="mistral-small-2506", messages=[...])
// TypeScript / raw fetch
const body = {
model: "mistral-small-2506", // previously: "mistral-small-latest"
messages: [...]
};
No migration guide was published — the change is additive. The only risk is structured output parsers or prompt-sensitive pipelines drifting on latest.
💡 Conseil du jour
Grep your codebase for floating aliases — all providers.
Mistral Small 3.2 going live is a good reminder that -latest, -preview, and -turbo aliases across every provider are silent upgrade vectors. One new minor version can shift JSON output structure, tone calibration, or refusal behavior enough to break a downstream parser.
grep -rn 'mistral-small-latest\|claude-3-sonnet\|gpt-4-turbo\|gemini-pro' ./src
Replace every hit with a dated model ID. Add a 90-day calendar reminder to re-evaluate.
Action today: Pin mistral-small-2506 in your staging config, run 30–50 representative prompts (especially structured JSON output calls), confirm schema compliance, then promote. Total time: under 30 minutes.