# Publishing your extension

Due to chrome's extension submission requirements, there isn't a one-liner command provided by chromex to immediately publish your extension for the world to see; some massaging still has to be done. The good news is, it's pretty straightforward! Simply follow Google official extension publishing tutorial [here](https://developer.chrome.com/webstore/publish#upload-your-app).

Some key points to note are:
  1. There is a one-time $5 one signup fee made payable to Google if you want to be able to publish Chrome extensions. This will give you the ability to publish up to 20 extensions
  2. You are required to submit your extension packaged as a zip file. 
  3. Your extension will be published with the version number specified in your `extension.config.js`'s `manifest.version` field. By default, we will use the version number in your project's `package.json`. This allows for easier version management.

`create-chrome-extension` provides you with a convenience command to do just that:

        npm run release 

 This will 1) bump the version number in `package.json` according to [standard-version](https://github.com/conventional-changelog/standard-version), and 2) create a production-ready ZIP of your extension (named `ext.zip`) in your project root folder. Simply select to file when prompted to upload your app by following the official tutorial link above.


# Managing new releases over time

Let's say you have published an initial version of your extension