Mozilla Add-ons

Mozilla Firefox doesn't share extensions with Google Chrome, so you'll need to publish your extension to it separately.

Here, we'll go through the process of publishing an extension to Mozilla Add-ons.

Developer account

Before you can publish items on Mozilla Add-ons, you must register a developer account. In comparison to the Chrome Web Store, Mozilla Add-ons doesn't require a registration fee.

To register, go to addons.mozilla.org and click on the Register button.

It's important to set at least a display name on your profile to increase transparency with users, add-on reviewers, and the greater community.

You can do it in the Edit My Profile section:

Submission

After registering your developer account, setting it up, and preparing your extension, you're ready to publish it to the store.

You can submit your extension in two ways:

• Manually: By uploading your extension's bundle directly to the store.
• Automatically: By using GitHub Actions to submit your extension to the stores.

The first submission must be done manually, while subsequent updates can be submitted automatically. We'll go through both approaches.

Manual submission

To manually submit your extension to stores, you will first need to get your extension bundle. If you ran the build step locally, you should already have the .zip file in your extension's build folder.

If you used GitHub Actions to build your extension, you can find the results in the workflow run. Download the artifacts and save them on your local machine.

Then, use the following steps to upload your item:

Automated submission

TurboStarter comes with a pre-configured GitHub Actions workflow to submit your extension to web stores automatically. It's located in the .github/workflows/publish-extension.yml file.

What you need to do is fill the keys.json file with your store's credentials using the keys.template.json file as a template:

{
  "firefox": {
    "extId": "aaaaaaa-aaaa-bbbb-cccc-dddddddddddd",
    "apiKey": "abcd",
    "apiSecret": "efgh"
  }
}

Please refer to the official guide to learn how to get these credentials correctly.

After that, set EXTENSION_SUBMIT_KEYS as a secret in your GitHub repository to the content of the keys.json file.

That's it! You can run the workflow and it will submit your extension to the Chrome Web Store.

Review

Once you submit your extension bundle, it's automatically sent to review and will undergo a review process. The time for this review depends on the nature of your item.

The add-on review process includes the following phases:

1. Automatic Review: Upon upload, the add-on undergoes several automatic validation steps to ensure its general safety.
2. Content Review: Shortly after submission, a human reviewer inspects the add-on to ensure that the listing adheres to content review guidelines, including metadata such as the add-on name and description.
3. Technical Code Review: The add-on's source code is examined to ensure compliance with review policies.
4. Basic Functionality Testing: After the source code is verified as safe, the add-on undergoes basic functionality testing to confirm it operates as described.

There are important emails like takedown or rejection notifications that are enabled by default. To receive an email notification when your item is published or staged, you can enable notifications in the Account Settings.

The review status of your item appears in the developer hub next to each item.

You'll receive an email notification when the status of your item changes.

You can learn more about the review process in the official guides listed below.