Release management
EvoX Desktop, the embedded sidecar, the Evolver npm package, and the documentation website have different repositories, versions, and release credentials. A successful release of one component does not validate the others.
In this section
- Build and sign: produce and sign artifacts in the owning pipeline.
- Verify and promote: re-download candidate artifacts and verify actual bytes before updating manifests.
- Platform coverage: verify the real delivery state for macOS, Windows, and Linux independently.
Release objects
| Object | Primary release form |
|---|---|
| EvoX Desktop | Platform installers, update manifests, and channel history |
evox-cli sidecar | Target-triple binaries and signed manifests |
| Evolver | npm package, CLI/Proxy/MCP entry points, and package metadata |
| Documentation website | Next.js build output and static assets |
Update release manifests last. Promote a channel only after retrieving candidate artifacts from their final download location and verifying size, digest, signature, and startup behavior.
EvoX Docs · Administration · Release management