This document describes how to release the Tinkerell infrastructure provider.
This is not intended for regular users.
This is normally performed by our CI system. However, there are important steps to take first.
In order to cut a release, you must:
- If this is a new major or minor version - but not just a patch change - update metadata.yaml to add it, and map it to the correct cluster-api contract version
- Commit the changes.
- Push out your branch, open a PR and merge the changes
- Wait for the Continuous Integration github action to finish running
- Tag the release with `git tag -a vX.Y.z -m "Message"
- Push out the tag
- GitHub Actions detects a new tag has been pushed
- CI builds docker images for each supported architecture as well as a multi-arch manifest, and tags it with the semver tag of the release, e.g.
v0.1.0 - CI creates the release in
out/release, the equivalent ofmake release - CI copies the artifacts in
out/release/*to the github releases