Release Notes

This page tracks the honest development state of Karkain. The toolchain is a Karkain 1.2.0 (Stable) build: functional, tested, and self-hosted. The v1.2.0 identity is the public label from the v1.2.0 release (1.0.x and 1.1.0 continue as historical lines); the 1.1.0 and 1.0.0 stories are preserved below as history.

Versioning: the CLI reports Karkain Compiler v1.2.0 via karkain --version; the public label progressed Developer Preview (115, v0.115.x) -> Beta 1 (117-118, v0.117.x) -> 1.0.0 (Stable) (Phase 119) -> 1.1.0 (Stable) (Phase 142) -> 1.2.0 (Stable) (Native Independence).

v1.2.0 - Native Independence (current)

Status

Karkain 1.2.0 (Stable) - the project’s public status. Full story: docs/audit/KARKAIN-V1.2.0-GA-QUALIFICATION.md

Theme

Sovereignty I - Off C, Off Go. The native targets are emitted by the SELF-HOSTED compiler, not by a C compiler and not by the Go backend: karkain build --target native-x86_64-<os> produces an image with no gcc and no go on PATH.

What shipped

The native VALUE MODEL in the self-hosted engine: arrays, the heap arena, string operations (concat, push, records, maps) and float64.

The self-hosted engine’s own machine-code ENCODER, the ELF, PE and Mach-O container writers, and the whole-program driver.

The native milestones, each with its own gate: NAT-CALL (user functions), NAT-IF (branches), NAT-QUAL (the qualification), NAT-LOOP (loops, break/continue), NAT-IDX (array indexing and the bounds diagnostic), NAT-FRAME (the frame layout against the Go oracle’s), NAT-STR-STAGE (the string staging area), NAT-RODATA (the reporter’s read-only data) and NAT-REG (register allocation, opt-in).

Compatibility

Every 1.1.0 program builds and runs identically. The surface change is strictly additive; the one behavioural change is that the native targets are now produced by the self-hosted engine.

Release provenance

The 13 published archives were built locally on a Windows host from the tagged commit (v1.2.0, peeled commit 77d7069) using Go 1.21.13 (the CI workflow’s Go version); GitHub Actions could not execute the release matrix because the account was subject to a billing/payment restriction. This is a locally built and published release, NOT a CI-green release. The tag-triggered workflow did not complete. Checksums were independently verified.

Known differences

The reporter’s read-only data is laid out in the oracle’s interning order except for one shape, and the field-assignment code differs by 25 bytes because the oracle stages the pair through the string staging area and the self-hosted driver does not. Both are documented in docs/inventory/native-feature-matrix.json.

v1.1.0 - Stable Build (historical)

Status

Karkain 1.1.0 (Stable) — the project’s public status; 1.0.x is the LTS line (security fixes). Full story: docs/release/KARKAIN-1.1-RELEASE-NOTES.md

Since 1.0.0

Stdlib freeze + SemVer policy (132); first-class fn values (133); incremental v2 (134); local registry (135); LSP v2 (136); concurrency parity, 08-concurrency Stable (137); @target(gpu) WGSL kernels (138); new triples + WASM structs + karkain wit (139); karkain dbg + VS Code debug surface (140); SimplifyCFG optimizer pass + profile cell counts + measured RSS table (141); std.net/std.http/std.db (125A); std.numerics (126)

Compatibility

Every 1.0.0 program builds and runs identically (conformance 64/64, Phase 114 corpus byte-identical Go↔kcc); the one behavior fix is K114 escape rejection (previously accepted-and-miscompiled)

Example corpus

61 files across 15 categories (59 Runnable incl. test-mode, 2 Stable, 1 Planned dir), pinned goldens byte-identical both engines

v1.0.0 — Stable Build (historical)

Status

Karkain 1.1.0 (Stable) — the project’s public status (see Compatibility Policy for the guarantees attached to it)

Language core

Stable core defined and regression-gated on both engines: variables, functions, recursion, control flow, arrays, maps, structs, enums, match, strings, modules with public exports; while (cond) syntax aligned between the Go and kcc parsers

Diagnostics

Recoverable parse errors are no longer swallowed by build/run: let = 42 and friends exit 3 with a rendered error[K001]; undefined identifiers exit 3 on both engines during build/run (error[K002] Go / error[K102] kcc) — same contract as check

Error codes

Numeric codes (K001-K008, K100, K101–K115) documented by karkain explain and explain --list

Standard library

Public modules hardened: std.string, std.collections, std.io, std.encoding, std.crypto, std.testing with new edge-case parity tests (empty/invalid/duplicate inputs), plus std.numerics (40 funcs, Phase 126) and std.net / std.http / std.db (Phase 125A) with the Winsock link contract enforced on every generated-C linker

Example corpus

Phase 114/116 corpus (60 pinned goldens) verified under the new

semantic gating and byte-identical on both engines (Go + kcc)

Self-hosted compiler

kcc owns the default check/build/run/test path; KIR v1 structural

verification runs on the default check (Phase 121); flat project assembly is owned inside the compiler (Phase 122); stage-2 == stage-3 bitwise bootstrap identity

Bootstrap memory guard

error[K127] clean abort (stages 2/3) on low-RAM hosts replaces the

documented SEGFAULT class (Phase 127)

Compute targets

Phase 124 experimental catalog: cpu, simd, wasm32-wasi,

gpu-experimental, npu-experimental, quantum-experimental

Toolchain

Exit-code contract verified end-to-end; debug and prof opt-in

diagnostics verified in the Beta gate; fresh-checkout script scripts/beta-fresh-checkout.ps1

Developer readiness

Beta documentation (status/beta.rst), Beta readiness scorecard,

Phase 117 CI gate, version identity v1.0.0 (Stable Build)

Known gaps (honest)

Closures/fn codegen remains broken on both engines (documented);

GPU/NPU/quantum kernel language surface and a public package registry are Planned; concurrency, profiling, debug tracing, WASM and SIMD remain Go-engine only; Docker image is Planned

Entry requirements for every release note entry

  • The CLI version reported by karkain --version.

  • What is newly Implemented (gated) vs experimental vs planned.

  • Any behavior changes that might break existing programs.

Previous highlighted milestones

Phase

Version era

Summary

117

v0.117.0

Beta 1 readiness (historical): Go/kcc while and semantic-gate parity, parse-error hardening, numeric explain codes, stdlib edge tests, Beta docs + gate + fresh-checkout script

116

v0.115.0

Corpus normalization + real-world programming examples (50 files, dash-named categories, stack/queue/knapsack/token-stats) + metadata gate

115

v0.115.0

Developer Preview readiness: license/contributing/CoC, honest docs, version identity, fresh-checkout gate

114

pre-0.115

Example corpus (46 files, 15 categories) + parity gate

113

pre-0.115

Developer Preview documentation + status model established

111

pre-0.115

Cross-compilation via explicit target triples

107–110

pre-0.115

Concurrency runtime, WASM target, standard library v2, profiling

95–99

pre-0.115

Self-hosted compiler becomes the default engine; bootstrap identity

91

pre-0.115

(Historical note: this phase claimed a “1.0 release-ready” decision; that claim was retracted — the label moved Developer Preview → Beta 1 → 1.0.0 at Phase 119.)

See also

Roadmap — forward-looking plan. Beta 1 — what Beta 1 promises and the honest limitation list.