Release process

Minor version releases

Add release notes to docs/modules/ROOT/pages/CHANGELOG.adoc, submit PR and merge into main.
Switch to main and update branch
- git checkout main
- git pull upstream main
Create a release branch
- git checkout -b release/x.x
- git push upstream release/x.x
Commit and create a tag. Make sure the tag has a "v" prefix.
```
git tag -a v<VERSION> -m "Release version <VERSION>"
```
Push to upstream
```
git push upstream refs/tags/vx.x.x
```
Wait for CI build to complete
Prepare PR to start next dev iteration
- docs/antora.yml: change version (no v prefix)
- VERSION.txt: change version (no v prefix)
- Commit Start next dev iteration, submit PR and merge after approval

Pre-conditions: all commits are cherry-picked from main branch, committed, and CI is green.
From branch release/x.x: submit a PR
- In a separate commit, update docs/antora.yml and VERSION.txt (both with no v prefix)
- In one commit, update CHANGELOG.adoc
- Submit PR to release/x.x branch and rebase merge
Commit and create a tag. Make sure the tag has a "v" prefix.
```
git tag -a v<VERSION> -m "Release version <VERSION>"
```
Push to upstream
```
git push upstream refs/tags/vx.x.x
```
Wait for CI build to complete

Cherry-pick release notes

Create branch and cherry pick

git checkout -b cherry-pick-release-notes main
git cherry-pick $(git rev-parse release/x.x)