2017-06-05 22:46:18 +02:00
# Publishing Guide
When publishing a new version of MetaMask, we follow this procedure:
2018-05-23 23:48:05 +02:00
## Preparation
We try to ensure certain criteria are met before deploying:
- Deploy early in the week, to give time for emergency responses to unforeseen bugs.
- Deploy early in the day, for the same reason.
- Make sure at least one member of the support team is "on duty" to watch for new user issues coming through the support system.
- Roll out incrementally when possible, to a small number of users first, and gradually to more users.
2017-06-05 22:55:48 +02:00
## Incrementing Version & Changelog
2018-03-02 22:55:56 +01:00
Version can be automatically incremented [using our bump script ](./bumping-version.md ).
2017-06-05 22:55:48 +02:00
2018-03-02 22:55:56 +01:00
npm run version:bump $BUMP_TYPE` where `$BUMP_TYPE` is one of `major` , `minor` , or `patch` .
2017-06-05 22:55:48 +02:00
2018-05-23 23:48:05 +02:00
## Building
While we develop on the main `develop` branch, our production version is maintained on the `master` branch.
With each pull request, the @MetaMaskBot will comment with a build of that new pull request, so after bumping the version on `develop` , open a pull request against `master` , and once the pull request is reviewed and merged, you can download those builds for publication.
2017-06-05 22:55:48 +02:00
## Publishing
2018-05-23 23:48:05 +02:00
1. Publish to chrome store.
2018-05-23 23:58:09 +02:00
2. Visit [the chrome developer dashboard ](https://chrome.google.com/webstore/developer/dashboard?authuser=2 ).
3. Publish to [firefox addon marketplace ](http://addons.mozilla.org/en-us/firefox/addon/ether-metamask ).
4. Publish to [Opera store ](https://addons.opera.com/en/extensions/details/metamask/ ).
5. Post on [Github releases ](https://github.com/MetaMask/metamask-extension/releases ) page.
6. Run the `npm run announce` script, and post that announcement in our public places.
