Channels

Each version belongs to one channel. Channels split insider / beta / stable tracks and can pin a store listing.

When to use

Use channels for multi-track releases, unlisted tracks, or channel tokens. A single-track product can keep only system stable.

Configuration entry

Project → Channels. Steps: Channels. No YAML table.

Rules and error codes

Concept	Behavior
System alpha / beta / stable	Seeded at project create; cannot delete (SYSTEM_CHANNELSystem channels alpha/beta/stable cannot be deleted)
Custom slug	Immutable after create
stability_rank	Higher is more stable. Promote from a lower channel
unlisted	Omitted from public catalogs; not auto-selected unless the client is already on that slug or queries it
Channel token / X-Channel-Token	Wrong token on check skips that hidden channel, not 403. Changelog mismatch is 404

SemVer prerelease suffix must match the channel or CHANNEL_SUFFIX_MISMATCHPrerelease suffix vs channel; stable cannot use a prerelease suffix. stable cannot use a prerelease suffix. Missing channel: CHANNEL_NOT_FOUNDChannel missing.

Client duties

Public GET /channels omits unlisted and token-protected rows. Hidden-channel upgrades use check channel= + X-Channel-Token.

Related: Releases, Install policy, Store listings.