RELEASE

Release

The release process follows a streamlined approach, no release branches involved. New releases can be major, minor or patch based releases, but always incrementing digits regarding the latest release version.

New Major.Minor.Patch version

1. Create a new minor release branch from the HEAD of main:

   git checkout -b release-vX.Y.Z
   

2. Update version (prefixed with "v"):

   make prepare-release VERSION=vX.Y.Z
   

3. Verify local changes:

   make install
   bin/kuadrantctl version
   

   The output should be the new version, for example :

   kuadrantctl v0.3.0 (ff779a1-dirty)
   

4. Commit and push:

   git add .
   git commit -m "prepare-release: release-vX.Y.Z"
   git push origin release-vX.Y.Z
   

5. Create git tag:

   git tag -s -m vX.Y.Z vX.Y.Z
   git push origin vX.Y.Z
   

6. In Github, create release.

7. Pick recently pushed git tag

8. Automatically generate release notes from previous released tag

9. Set as the latest release

10. Verify that the build Release workflow is triggered and completes for the new tag

Verify new release is available

1. Download the latest binary for your platform from the kuadrantctl Latest Releases page.
2. Unpack the binary.
3. Move it to a directory in your $PATH so that it can be executed from anywhere.
4. Check the version:

   kuadrantctl version
   

   The output should be the new version, for example :

   kuadrantctl v0.3.0 (eec318b2e11e7ea5add5e550ff872bde64555d8f)