Jev Version Tracking

Release notes and behavior changes for each Jev version, starting from 1.13.

Jev version FAQ

+ What is the newest Jev version?

Jev 1.14 is the newest version as of 2026-11-04. TypeSafe’s model changelog lists it under October 14, 2026 with model ID jev-1.14.0, and OpenRouter serves it as the versioned slug typesafe/jev-1.14 (endpoint typesafe/jev-1.14-20261014). The previous release, 1.13, was published in September 2026 and is still served as typesafe/jev-1.13.

+ How do I check which Jev version answered my request?

Read the model field in the response body. Every response carries a model string with the versioned ID that answered, for example jev-1.14.0, so a log row tells you which version produced it. That matters if you pin a version instead of using the jev-latest alias, and it is the only reliable way to attribute historical rows after an upgrade.

+ What do the jev-latest and jev-preview aliases point to?

Both currently resolve to jev-1.14.0. The official models page states that jev-latest points at the newest release, which is 1.14, and that jev-preview points at the same model because no preview build exists right now. If you need a fixed version, pin the versioned ID instead of the alias.

+ Where are the Jev release notes?

The official changelog is at docs.typesafe.ai/changelog, and each version on this site has its own page that restates the published change set and names what is still unpublished: Jev 1.14 and Jev 1.13. The 1.14 entry lists exactly four changes — new model ID, better multilingual support, Box questions, and images in state, instructions and criteria — plus two items, image support and long context, that the changelog notes also work on 1.13.

+ Did the price change between Jev versions?

No. The official models page shows the same price for 1.13 and 1.14: $42 per billion input tokens, or $0.042 per million input tokens, with output tokens free. The OpenRouter endpoints API returned 0.000000042 per prompt token for both versioned slugs when checked on 2026-11-04. Pricing can move independently of version numbers, so re-check before you budget.

+ Do I have to migrate code to move from 1.13 to 1.14?

Not the request shape, if you already send text questions to a versioned slug. The work is in three places: the model string if you pin a version, the confidence threshold you tuned on 1.13, and any logging that assumes a fixed answer shape — Box answers add a box field that text questions never return. Image support and long context are additive and gated behind headers, so a text-only path keeps working unchanged.