
v1.2.0
Egress control, descriptor ownership, security hardening
The second minor release. 2,241 tests, 435 stdlib modules.
Every release, newest first. Releases are signed.

v1.2.0
The second minor release. 2,241 tests, 435 stdlib modules.
Patch release.
Patch release fixing three adopter-reported v1.1.0 regressions.
The first feature release on the 1.0 line.
A security release on the 1.0 line.
38 commits on the 1.0 line (v1.0.1 was a one-day patch carrying E0331, the trait-bound fix and the shared macOS container VM).
And the clock became a capability.
rc3 closes every finding from the rc2 security scan (H-1 through H-9, M-1 through M-15) and adds three CI gates that did not exist…
Reproducible across two machines.
The engine moves inside the language.
The OWASP injection family is eliminated at the level of the grammar, not patched at runtime.
Generics, async, Secure<T, State>, native containers.
And a BSI TR-02102-2 TLS audit.
Newest first. This is the full record behind the claims on the home page, including the audits that found our own bugs. Findings are named rather than hidden, and corrected when they turn out to be wrong.
A parallel bug hunt found nine expression positions where the typechecker never called check_expr at all.
Four threads of work landed in the same week.
Four modules landed that turn kern from a language you deploy onto a cloud into one you can build a cloud out of, and they share a design decision…
The isolation story went from a proof of concept to a multi-tenant platform in one wave.
An adopter put it plainly: the documentation is what actually gets read, so a document promising a capability the code does not deliver is a false…
Compile throughput was profiled end to end and three root causes fell out, each fixed without a rewrite.
Kern is now addressable by code-generating models as a first-class consumer.
Kern reaches the device tier without a C dependency.
The standard library grew from 303 modules to 354, and from 2,219 public functions to 2,982, in three deliberate directions.
Test coverage was being measured the flattering way.
A sustained hardening wave gave the runtime a ceiling wherever a remote peer chooses the cost.
The July trust push turned the “real but manually verified” caveats into blocking CI jobs.
Secret is now a first-class compile-time taint tag alongside PersonalData<T> (E0302) and Untrusted<T> (E0303): a secret reaching any sink that does…
The data-confidentiality track is complete: all five network transports now do TLS.
Five independent audits of the language itself were folded into one ranked register (docs/design/language-security-hardening-2026-08.md), which…
Every Kern binary now seals itself, before user code runs, to a seccomp-BPF filter that permits only the syscalls its capability set grants, and…
A Kern service's identity on the network is now the SHA-256 of its own reproducible binary: kern_attest_self_hash() measures the running executable…
The container engine's full mode (host bridge, veth pairs, NAT, inter-container networking) now runs for a non-root launcher: install-caps.sh grants…
The container engine now extends beyond Linux namespaces.
All authority-bearing entry points: network, filesystem, process, FFI, environment access: now require explicit Cap<T> capabilities.
Selective monomorphization for stdlib hot paths: List<T>, Map<K,V>, Result<T>, Option<T>, Decimal: emitted as linkonce_odr typed wrappers so…
init / build / run / test / add / remove / verify / install / publish / search / update with manifest [dependencies] / [dev-dependencies] parsing.