chore: update release instructions

SwissDataScienceCenter · Feb 7, 2024 · 4a7cc2c · 4a7cc2c
1 parent bdc0588
commit 4a7cc2c
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/RELEASE.md b/RELEASE.md
@@ -12,8 +12,9 @@ This procedure should be followed for *any* release:
 
 * Create a release branch (e.g. `0.46.x`), if one does not already exist, with the [release action](https://github.com/SwissDataScienceCenter/renku/actions/workflows/create-release-branch.yml).
 * Create a `CHANGELOG` entry for the release and open a PR; create a deployment, this is the reference for the release.
-* Note that any PR that should go into the release needs to target the release branch _not_ `master`. 
+* Note that any PR that should go into the release needs to target the release branch _not_ `master`.
 * All release branches should be protected.
+* Use the "Rebase and Merge" button to merge release branches into `master`; do not squash commits.
 
 Acceptance tests have to pass on all release branches before merging.