Release x.x.x

[ununhexium]

Release

Work Breakdown

Feel free to edit this release checklist in-progress depending on what tasks need to be done:

• [x] Release edc-ui, this might require several steps, first of which is to create a new Release issue
• [ ] Decide a release version depending on major/minor/patch changes in the CHANGELOG.md.
• [ ] Update this issue's title to the new version
• [x] release-prep PR:
  • [x] Write or review the current Productive Deployment Guide
  • [x] Write or review the current Development Deployment Guide
  • [x] Write or review the current Local Demo Deployment Guide
  • [ ] For Major version updates: If we want to continue supporting the old major version:
  • [ ] Keep the old Productive Development Guide in a separate location.
    • [ ] Add a note to the old version about its deprecation status.
    • [ ] Add a Link the old version in the new version for discoverability.
    • [ ] Check all links in the old version.
  • [ ] Keep the old Productive Development Guide in a separate location.
    • [ ] Add a note to the old version about its deprecation status.
    • [ ] Add a Link the old version in the new version for discoverability.
    • [ ] Check all links in the old version.
  • [x] Update the CHANGELOG.md.
  • [x] Add a clean Unreleased version.
  • [x] Add the version to the old section.
  • [x] Add the current date to the old version.
  • [x] Add all relevant changelog entries from the newer EDC UI release(s), merge and reword them.
  • [x] Add all deployment migration notes from the newer EDC UI release(s), merge and reword them.
  • [x] Check the commit history for commits that might be product-relevant and thus should be added to the changelog. Maybe they were forgotten.
  • [x] Write or review the Deployment Migration Notes section, check the commit history for changed / added configuration properties.
  • [x] Reorder, reword or combine changelog entries from a product perspective for consistency.
  • [x] Write or review a release summary.
  • [x] Write or review the compatible versions section.
  • [x] Remove empty sections from the patch notes.
  • [x] Replace the existing docker-compose.yaml with docker-compose-dev.yaml.
  • [x] Set the version for EDC_IMAGE of the docker-compose's .env file.
  • [x] Set the version for TEST_BACKEND_IMAGE of the docker-compose's .env file.
  • [x] Set the UI release version for EDC_UI_IMAGE of the docker-compose's .env file.
  • [ ] If the Eclipse EDC version changed, update the eclipse-edc-management-api.yaml file.
  • [x] Run all tests locally as long as the GH flaky tests are a problem.
  • [x] Merge the release-prep PR.
• [ ] Wait for the main branch to be green. You can check the status in GH actions.
• [ ] Validate the image
  • [x] Pull the latest edc-dev image: docker image pull ghcr.io/sovity/edc-dev:latest.
  • [x] Check that your image was built recently docker image ls | grep ghcr.io/sovity/edc-dev.
  • [x] Test the release docker-compose.yaml with EDC_IMAGE=ghcr.io/sovity/edc-dev:latest (at minimum execute a transfer between the two connectors).
  • EDC
    • [x] Test with EDC_UI_ACTIVE_PROFILE=sovity-open-source
    • [x] Test with EDC_UI_ACTIVE_PROFILE=mds-open-source
  • [x] Ensure with a docker ps -a that all containers are healthy, and not healthy: starting or healthy: unhealthy.
• [x] Create a release
  • [x] 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.
  • [x] Re-use the changelog section as release description, and the version as title.
• [x] 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. Propose changes where it makes sense.
• [x] Close this issue.
• [x] Inform the Product Manager of this new release

[ununhexium]

https://github.com/sovity/edc-ce/releases/tag/v10.4.0