Release 4.1.1

[kamilczaja]

Release

Work Breakdown

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

• [x] Check whether the flyway migrations in Authority Portal and sovity EDC-CE Catalog Crawler are identical. If not, you cannot proceed with the release or you need to make clear which EDC CE version is compatible and vice versa
• [x] Release sovity EDC CE, this might require several steps, first of which is to create a new Release issue
• [x] Decide a release version depending on major/minor/patch changes in the CHANGELOG.md.
• [x] Update this issue's title to the new version
• [ ] release-prep PR:
  • [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] Bump the EDC CE Version to a release version in the libs.versions.toml.
    • [x] Bump the links to the Catalog Crawler initial deployment guide to the fixed EDC CE Version
    • [x] Add all Catalog Crawler or Catalog relevant changelog entries from the newer EDC CE release(s), merge and reword them.
    • [x] Add all Catalog Crawler or Catalog deployment migration notes from the newer EDC CE release(s), merge and reword them.
    • [x] Write or review the Deployment Migration Notes section.
    • [x] Ensure the Deployment Migration Notes contains the compatible docker images.
    • [x] Write or review a release summary.
    • [x] Remove empty sections from the patch notes.
  • [x] Wait for the pipeline to be green.
  • [x] Merge the release-prep PR.
• [x] Wait for the main branch to be green.
• [x] Create a release and re-use the changelog section as release description, and the version as title.
• [ ] Create a release in the Authority Portal EE repository.
  • [ ] release-prep PR:
    • [ ] Copy the Keycloak themes for all flavors from here to the EE repository.
    • [ ] Copy the OAuth2 proxy templates from here to the EE repository.
    • [ ] Copy the realm.json files for all flavors from here to the EE repository.
    • [ ] Update the Catalog Crawler image in EE's .env.
    • [ ] Link this release in the EE changelog.
    • [ ] Merge the release-prep PR.
    • [ ] Deploy a version with the PR-Tag to Sirius and test the deployment.
  • [ ] Create a release, re-use the changelog section as EE release description.
  • [ ] Re-use the version of this release as the title for the EE release.
• [ ] Notify the deployment team, which will send a message to the customer about the new release.
• [ ] release-cleanup PR:
  • [ ] Revisit the changed list of tasks and compare it with .github/ISSUE_TEMPLATE/release.md. Apply changes where it makes sense.
  • [ ] Merge the release-cleanup PR.

[kamilczaja]

Skipping EE release because of 4.2.0 releasing right after, including all changes made in 4.1.1