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.2 #247

Open
wants to merge 5 commits into
base: main-stufe-4
Choose a base branch
from
Open

TC_4.0.2 #247

wants to merge 5 commits into from

Conversation

f-peverali
Copy link
Contributor

Version Upgrade Template

Version: 4.0.2

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 successfull, release version and date was updated accordingly.
  • Eventually, increase the dependency of to newer Basis Modul and Basispofil-de and possibly others (package json and sushi-config)
  • Run Python script in terminal and increment version --> Eventeu
  • 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 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 changed the title auto-generated file update of TC version by GitHub Actions TC_4.0.2 Dec 5, 2024
f-peverali and others added 4 commits December 5, 2024 13:45
* add workflow basis reference

* update basis reference

* update branch

* update owner

* change name of workflow file

* change branch

* test action

* update secrets

* test commit

* auto-generated FHIR files by GitHub Actions (CI FSH to FHIR Validation)

* remove comment

* test commit

* update dependency branch

* auto-generated FHIR files by GitHub Actions (CI FSH to FHIR Validation)

* delete reference yml and include in main

* change branch

* change trigger

* test commit

* test commit

* auto-generated FHIR files by GitHub Actions (CI FSH to FHIR Validation)

* change branch of call-tool-update

* change name

---------

Co-authored-by: leslieber <[email protected]>
Co-authored-by: f-peverali <[email protected]>
Co-authored-by: f-peverali <[email protected]>
* update text

* auto-generated FHIR files by GitHub Actions (CI FSH to FHIR Validation)

---------

Co-authored-by: f-peverali <[email protected]>
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.

2 participants