-
Define the next semantic version
Semantic versioning: a.b.c
- a: major breaking changes
- b: new functionality, new features
- c: any other small changes
-
Checkout the main branch and make sure it is up-to-date:
git checkout main && git pull -
Create a new branch
-
Update the CHANGELOG.md file with changes of this release, you should add a new section with your version number and the relevant updates, like the ones that exist on the previous versions
-
Change the version in
gradle.properties -
Change the version in
maestro-cli/gradle.properties -
git commit -am "Prepare for release X.Y.Z."(where X.Y.Z is the new version) -
Submit a PR with the changes against the main branch
-
Merge the PR
git tag -a vX.Y.Z -m "Version X.Y.Z"(where X.Y.Z is the new version)git push --tags- Wait until all Publish actions have completed https://github.com/mobile-dev-inc/maestro/actions
- Trigger the Publish Release action
- ATTENTION: Wait for it to finish
- Go to OSS Sonatype and login with user/password
- Go to Staging Repositories, select the repository uploaded from the trigger above.
- Click "Close" and then "Release". Each of these operations take a couple minutes to complete
CAUTION: You should go back to the notion document to see how to update the Robin and Maestro Cloud versions before updating the CLI
- Trigger the Publish CLI Github action
- Test installing the cli by running
curl -Ls "https://get.maestro.mobile.dev" | bash - Check the version number
maestro --version