Skip to main content

Chrome Extension Release Process

Releasing Chrome Extension needs to follow Chrome Web Store publish process. We use Chrome Web Store Publish API in our release process.

Releasing to production environment​

Deploy process consists of these steps:

  • Creating a new release via GitHub releases,
  • Creation of the artifact of extension package as ZIP file,
  • Uploading the artifact to Chrome Web Store,
  • Publishing previously uploaded artifacts to the test group.

The "publish" step doesn't actually publish anything. It submits the artifact for a review, after which it can be rejected or actually published.

Step-by-step instructions​

  1. Go to GitHub releases and create a new release. Browser extension release pipeline requires a tag with a prefix ext_browser_. So when making a new release one should also create a new tag, for example ext_browser_v0.5.0.

  2. The extension will be automatically published to the users after the approval from Chrome Web Store Team which may take from several minutes up to a couple of days. The duration of the review depends on various factors: publish target (public or test group), additional permissions, etc. It is preferred that all extension changes should be published to the staging channel first.

Note Production version of the Chrome extension can be found here.

Deploying to QA environment​

GitHub offers a pre-release option when preparing a release draft. It is a checkbox that marks a release as a non-production ready, but we use it as a workaround for releasing a Chrome extension to QA environment.

Note QA version of the Chrome extension can be found here.