TC 3.0.5

[f-peverali]

… FHIR Validation)

Version Upgrade Template

Version:

Date:

Description

This is a Pullrequest 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

• 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".
• This PR has a clean meaningful commit history. Minor commits or commits without description have been squashed, at the latest now.
• The GitHub Actions "TC version update" and "CI (FHIR Validation)" finished successfully; release version and date was updated accordingly by release_publish.py (triggered by action)
• Eventually, increase the dependency of to newer Basis Modul and Basispofil-de and possibly others (package json and sushi-config)
• All release note items have been annotated as test modifiying OR test stable (the annotation should already take place within tickets for tracking reasons)
• the release notes were reviewed with a person responsible for testing
• New Release Notes were created, alined to the commit history. Possibly, if you want to check the release notes for completeness, check against automatic relesase note generation in GitHub. In Github, go to
  • -> Releases then -> Draft a new release with the Modul Name and Version, then
  • -> Target the main-Branch and -> enter a new Tag according to the Version, then click.
  • 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.
  • Finally -> Save as Draft

Merge and Publishing

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

Post-Merge Activities

• Go to the corresponding SIMPLIFIER Project and -> Github -> Reimport the project.
• Go to the corresponding SIMPLIFIER Project and -> Packages -> Expand the Dropdown for Create -> Create new package for the project.
  • With the corresponding version number, and
  • The Release notes (from above) and a compare-link to the previous Release.
  • Unlist the old package by -> clicking on the old package, -> go to Administration and -> click on Unlist
• Publish the previously drafted Release, including version number, on GitHub.
• Publish IG in Simplifier
  • Provide a version in the IG title --> (x.x.x)
  • Scope the IG to the published package
  • Set URL key to isik-[module-name]-version (version without dots)
  • Publish via Simplifier GUI (set to overwritable)

Obsolete

• 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
• Add the zip (other tasks are automated by action called "Unzip and Update IG Version in webpage", in order to provide the Archige in the following page . https://gematik.github.io/spec-ISiK-Basismodul/index.html)
• If ISiK Basismodul was updated all depending Modules should be updated with a renewed dependency to the incremented Basismodul version - possibly including and closing technical corrections

Finished