Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tc 3.0.4 #195

Merged
merged 17 commits into from
Nov 25, 2024
Merged

Tc 3.0.4 #195

merged 17 commits into from
Nov 25, 2024

Conversation

f-peverali
Copy link
Contributor

@f-peverali f-peverali commented May 21, 2024

Version Upgrade Template

Version: 3.0.4

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

  • 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".
  • 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.

  • The Release_Publish.py script, release version and date was updated accordingly. The script ran without errors as a github-action
  • Eventually, increase the dependency of to newer Basis Modul (package and sushi-config)
  • New Release Notes were created, aglined to the committ history and cleaned. 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 posivitly reviewed by a collegue.
  • 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 Admininstration and -> click on Unlist
  • 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 f-peverali marked this pull request as draft June 20, 2024 12:34
@f-peverali
Copy link
Contributor Author

VORSICHT: IHE dependency hier ggf. im Konflikt mit bestehender (aus Basisprofile-DE)?! @alexzautke

@f-peverali f-peverali marked this pull request as ready for review November 25, 2024 07:30
@nikohl-de nikohl-de merged commit b528895 into main-stufe-3 Nov 25, 2024
1 check passed
@nikohl-de nikohl-de deleted the TC_3.0.4 branch November 25, 2024 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants