All news briefs
Product update

Mistral releases version 2.5.0 of its TypeScript SDK

The story in five sentences

  1. Mistral AI has released version 2.5.0 of its official TypeScript client.
  2. GitHub marks the release as final rather than a prerelease.
  3. The publication was created automatically by the GitHub Actions bot.
  4. The release notes say the generated client is based on an OpenAPI description and the Speakeasy CLI.
  5. The release notes do not identify specific new features or breaking changes.

Full explanation

Mistral AI published version 2.5.0 of its TypeScript client on July 17 at 08:16 UTC. GitHub classifies the release as stable rather than a prerelease and marks it as immutable. It points to a target commit beginning with 11368f, while the page provides no additional downloadable artifacts. The corresponding npm package is @mistralai/mistralai 2.5.0.

The publication was produced by the GitHub Actions bot rather than written manually by a maintainer. Its metadata says the client was created on July 10 from an OpenAPI description with Speakeasy CLI tooling. The page records the tool versions used for that generation, but it does not explain changes from the preceding client release.

The evidence establishes that a new final version of the generated TypeScript client exists. It does not establish which endpoints, types, fixes, or behavioral changes are new. The release offers no migration instructions, compatibility notes, or explicit list of breaking changes. Developers cannot infer the practical effect on an existing integration from this release page alone.

Privacy setting

May we measure pseudonymous page views and session replays?

With your consent, PostHog EU measures which pages are opened and additionally records your session: mouse movement, clicks, scrolling and the rendered page content are stored as a replayable reconstruction. Typed input is masked before sending. The contents of sign-in, sign-up, password recovery, the founder chat, the newsletter field, your email display, your quiz answers and the checklists are not recorded at all; on the sign-in and sign-up pages recording is paused. Addresses are always stored without query parameters. A random device identifier and technical connection data such as the IP address are processed as well. In addition, strictly defined usage events are measured: how far a post was read, which article element was used, which call to action was clicked, how a newsletter sign-up ended, how far you get in a course or in the feed (recording only whether a task was correct or incorrect, never your answer itself), which video you start, whether you switch the language, and how a sign-in or sign-up attempt ended — without the email address, without the password, and without the error message. Only values from a fixed list and whole numbers from fixed ranges are transmitted — no input and no free text. We also label production, internal, and automated test visits separately and derive whether a visit came from a known interface such as ChatGPT, Claude, or Perplexity from a known referring domain or a strictly allowed campaign value. The full referring address and query parameters are not sent, and this cannot identify a specific AI model. If PostHog's IP-based geo enrichment is enabled in the project, the service can derive an approximate country, continent, and region; we do not request browser or GPS location. Every visit is also assigned to a page area from a fixed list (for example home, blog, tools, account) — the area is sent, not the address. Page loading and stability metrics are measured as well (Core Web Vitals: LCP, CLS, INP, FCP), without network payloads. A click on a link leading away from the site is recorded only as the target domain from a fixed list, without path, query parameters, or link text. For the Idea Wheel, AI Labelling and Limit Reset tools only the kind of action is measured — spin, option changed, copy or export, for instance — never your input and never a result. Learn more about privacy

Without your consent no analytics code is loaded and nothing is recorded. You can withdraw at any time: withdrawal ends collection immediately; data already collected may have been transmitted by then and is deleted after the storage period.