From a2cafa4f4d357c14cbbb8f1e90f36f0b2be2b6de Mon Sep 17 00:00:00 2001 From: Jean-Philippe Evrard Date: Fri, 3 Jul 2026 18:47:56 +0200 Subject: [PATCH] Fix release process We need to keep the previous process to merge broken manifests, so that people git cloning at each TAG event will receive the right manifest. Without this, the update of the kured-ds and kured-ds-signal happen by dependabot AFTER the release, so it means the tag is NOT INCLUDING the right manifest. Signed-off-by: Jean-Philippe Evrard --- CONTRIBUTING.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b83ea26..7e1efcf 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -300,6 +300,14 @@ See also our GitHub issues with the label [`testing`](https://github.com/kubereb Ensure you have used the latest patch version in the tree. Check the documentation "Updating k8s support" if the minor version was not yet applied. +### Update the manifests with the new version + +```sh +export VERSION=1.24.0 +make DH_ORG="kubereboot" VERSION="${VERSION}" manifest +``` +Create a commit updating the manifest with future image [like this one](https://github.com/kubereboot/kured/commit/58091f6145771f426b4b9e012a43a9c847af2560). + ### Create the new version tag on the repo (optional, can also be done directly in GH web interface) Tag the previously created commit with the future release version.