We're following semantic versioning approach to releases in Kritis.
Modify the Kritis version values for the containers in these locations:
Assemble all the meaningful changes since the last release into the CHANGELOG.md file. See this PR for an example.
Verify that the integration test suite has passed for the release PR, then merge the PR.
Make sure your fork of the repository is updated. Assuming git remote shows the origin (the fork) and upstream (the main repository), do:
git pull origin master
git pull upstream master
git tag -am "kritis-vX.Y.Z release" vX.Y.Z
git push upstream --tags
NOTE: the last command will not work if you set git remote set-url --push upstream no_push as described in DEVELOPMENT.md. You will need to re-enable the push for this to work, so proceed with caution.
Once the tag is pushed upstream, the CloudBuild will run, creating the new versions of the kritis containers and a new helm chart.
You can find the releases in Github, e.g. v0.1.0.