Jev version pinning
Version pinning is how you keep floors honest. Two clocks exist: the model id TypeSafe resolves (jev-1.13.0 vs jev-latest / jev-preview) and your questions git SHA. Mixing them is how last quarter’s τ silently misfires.
This is the access-cluster how-to. Policy essay: versioning guide. Independent. Models page: docs.typesafe.ai/models. We do not issue keys and we are not a status page.
Independent angle (cover, do not clone)
Win delta (status-and-changelog): pinning + alias policy; outbound official models/changelogs; not a cloned “is Jev down” or daily changelog microsite.
What to pin
| Environment | Model field | Why |
|---|---|---|
| Local / CI unit | Mock client | No network flake in PR |
| Dev integration | jev-latest OK |
You are not fitting floors yet |
| Staging harness | Versioned id (jev-1.13.0 today) |
Gold must match prod |
| Production with floors | Same versioned id as staging | Promote like a binary |
| Preview experiments | Isolated door / separate config | Never silent swap onto prod |
Log response.model on every production call. Alert when it ≠ the pin (monitoring).
Door strings are not portable
First-party HTTP uses ids like jev-1.13.0. Some marketplaces use typesafe/jev-1.13 or other prefixes. Those are different strings. Record door + id together. See channels compared.
Do not copy a first-party noul example into a door that documents boolean without reading that door.
How to promote
questions@sha + model:jev-1.13.0 + door id = a release. Staging runs the harness (testing). Prod gets the same triple. jev-preview is a separate environment even if the models page once said it matched jev-latest — re-check; we will not freeze their alias table here.
SDK changelogs are official and outbound. We will not invent a daily Jev changelog feed.
Vendor claims
List price and rate-limit figures live on TypeSafe’s models page and can change. Treat $0.042 / M input (jev-1.13, output free on that page) as a vendor claim. Pinning does not freeze price.
What this page does not claim
- Not TypeSafe’s changelog or status host.
- Not a guarantee
jev-1.13equalsjev-1.13.0on every door. - Not official TypeSafe.
FAQ
Is jev-1.13 the same as jev-1.13.0?
First-party docs pin the versioned id. Marketing lines and some doors use the shorter string. Do not assume equality — log response.model.
When may I use jev-latest in prod?
Only if you have no fitted floors and accept behavior moves. Once τ exists, pin.
Where is the alias policy essay? Versioning guide. Observability fields: observability.
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.
Access-cluster notes are independent. Hub: Access. Siblings: versioning guide, monitoring guide, models and aliases. Canonical: https://docs.typesafe.ai.
Sources
Public TypeSafe or adjacent documentation only. No private claims.