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 4.0.1 #203

Merged
merged 126 commits into from
Jan 24, 2025
Merged

TC 4.0.1 #203

merged 126 commits into from
Jan 24, 2025

Conversation

f-peverali
Copy link
Contributor

@f-peverali f-peverali commented Sep 23, 2024

… FHIR Validation)

Version Upgrade Template

Version: 4.0.1

Date: 02.12.2024

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.
  • By running the Release_Publish.py script, release version and date was updated accordingly. The script ran without errors.
  • 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 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)
  • Publish the previosuly drafteted Release, including version number, on GitHub.

Obsolet

  • 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 changed the title auto-generated file update of TC version by GitHub Actions (CI FSH to… TC 4.0.1 Sep 23, 2024
f-peverali and others added 18 commits September 23, 2024 14:19
Übertragung sämtlicher instanzbezogener Doku aus dem IG in FSH
Update ISiKCapabilityStatementDokumentenaustauschServer.fsh
Motivation aus IG migriert nach DocumentReference.purpose
fix syntax for purpose entry
fix pagelinks in rest.resource.documentation
Dokumentation der MS Elemente
ISiKDokumentenMetadaten Bundle
@f-peverali

This comment was marked as resolved.

nikohl-de
nikohl-de previously approved these changes Jan 24, 2025
@f-peverali f-peverali merged commit 70372dd into main-stufe-4 Jan 24, 2025
3 checks passed
@f-peverali f-peverali deleted the TC_4.0.1 branch January 24, 2025 13:24
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.

5 participants