Beta and Stable

EvoX Desktop uses Pre, Beta, and Stable update channels. Channels control which signed builds an installation receives; they are not separate codebases.

Version shapes

EvoX derives the channel from its own version. An unrecognized version is not guessed into a channel and is not offered another channel's release.

Same-channel updates

Each channel reads a separate update manifest. Pre accepts Pre, Beta accepts Beta, and Stable accepts Stable. Moving between channels normally requires installing the official build for the destination channel, not toggling a general preference.

Managed environments may pin updateChannel or updateFeedURL through organization policy. Valid channel values are pre, beta, and stable; a rejected policy does not make the binary pretend to be a different release.

Download verification

The manifest lists desktop and CLI components separately, with platform-specific assets. A downloadable asset binds at least:

• Version and platform;
• URL and format;
• File size;
• SHA-256;
• Ed25519 signature.

The client hashes the downloaded bytes and verifies the signature with its release public key. Missing signatures, mismatched digests, wrong platforms, and invalid version markers fail closed.

How Beta relates to Stable

A Beta is promoted from a previously published Pre instead of being rebuilt from the current trunk. Stable similarly reuses an accepted Beta commit. Any code change requires a new Pre and then a new Beta; a Stable release cannot quietly add untested changes.

Troubleshoot updates

• Record the full installed version and resolved channel.
• Confirm that the manifest contains an asset for the current platform.
• Check whether a proxy, mirror, or security product replaced the download.
• Never disable signature verification to work around a fetch problem.
• After changing channels, verify that the installed binary and managed policy agree.

EvoX Docs · Configuration · Paths and platforms