How is the workflow when there are several beta versions before a release? For instance, there’s currently version 1.0, 1.1 and 1.2 of an app in the F-Droid repo. Then there’s 1.3-beta1, 1.3-beta2, 1.3-beta3, 1.3-beta4… should the update bot handle those new betas? Wouldn’t the betas then replace the main version?
Or shall I manually create one beta and update it with MR, and let the bot only do the main releases?