Status: stable model; listing begins with the first public baseline — release records published here never depend on private links or internal deployment records.

Releases

Versioning model

Xtrape uses milestone-aligned component versioning with explicit deployment stack records. Versions are SemVer X.Y.Z:

• X — incompatible product/protocol/deployment generation;
• Y — milestone or capability phase (0.6, 0.7, 0.8);
• Z — component patch inside that milestone. Preview suffixes: -alpha.N / -beta.N / -rc.N.

The key idea: component patch numbers do not need to match. Each repository releases its own patches independently; a stack record publishes the recommended deployable combination under a stack version, listing the exact component version matrix. (A real example from the 0.7 milestone: a "0.7.4" stack containing a contracts package at 0.7.5, because a rename release bumped that package independently.) A stack version names a combination, not a shared number.

Release order runs contracts → runtime packages → service/adapter images → stack pins → changelog, with final integration validation against published artifacts.

Supported versions

Only the current public minor and its listed patch releases receive fixes. Deprecations name the replacement, the first deprecated version, and the earliest removal window, and normally persist one documented release window before removal. Wire values, persisted state, token prefixes, and artifact identities always require a migration plan. Pre-1.0 users should pin exact versions and digests.

Public releases

Release	Status	Artifacts
Xtrape Public Concept Baseline 0.8.0-draft.1	in preparation	static site build, source archive, SHA256SUMS, provenance.json, Sigstore bundle, Zenodo DOI (pending), Software Heritage SWHID (pending)

Each published release page will show: canonical repository, commit SHA and tag, mirror URLs with ref-consistency status, artifact digests, the Sigstore bundle, the Zenodo version DOI, and the Software Heritage SWHID (or an honest archive_status: pending). See Provenance for how to verify all of it.

Historical note: the 0.7.x train (0.7.1 → 0.7.6) completed component-side in private infrastructure; its stack records become public as the corresponding repositories are opened in later phases.