Moving a snap between channels helps to manage a user’s expectations in any trade-off between stability in the stable channel, and cutting edge features in the edge channel (as an arbitrary example). But its also a useful technique for beta testing, or for when a snap needs to revert to a previous revision.
See Releasing your app for details on how to upload and publish a snap if you haven’t done so already.
The web UI’s release management functionality is equivalent to using
snapcraft release on the command line, and both require that you first login to the store.
After logging in to the Snap Store and selecting a published snap, click the ‘Releases’ tab to access the release management functions.
The Releases page lists which revisions of a published snap will be delivered to users tracking a specific channel.
On the command line, with a developer account already created, enter the following to login:
$ snapcraft login
The command line equivalent to the web UI’s Releases page is the output from
snapcraft status <snap-name>:
$ snapcraft status opencorsairlink Track Arch Channel Version Revision latest amd64 stable 61d336a 127 candidate 61d336a 127 beta 61d336a 127 edge 61d336a 127 arm64 stable 46dbf20 95 candidate 46dbf20 95 beta 46dbf20 95 edge 61d336a 128 armhf stable 46dbf20 94 candidate 46dbf20 94 beta 46dbf20 94 edge 61d336a 129 [...]
To move a snap between channels in the web UI, simply drag a revision from one channel to another, or use the cog drop-down menu on a revision and select a destination.
Click Save to make the requested change, or Revert to undo the proposed changes.
On the command line, the release command takes the snap name, the revision you wish to move and the destination channel (or channels) as its arguments:
$ snapcraft release mysnap 13 candidate
You can also move earlier revisions back into a channel:
$ snapcraft release mysnap 5 beta
A snap’s distribution can be limited from the Snap Store web UI by two options listed on a snap’s Settings page:
- Visibility: controls who can see a snap and install a snap. See Public, Private and Unlisted snaps for more details.
- Distribution: controls the territories where a snap can be installed or not installed, as outlined below.
The Distribution options set whether a snap can be installed in all territories (default), or whether its distribution is either
- limited to selected territories
- excluded from selected territories
Activating either of the Selected territories fields will open a drop-down list of territories from which to choose from. More than one territory can be added.
Last updated 1 year, 5 months ago.