Versioning

This page summarizes the version markers that appear across the repository. It

does not replace the exact release, ABI, package, or compatibility references.

Project Release Version

The current project version is stored in VERSION. At the time of this

documentation pass, it is:

0.12.0

Release artifacts are written under:

build/release/v0.12.0

See Release Guide and Release Notes.

Trusted Root Version

The normal trusted compiler root is 0.1.0. make release uses the trusted root

from TRUSTED_VERSION, which defaults to 0.1.0.

Precondition for changing TRUSTED_VERSION: the maintainer must intentionally

move the trusted root and update release, compatibility, and bootstrap evidence.

See Bootstrap Model, Bootstrap Chain, and

Release Compatibility.

ABI Versions

The current native runtime boundary is documented as ABI version 0.1 in

ABI Guide. Promoted runtime value layouts use ABI v1 evidence rows in

ABI Value Layouts and abi/value-layouts.tsv.

Needs verification before an ABI change:

• whether existing compiled artifacts remain compatible;
• whether generated ELF/object/linker paths need new evidence;
• whether release compatibility docs and tests need a migration note.

Package Manifest Version

The root package manifest is 0x0.pkg. It currently declares:

package 0x0
version 0.1.0

This package version is distinct from the project release version. Package

dependencies are locked in 0x0.lock.

See Packages, Package System, and

Package Registry.

Scripting Profile Version

The production-ready scripting compatibility profile is

scripting-profile-v1. Changes to command spellings, JSON fields, capability

names, diagnostics, or host ABI exposure must follow the compatibility policy.

See Scripting And REPL and Release Compatibility.

Runtime Host ABI

runtime/host-abi.tsv is the versioned host ABI operation inventory for

filesystem, process, network, signing, and hardware emulator host effects.

See Runtime Production Capabilities.

Documentation Versioning Rule

When a version changes, update:

• release notes;
• release guide;
• compatibility policy if compatibility changes;
• public site metadata and release pages when relevant;
• package/ABI/runtime docs if their version markers changed;
• examples or migration notes when user-visible commands change.

If no user-visible behavior changed, document why in the ADR/RFC documentation

impact review.