Open· Last updated 2026-09-21

Jev versioning guide

Versioning is two clocks: model id (jev-1.13.0 vs jev-latest / jev-preview) and your questions git SHA. Mixing them is how floors rot.

Independent. Models page: aliases resolve to versioned ids; response model reports who answered. docs.typesafe.ai/models.

Independent angle (cover, do not clone)

Win delta (status-and-changelog): pinning + alias policy; outbound docs/changelogs; not a status-page or changelog clone.

Policy we recommend

• Dev: jev-latest OK
• Prod with floors: pin jev-1.13.0 (or current versioned id)
• Preview: isolated door, never silent
• Promote pins like you promote binaries
• Log response.model always

Changelogs

SDK changelogs are official and outbound. Model behavior changes belong on TypeSafe’s models/jaggedness pages. We will not invent a daily Jev changelog feed.

Promote like a binary

questions@sha + model:jev-1.13.0 + door id = a release. Staging runs the harness. Prod gets the same triple. jev-preview is a separate environment.

If OpenRouter says typesafe/jev-1.13 and first-party says jev-1.13.0, those are different strings. Record both.

What this page does not claim

• Not an official changelog.

FAQ

Is jev-1.13 the same as jev-1.13.0? First-party docs pin the versioned id. Some doors use typesafe/jev-1.13. Do not paste across doors.

When jev-preview ≠ jev-latest? When TypeSafe ships a preview build. Models page said they currently match at the time we read it — re-check.

Disclaimer

This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.

Open-cluster pages are independent field-guide notes. Replicas and third-party interfaces mentioned anywhere on jev.pro are not Jev and not endorsed. Hub: Open. Siblings: monitoring guide, version pinning, models and aliases. Canonical: https://docs.typesafe.ai.