Release Process
Release Process
Document verified release preparation and publication procedures.
Status: Partial implementation reference — Code-confirmed; operational validation pending
Last reviewed: 2026-10-19
Scope
Versioning, checks, approvals where applicable, publication, validation and recovery. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.
Current implementation baseline
Worker workflows deploy eligible pushes to main after their configured checks. This describes declared automation, not approval or a release performed by this audit. The deployment page distinguishes application tests from the checks actually wired into CI.
For changes involving corpus identity/public archives, follow the coordinated rollout: apply compatible migrations under fencing, preserve external identity, validate Corpus, publish Resources contracts, capture exact published bytes and refresh/check the SDK separately. Never roll external lineage back with software.
The SDK maintainer guide describes generation and package checks; registry ownership and release readiness need separate confirmation. Backup readiness remains governed by its unresolved export/restore acceptance work. No commit, push, publication or deployment was performed here.
