What is in this release
Envzn 0.8
Run evc --version for the compiler's version; the tables below list every component's.
0.8 names the language package as a whole: the compiler,
the intermediate representation, the kernel and the standard library, shipped
together and tested together. Every component inside carries its own version and
they move independently, because they are developed independently: a fix to the
JSON parser is not a new compiler.
The three that must stay in step
The compiler, the EvIR and the kernel can each change on their own, but they are fundamentally in sync: the compiler emits an EvIR the kernel's headers expect, and a mismatch between any two of them is a defect rather than a configuration. They are versioned separately so a change can be described precisely, not so they can drift apart.
| Component | Version | What it is |
|---|---|---|
Compiler (evc) |
6.3.0+56e | The canonical compiler. Its own lineage, independent of the release number. |
| EvIR | f4bd86e2f3cb3904 (schema hash) |
The serialized intermediate-representation format, named by its schema hash, which moves exactly when the format does. |
Kernel (ENVZN) |
8.1.4+264 | Text, collections, math, time and I/O — what every Envzn program rests on. |
The standard library
Each module is versioned by its own manifest and released with the package.
| Module | Version |
|---|---|
Data |
2.1.4+5d |
Json |
3.0.2+2c |
Logger |
0.2.5+1a |
Networking |
2.0.8+45 |
Regex |
1.0.3+1e |
diagnostics |
2.11.0+1a |
epm |
3.8.1+8b |
evTest |
0.1.6+12 |
mda |
0.2.0+e |
The language edition
Module manifests also carry a language_version — currently 2.0. That is an
edition marker, in the sense Rust means by edition = "2021": it states which
level of the language a module is written against, so the compiler knows how to read
it. It is not a maturity claim and is unrelated to the release number above.
Copyright © 2026 The Data Science Group, LLC.