Documentation · Releases
Product updates and application deployments use separate trust boundaries
Sysaro separates updating the product itself from deploying user applications, while both paths verify artifact provenance and integrity.
Verified against public version: 0.20.02026-09-15Factual boundary · roadmap is not presented as shipped
Product updates use signed manifests/artifacts and a separate Stable publication boundary. Application deployments use immutable release artifacts with SHA-256, safe extraction, health checks and rollback.
Product update
1
Candidate
Deterministic unsigned build candidate
2
Gate
Source/version/freshness/reproducibility checks
3
Signing
External Ed25519 signing step
4
Stable
Published repository manifest + verified artifact
Application deployment
1
Upload
Exact size + SHA-256
2
Agent fetch
Authenticated node/release UUID boundary
3
Extract
Traversal/symlink/hardlink/special-file rejection
4
Activate
Immutable release + healthcheck + rollback
Current production gate
A broad tagged Control Plane release requires a real composer.lock and bundled vendor. The project does not fabricate a lock file in an isolated environment.
Unsigned development candidates are stored separately and do not overwrite published Stable 0.20.0.