FWDekker
commented
10 months ago I just tried out how to add beta versions myself. You have to add a custom repository with url https://plugins.jetbrains.com/plugins/beta/list in your plugin settings. After that, the latest beta version always takes precedence over the latest non-beta version. This is true for every plugin, there is no way to disable beta for just one plugin. Therefore, it does not make sense to ask users to disable the beta, since they would have to disable betas for all plugins.
Therefore, I have decided to hide the old beta versions on plugins.jetbrains.com. They still exist, but cannot be downloaded by users anymore. When v3.0.0 is released, even users on the beta will receive the update notification. If JetBrains ever rolls out improved channel management, I'll un-hide these beta versions for historical reasons.
On plugins.jetbrains.com, the beta channel is no longer needed once v3 is uploaded to the main channel, since I do not plan to run betas in the future. Therefore, the beta channel can be closed. However, closing channels is not a thing yet. Therefore, I suggest uploading the full v3 release, but with a modification that warns the user in the Randomness settings panel that the version they're using is no longer supported, and explaining to them how they can switch to the stable channel.