Releasing

As part of the release process, GitHub's CLI tool is used. To have the entire process work smoothly you should have it set up on your machine.

Please follow the installation instructions to get it set up.

GitHub's CLI tool is used to automatically create a pull request as part of the release process.

If you do not have GitHub's CLI set up on your machine, you will need to create the PR manually

To release the library, run bundle exec fastlane tag_release and choose to bump either the major, minor or patch when prompted.

This will create a new tag, update the changelog and trigger the publish workflow on Bitrise.

Then you need to:

Have a valid Bitrise access token saved in your path under the variable name BITRISE_TOKEN. See Bitrise docs.
Two environment variables, ANDROID_COMPONENTS_APP_SLUG & ANDROID_COMPONENTS_RELEASE_WORKFLOW_ID will also need to be included in your bash/ZSH profile. Speak with Chris to obtain these values.
Check Bitrise to verify that the publish workflow was triggered
Check GitHub to see the PR and request reviews from the relevant people. Once approved, merge to bring the main branch up to date with the latest release.

Note: the PR does not need to merged for the release to happen

Increment the version number in components-test/build.gradle, then commit & push these changes.
Go to Bitrise and start a build using master branch and the publish_test_library workflow

Provide feedback