Clavem

Release channel

A release channel is a named track of app updates, such as stable, beta or nightly, that lets each user choose how early they receive new versions.

How it works

A channel is a label on a release plus a rule about who sees it. Typical tracks:

  • Stable. Everyone gets it by default.
  • Beta. Opt-in users get releases earlier, with rough edges.
  • Nightly. Automatic builds, for testers and contributors.

The app asks for its own channel, and the server answers with the newest release on that channel. A user can move between tracks in the app’s settings.

Sparkle, the macOS update framework, has the feature built in. As of November 2026, its documentation says updates go on the default channel unless an <item> carries a <sparkle:channel> element, for example beta. Only updaters that allow that channel find the update, and an updater cannot exclude itself from the default channel.

Example: the trap in Clavem’s “latest”

Clavem’s releases endpoint has no channel parameter. It returns the most recently published release of a product, which is not the highest version number and not the most recently created. A timeline:

Day Action latest returns
Mon Publish 3.2.1 3.2.1
Tue Publish 4.0.0-beta.2 4.0.0-beta.2
Tue Every app that asks sees a newer version than 3.2.1
Wed Unpublish 4.0.0-beta.2 3.2.1 again

On Tuesday every customer’s update check reports the beta, because the product has one stream. Version strings are free text of 1 to 64 characters from letters, digits, dots, dashes, plus signs and underscores, so 4.0.0-beta.2 is accepted but nothing in it marks the build as a beta to the endpoint. Your app can read the string, but it cannot ask the server to skip it.

Release channel versus platform label

Clavem files can carry a platform label such as macos or windows, and the endpoint’s platform query returns only matching files plus unlabelled ones. That filters files within one release. It does not filter releases, so it cannot split stable from beta.

How Clavem handles it

Clavem has no release channels. Two honest options:

  1. Keep betas off the endpoint. Distribute betas from your website or a beta tool of your choice, and publish to Clavem only what everyone should get.
  2. Use a separate product for the beta track. Each Clavem product has its own releases, its own device limit and its own Ed25519 key pair, and a license belongs to one product. Beta testers would need a license for the beta product, which you can create with the management API (it counts against your plan’s active licenses). This is a workaround, not a feature, and it doubles the bookkeeping.

If your app compares versions itself, make it ignore pre-release tags unless the user opted in; see semantic versioning for how pre-release identifiers sort. How releases are uploaded, published and unpublished is in Releases and downloads.

Questions

Does Clavem support beta channels?

Not as a feature. A product has one stream of releases, and the newest published release is the latest one the endpoint returns. A separate product for a beta track is one workaround.

How do I pull a bad release?

Unpublish it in Clavem. The previously published release becomes the latest again.

Sources

  1. Sparkle, Publishing an update, channels (checked November 2026)