🌱 Adding informations about releasing and fixing CI

.github/workflows/release.yml

@@ -21,6 +21,9 @@ jobs:
         uses: actions/setup-go@v2
         with:
           go-version: '^1.16'
+      - name: install kustomize
+        run: |
+          make kustomize
       - name: generate release artifacts
         run: |
           make release

Makefile

@@ -245,7 +245,7 @@ verify-gen: generate
 
 
 ##@ Release
-PREVIOUS_TAG ?= $(shell git tag -l | grep -E "^v[0-9]+\.[0-9]+\.[0-9]+$$" | sort -V | grep -B1 $(RELEASE_TAG) | head -n 1 2>/dev/null)
+PREVIOUS_TAG ?= $(shell git tag -l | grep -E "^v[0-9]+\.[0-9]+\.[0-9]." | sort -V | grep -B1 $(RELEASE_TAG) | head -n 1 2>/dev/null)
 
 RELEASE_TAG := $(shell git describe --abbrev=0 2>/dev/null)
 RELEASE_DIR ?= out

docs/developers/releasing.md

@@ -0,0 +1,33 @@
+# Release Process
+
+## Create a tag
+
+1. Create an annotated tag
+   - `export RELEASE_TAG=<the tag of the release to be cut>` (eg. `export RELEASE_TAG=v1.0.1`)
+   - `git tag -a ${RELEASE_TAG} -m ${RELEASE_TAG}`
+2. Push the tag to the GitHub repository. This will automatically trigger a [Github Action](https://github.com/kubernetes-sigs/cluster-api/actions) to create a draft release.
+   > NOTE: `origin` should be the name of the remote pointing to `github.com/syself/cluster-api-provider-hetzner`
+   - `git push origin ${RELEASE_TAG}`
+
+## Promote images to quay
+
+1. Login to quay
+2. Do:
+   - `make release-image`
+
+
+## Release in GitHub
+
+1. Review the draft release on GitHub. Pay close attention to the `## :question: Sort these by hand` section, as it contains items that need to be manually sorted.
+1. Publish the release
+
+### Versioning
+
+See the [versioning documentation](./../../CONTRIBUTING.md#versioning) for more information.
+
+### Permissions
+
+Releasing requires a particular set of permissions.
+
+* Tag push access to the GitHub repository
+* GitHub Release creation access