Tc 3.0.2

[f-peverali]

Version Upgrade Template

Version: 3.0.2

Date:

Description

This is a Pullreuqest that requires an increase in the Version number. Therefore, multiple outside-github, related Task have to be performed and checked.

All jobs with an x in the boxes were performed to the best of knowledge.

Pre-Merge Activities

• [x] This PR refers to a versioned Branch with a name and a version number in the form of N.n.n, e.g. "TC_3.2.1".
• [x] This PR has a clean meaningful committ history. Minor committs or committs without descirption have been squashed, at the latest now.

• [x] The ./github/workflows/main.yml refers to the correct Firetly Terminal and SUSHI Version.

  Firely Terminal Pipeline 0.4.0.

  SUSHI Versions 3.5.0.

• [x] By running the _ReleasePublish.py script, release version and date was updated accordingly. The script ran without errors.
• [x] Eventually, increase the dependency of to newer Basis Modul (package and sushi-config)
• [x] New Release Notes were created, aglined to the committ history and cleaned. In Github, go to
  • [x] -> Releases then -> Draft a new release with the Modul Name and Version, then
  • [x] -> Target the main-Branch and ->enter a new Tag according to the Version, then click.
  • [x] Click -> Generate Release notes , ->Adjust them if necessary and -> Copy/Paste the Details in the RealeaseNotes.md of the very Branch you want to merge.
  • [x] Finally -> Save as Draft

Merge and Publishing

• [x] With the updated Version, Dates, and Release Notes (as described above) with the last committ into the Branch you want to merge.
• [x] In GitHub -> Actions the ->CI (FHIR Validation) workflow terminates successfully.
• [x] Add the Approve / the PR gets posivitly reviewed by a collegue.
• [x] Merge (without squash) the PR, delete the Branch.

Post-Merge Activities

• [x] Go to the corresponding SIMPLIFIER Project and -> Github -> Reimport the project.
• [x] Go to the corresponding SIMPLIFIER Project and -> Packages -> Expand the Dropdown for Create -> Create new package for the project.
  • [x] With the corresponding version number, and
  • [x] The Release notes (from above) and a compare-link to the previous Release.
  • [x] Unlist the old package by -> clicking on the old package, -> go to Admininstration and -> click on Unlist
• [x] Publish the previosuly drafteted Release, including version number, on GitHub.
• [ ] Provide / Archive the IG in the corresponding gh-pages branch of the GitHub project.
  • [ ] Checkout the Branch (no need to merge it later).
  • [ ] Export from Simplifier via -> Guides -> Expand the Modul ... -> Export
  • [ ] Unpack the zip, remove the packages folder (because its kinda big), and move everything else to a (version coressponding) new folder in the branch folder structure.
  • [ ] committ the branch.

Finished

[f-peverali]

IG will not be archived, since no relevant change in IG