Mistral AI v2.0.0

Descripción Detallada

A technical release focused on improving developer experience and parity with the Python SDK v2. What's new Schema naming conventions 42 request/response types renamed to follow consistent conventions: - Request bodies: `{Verb}{Entity}Request` (e.g. `CreateAgentRequest`) - Responses: `{Verb}{Entity}Response` (e.g. `ListFilesResponse`) - Entities: `{Entity}` (e.g. `BatchJob`, `Checkpoint`) See MIGRATION.md for the full rename table. Forward compatibility - Enums now accept unknown values, new API values won't crash old SDK versions - Discriminated unions get an `Unknown` variant for the same reason Automatic schema conflict resolution Speakeasy's `nameResolutionFeb2025` flag is enabled, automatically detecting and resolving ambiguous type names during generation (e.g. `Tools` → `ConversationRequestTool`). Native ES Modules The SDK now ships as ESM, enabling tree-shaking, faster startup, and better compatibility with modern bundlers and runtimes. Zod v4 Runtime validation upgraded from Zod v3 to Zod v4. GCP SDK rename `MistralGoogleCloud` → `MistralGCP` and `MistralGoogleCloudError` → `MistralGCPError` Breaking changes - 42 type renames (see MIGRATION.md) - ESM only — CommonJS `require()` no longer supported - Zod v4 — if you import SDK schemas directly, they are now Zod v4 schemas - GCP class: `MistralGoogleCl