Skip to content

Releases and changelog

Iteron publishes immutable pre-alpha artifacts. Availability does not imply a stable CLI, configuration, record, or runtime compatibility promise.

Published history

The GitHub Releases page is the canonical binary channel. Its release notes are authoritative for the exact assets attached to each tag.

Tag Published Build origin Native archives
v0.0.1 2026-08-06 local macOS build aarch64-apple-darwin
v0.0.2 2026-08-07 local macOS build aarch64-apple-darwin
v0.0.3 2026-08-10 local macOS build aarch64-apple-darwin
v0.0.4 2026-08-10 local macOS build aarch64-apple-darwin
v0.0.5 2026-08-14 release workflow release page is authoritative
v0.0.6 not published validation refusal none
v0.0.7 2026-08-15 release workflow release page is authoritative
v0.0.9 2026-08-16 release workflow three macOS/Linux archives
v0.0.19 2026-08-23 release workflow three macOS/Linux archives
v0.0.20 2026-08-24 release workflow macOS arm64, Linux arm64/x86-64, Windows x86-64
v0.0.21 2026-09-15 release workflow release page is authoritative

The first four were produced while hosted Actions capacity was unavailable. They carry content-addressed manifests, receipts, checksums, legal evidence, and SBOMs, but not GitHub OIDC attestations or the complete three-target matrix. They are useful historical pre-alpha artifacts and do not satisfy the accepted workflow release contract below.

v0.0.6 remains an immutable tag, but the release workflow rejected it before creating a release because the public schema chronology had not advanced. It has no downloadable assets and is not a release fallback.

The latest release, its manifest, and GitHub asset list are authoritative for current targets and attestations. This table records historical milestones and may lag new immutable releases.

Accepted release artifacts

The current distribution matrix is:

  • aarch64-apple-darwin;
  • aarch64-unknown-linux-musl and x86_64-unknown-linux-musl;
  • x86_64-pc-windows-msvc. The Windows archive is a distribution target, not a claim of full product support: Windows has no code-execution sandbox, and the interactive TUI remains unsupported there.

An accepted release contains the targets named by its release notes and, for the complete supported matrix:

  • three native macOS/Linux archives and one Windows x86-64 archive;
  • version-bound install.sh and install.ps1, plus SHA256SUMS;
  • release-manifest.json with commit, CLI stream, target, size, and digest evidence;
  • release-manifest.receipt.json identifying the exact final manifest bytes;
  • Apache-2.0 and third-party license and notice material;
  • per-target SPDX SBOMs;
  • GitHub build provenance, SBOM attestations, and offline bundles.

The executable payloads are iteron and the fixed iteron-workspace-hook; the archive also carries the public PlantCore contract bundle. The repository research binary iteron-harness, its fixture optimizer, and its protocol development assets are not release or installer payloads. Researchers build that binary explicitly from a reviewed source checkout; see the research harness protocol.

Windows first became a release target in v0.0.20. That archive does not imply a code-execution sandbox or a supported interactive TUI. Published releases are expected to use GitHub's immutable-release control; if a correction is required, the project publishes a new patch version rather than moving a tag or editing assets.

See the installation guide for current availability, version pinning, verification, and uninstall instructions.

Changelog

The source repository's CHANGELOG.md is the canonical human-readable change history. GitHub release notes identify the exact artifact set for a tag.

Do not infer release support from the workspace version alone. During 0.0.x, public interfaces may change between releases.

Acceptance gate

A release is accepted only when all of the following are true:

  • the annotated SemVer tag resolves to the current protected main commit;
  • source, ownership, formatting, clippy, and full workspace tests pass;
  • all declared targets are built, tested, packaged, and smoke-tested on their declared release runners;
  • archive structure, licenses, notices, checksums, SBOMs, and provenance pass;
  • the Owner approves the protected release environment;
  • the published release reports itself immutable;
  • content-addressed artifact canaries and fixed-version plus latest installer canaries pass on every declared target.

Maintainers follow the detailed release guide.