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 pinning notes — not an official changelog microsite. Models page: aliases resolve to versioned ids; response model reports who answered. docs.typesafe.ai/models. Replicas are not Jev and not endorsed. We do not issue keys.
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-latestOK - 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.modelalways
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.
Release discipline after the triple
Treat a criteria edit the way you treat a binary bump: PR, replay gold, promote. Live-tweaking τ in a console is how floors rot when jev-latest moves. Official: aliases resolve; response.model tells you who answered. Log it always. Alert when it drifts — monitoring and version pinning.
Do not paste a pin across doors and assume the card’s context limit or error set followed you. Details: models and aliases. jev-preview is never a silent alias on the money path.
Door-specific model strings (checklist)
- First-party HTTP/SDK: versioned id in the request; pin
jev-1.13.0if floors exist. - Marketplace / gateway: use their documented id. 402 and verification codes are callouts.
- Dev:
jev-latestis acceptable if you accept drift. - Preview: isolated door, labeled in traces.
- Never: a SemIf/OpenJev weight tagged as
jev-1.13.0. That is not Jev.
Vendor list price $0.042 / M input (confirm models page) is not a version. Do not “upgrade” by chasing a blog multiple.
When not to use this page’s advice
Do not treat this as TypeSafe’s changelog. Do not skip the harness because the alias name looks the same. Do not mix boolean and noul while “just changing the pin.” Schema-safe responses from a new id are still not a proof the floors still mean what you think.
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.
Can I pin in code comments only?
No. Pin in the request. Comments do not stop jev-latest.
Do question SHA and model id version together? Promote them as one release. Changing both at once without a split report hides the cause.
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.