docs: mention 'needs-backport' label in release process (#1216)

* Mention 'needs-backport' label in release docs.
* Add missing version prefix.
Signed-off-by: Fabian Kammel <fk@edgeless.systems>
This commit is contained in:
Fabian Kammel 2023-02-20 10:44:16 +01:00 committed by GitHub
parent 87fdb47caa
commit b6b353c53e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -15,9 +15,10 @@ Releases should be performed using [the automated release pipeline](https://gith
### Patch release
1. `cherry-pick` (only) the required commits from `main`
* Check PRs with label [needs-backport](https://github.com/edgelesssys/constellation/pulls?q=is%3Apr+is%3Aclosed+label%3A%22needs+backport%22) to find candidates that should be included in a patch release.
2. trigger the automated release pipeline from the existing minor version branch:
```sh
ver=1.3.1 # replace me
ver=v1.3.1 # replace me
minor=$(echo $ver | cut -d '.' -f 1,2)
gh workflow run release.yml --ref release/v$minor -F version=$ver -F kind=patch
```
@ -29,7 +30,7 @@ Releases should be performed using [the automated release pipeline](https://gith
1. Merge ready PRs
2. trigger the automated release pipeline from `main`:
```sh
ver=1.3.0 # replace me
ver=v1.3.0 # replace me
minor=$(echo $ver | cut -d '.' -f 1,2)
gh workflow run release.yml --ref main -F version=$ver -F kind=minor
```