extension-workshop/documentation/publish/distribute-pre-release-versions.md

layout	title	permalink	published	topic	tags	contributors	last_updated_by	date
sidebar	Distribute pre-release versions	/documentation/publish/distribute-pre-release-versions/	true	Publish	beta alpha testing pre-release publish guide how-to	caitmuenster	caitmuenster	2020-05-06

{% capture page_hero_banner_content %}

Distribute pre-release versions

Learn how to distribute an alpha or beta pre-release version of your extension for Firefox.

{% endcapture %} {% include modules/page-hero.html content=page_hero_banner_content %}

{% capture content %}

Pre-release channels are not supported on addons.mozilla.org (AMO), so if you would like to have a limited group of users test a beta version of your extension, you will need to take the following steps to set up your own channel using an self-hosted version of your extension:

1. In the manifest.json of the beta version, specify the location of your update manifest. This will ensure that your beta users will receive future updates. If your release channel is also self-hosted, you will need to use a different update URL for the beta channel.

2. Submit your extension for signing on addons.mozilla.org using the self-distribution workflow. If you prefer to use the command line, you can use web-ext to sign the extension.

{% capture note %}

If your extension’s release version is listed on addons.mozilla.org, you will need to define which channel you are signing with web-ext.

{% endcapture %} {% include modules/note.html content=note alert=false %}

3. After the extension has been signed, host the .xpi file on a web property that you own, such as a Github repository or Wordpress site.

4. Direct your beta users to install the extension from the web property.

You will need to follow the same process to add new versions to your beta channel. As long as you have set the location of the update manifest, beta users will automatically receive updates of the beta version as you make them available. Note that only beta users will get these updated versions. You will need to separately update your release channel to push updates to your release users.

If you decide to discontinue your beta channel and your add-on is listed on AMO, you can release a final beta version without an update URL in the manifest. This will tell Firefox to check AMO for updates, and within a few days users will be migrated to the main update branch. If your release channel is also self-hosted, you must change the update URL of your final beta version to match the main release version.

{% endcapture %} {% include modules/one-column.html id="listing-on-amo" content=content aside="" %}

{%- include page-meta-data.html -%}

{%- include up-next.html -%}