Is there a way to upload a version of a released AddOn to AMO and mark it as a beta or testversion? The usecase should be, that someone can install this testversion to test the actual behavior, without impact to standard version numbering or make the standard version auto-updating for end-users?
@caitlin, does that mean that the current answers [1] to the undermentioned are accurate?
I ask because like how I can utilize beta channels in the Google Play Store to use updates to trusted applications that I otherwise would need to utilize Obtanium or F-Droid to acquire due to how long those updates sit in Google’s validation pipeline, I get updates to from the Chrome Web Store weeks quicker than I do on AMO.
AMO (addons.mozilla.org) no longer accepts beta versions for listed publication. You can upload your add-on as unlisted which means it can be signed and installed for testing.
Unlisted add-ons will have to be distributed by the developers.
If you choose to distribute an extension yourself, you will also need to set the update_url in your extension’s manifest.json file and host a JSON update manifest on your web server.