<!-- The Runner Chart currently does not use [code-sync](https://jihulab.com/gitlab-cn/code-sync) to regularly merge the upstream `main` branch into `main-jh`, so the release process will be different. --> ## Prep stable branch changes - [x] Create 0-72-stable-jh ```shell # findout the merge base of branch "origin/0-72-stable" and "origin/main" BASE=$(git merge-base origin/0-72-stable origin/main | tr -d '\n') # merge the above "merge base" into out branch "main-jh" git checkout main-jh && git pull && git merge ${BASE} -m "Merge base-point of 0-72-stable and main into main-jh" # create branch "0-72-stable-jh" from branch "main-jh" git checkout -b 0-72-stable-jh ``` - [ ] Pick the below new required JH changes from `main-jh` into `0-72-stable-jh` if needed - `PICK COMMIT OR MR` - [x] Merge from `v0.72.0` to make sure all commits are passing CI - `git merge v0.72.0 -m "Version v0.72.0-jh"` - Resolve conflicts if any. - [x] Push the branch to the `canonical` remote to run test jobs - `git push origin 0-72-stable-jh:0-72-stable-jh` - `git push origin main-jh:main-jh` ## After release is finalized and tagged - [x] Tag `v0.72.0-jh` from `0-72-stable-jh` - `git tag -a v0.72.0-jh -m "Version v0.72.0-jh"` - [x] Push the tag to the `canonical` remote - `git push origin v0.72.0-jh` - [x] Trigger the `release stable` job manually and check if it succeeds.