From fe2ff20e1cd9f5635e2d91c387d5122fab636159 Mon Sep 17 00:00:00 2001 From: Christophe Loiseau <116@lab0.net> Date: Wed, 21 Feb 2024 17:27:22 +0100 Subject: [PATCH] chore: release process improvements (#816) --- .github/ISSUE_TEMPLATE/release.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release.md b/.github/ISSUE_TEMPLATE/release.md index 4565df1c7..0849c09d6 100644 --- a/.github/ISSUE_TEMPLATE/release.md +++ b/.github/ISSUE_TEMPLATE/release.md @@ -52,11 +52,16 @@ Feel free to edit this release checklist in-progress depending on what tasks nee the [eclipse-edc-management-api.yaml file](https://github.com/sovity/edc-extensions/blob/main/docs/eclipse-edc-management-api.yaml). - [ ] Update the Postman Collection if required. - [ ] Merge the `release-prep` PR. -- [ ] Wait for the main branch to be green. -- [ ] Test the release `docker-compose.yaml` with `RELEASE_EDC_IMAGE=ghcr.io/sovity/edc-dev:latest`. - - [ ] Ensure with a `docker ps -a` that all containers are healthy, and not `healthy: starting` or `healthy: unhealthy`. +- [ ] Wait for the main branch to be green. You can check the status in GH [actions](https://github.com/sovity/edc-extensions/actions). +- [ ] Validate the image + - [ ] Pull the latest latest edc-dev image: `docker image pull ghcr.io/sovity/edc-dev:latest`. + - [ ] Check that your image was built recently `docker image ls | grep ghcr.io/sovity/edc-dev`. + - [ ] Test the release `docker-compose.yaml` with `EDC_IMAGE=ghcr.io/sovity/edc-dev:latest`. + - [ ] Ensure with a `docker ps -a` that all containers are healthy, and not `healthy: starting` or `healthy: unhealthy`. - [ ] Test the postman collection against that running docker-compose. -- [ ] Create a release and re-use the changelog section as release description, and the version as title. +- [ ] [Create a release](https://github.com/sovity/edc-extensions/releases/new) + - [ ] In `Choose the tag`, type your new release version in the format `vx.y.z` (for instance `v1.2.3`) then click `+Create new tag vx.y.z on release`. + - [ ] Re-use the changelog section as release description, and the version as title. - [ ] Check if the pipeline built the release versions in the Actions-Section (or you won't see it). - [ ] Revisit the changed list of tasks and compare it with [.github/ISSUE_TEMPLATE/release.md](https://github.com/sovity/edc-extensions/blob/main/.github/ISSUE_TEMPLATE/release.md).