From 29d690eb7db63fa944d177f34f2ea446032dd516 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20G=C3=BCttler?= Date: Sat, 17 Aug 2024 15:26:41 +0200 Subject: [PATCH] :seedling: Extend releasing docs: Check for assets (#1442) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * :seedling: Extend releasing docs: Check for assets * :seedling: remove old kubernetes versions (#1443) * 🌱Add tests for PR 1413 (#1445) * :seedling: Better usage message for detect-linux-on-another-disk.sh (#1446) Fixes #1216 * ..revert unrelated change --------- Co-authored-by: Sven Batista Steinbach Co-authored-by: Yash Raj Singh <98258627+yrs147@users.noreply.github.com> --- docs/caph/04-developers/03-releasing.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/caph/04-developers/03-releasing.md b/docs/caph/04-developers/03-releasing.md index eecc0ac6b..121858a68 100644 --- a/docs/caph/04-developers/03-releasing.md +++ b/docs/caph/04-developers/03-releasing.md @@ -22,6 +22,7 @@ title: Release Process ## Release in GitHub 1. Review the draft release on GitHub: [Releases](https://github.com/syself/cluster-api-provider-hetzner/releases). Use the pencil-icon to edit the draft release. Then use the button "Generate release notes". Pay close attention to the `## :question: Sort these by hand` section, as it contains items that need to be manually sorted. Feel free to move less important PRs, like version upgrades (from renovate bot), to the bottom. +1. Double checkt that the assets got created. There should be one zip file, one tgz file, and 12 yaml files. 1. If it is pre-release, activate the corresponding check at the bottom of the page. And add `:rotating_light: This is a RELEASE CANDIDATE. If you find any bugs, file an [issue](https://github.com/syself/cluster-api-provider-hetzner/issues/new).` at the top of the release notes. 1. Before publishing you can check the [Recent tagged image versions](https://github.com/syself/cluster-api-provider-hetzner/pkgs/container/caph): "latest" should be some seconds old and the new version number. 1. Publish the release