We automated some parts of the release process to make things easier. This file lists the necessary steps to release the latest version of the application:
- Check and ensure the previous release branch
release/vX.Y.Z
was merged intomain
- Check and ensure
main
was back-merged intodevelop
- Check and ensure you are working in the latest
develop
branch - Run
yarn run version
- this will:- update the
version
in eachpackage.json
andmanifest.json
- create branch
release/vX.Y.Z
- create tag
vX.Y.Z
- push the branch and tag automatically
- update the
- Pushing a tag triggers a release build action in GitHub
- Wait for pipeline to create release containing the extension zip
- If the automatic npm publish failed, do it manually (ask Gerald)
- Create GitHub pull request to merge the new branch
release/vX.Y.Z
intomain
- Create GitHub pull request to back-merge
main
intodevelop
- Edit release to contain a bit more than just the auto generated notes and maybe a proper title
- Submit to Chrome Web Store (ask Ismael)