Home Features Documentation Back

Swing Updater

Documentation

Getting Started

Installation

Setup your shortcut

Integration

Integration Methods

RoutineHub

ShareShortcuts

Custom Server

Swing for Updates (SFU)

Other editions

Swing Updater 🅂

Swing Updater 🄴

Advanced

Result Codes

Pre-release Updates

Pre-release Versions

Personalization

Get Swing Updater Version

Custom Server Setup

Advanced

Pre-release Version Structure

When releasing pre-release versions, it's good practice to use a dedicated version structure to not mess up the pre-release channels with the Stable channel.

Swing Updater supports pre-release versions in the following format 0.0-LABEL-0.0 (or just 0.0-LABEL).

Everything before the first hyphen is considered the next shortcut version to be released. The label can be any string but it's recommended to use one of the three labels Swing Updater supports (Alpha, Beta or Final). The version proceeding the label is useful if you want to release multiple pre-release versions with the same label.

To sum up, if you want to release a beta version for the next minor 3.4 update, you should use something like 3.4-Beta-1 or 3.4-Beta.


Below you can find some expected results from the Swing Updater engine when asked about two pre-release versions:

InstalledRecentResult
1.0-alpha1.0-betaUpdate
1.2-final1.2-betaRollback
1.2-beta1.2-beta-1Update
5.4-final-3.25.4-final-3.3Update
3.1.4-alpha-1.0.13.1.4-alphaRollback
6.5.4-crystal6.5.4-diamondUpdate
8.9.0-final-88.8.9Rollback
3.4-alpha3.4Update