Releasing

How to make a new release

This is a checklist for releasing a new version of the extension.

• Be on the next branch
• Make sure to update all the versions in the corresponging files (package.json, firefox/manifest.json, google-chrome/manifest.json)
• git commit -m "release version X.Y.Z"
• git tag X.Y.Z
• git push --tags origin next
• Make PR in github (https://github.com/esphen/RESTED/compare/master...next)
• Write changelog in PR
• Close corresponding milestone in github
• yarn run build; pass gpg_keys/RESTED\ private\ key | ./scripts/build.sh
• mv RESTED.* ~
• scripts/build-source-archive.sh
• Test the xpi in firefox for sanity
• Go to https://addons.mozilla.org and upload both the xpi and the sources
• Verify the AMO validation report does not have any new stuff in it
• Upload to google: https://chrome.google.com/webstore/developer/dashboard?hl=no
• Upload to Opera: https://addons.opera.com/developer/
• Merge the PR
• Make release based on tag
• Upload files to release