Once the intended commit has been tested and we have confidence to cut a release, we can follow these steps to release Brigade:
Issue a docs pull request with all
<current release>strings updated to
<anticipated release>, e.g.
(Note: amending docs/index.yaml is not required. This file still exists (as of writing) only to serve older chart versions for a period of time after the chart migration to Azure/brigade-charts completed.)
Once this pull request is merged, create and push the git tag from the intended commit:
$ git tag v0.20.0 $ git push origin v0.20.0
The release pipeline located in our brigade.js then takes over and does the heavy lifting of building component images, pushing to designated image registries, building the
brigcli binaries and finally creating the GitHub release.
Lastly, issue a pull request in Azure/brigade-charts bumping the
appVersionvalues in both the Brigade chart and the Brigade Project chart to match the current release value. Once this pull request is merged, the brigade.js pipeline will handle building fresh chart artifacts and updating the chart index file.