This workflow should be zero-touch and lead to regular, stable, releases. Releases should satisfy the following conditions:
CHANGELOG.mdentry with changes listed
radarserver side binary
Releases will be handled via CI and be released using the GitHub release mechanism. Initiating a release (after the pre-requisites have been met) should involve a single manual step, pushing a tag to the repository.
masterbranch is pulled
When a new version is released updates can be handled one of two ways. A new set of binaries and container image can be downloaded from the release page, in the same manner as a first installation. Alternatively, the inline updater
ksync update will check the GitHub release page for newer releases and, if found, download the local binary.
In either case, the user must run
ksync init --upgrade to update the server side container and binary if version parity is needed.