From 3bb4d2afe13804633377218a2f5efc2dcfbceb5e Mon Sep 17 00:00:00 2001 From: Leslie Bernhardt Date: Tue, 3 Dec 2024 10:11:44 +0100 Subject: [PATCH] Remove step newer Basismodul dependency --- .github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md b/.github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md index bbbbc659..6a26ee28 100644 --- a/.github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md +++ b/.github/PULL_REQUEST_TEMPLATE/PR_Template_VersionUpgrade.md @@ -15,9 +15,9 @@ All jobs with an `x` in the boxes were performed to the best of knowledge. - [ ] 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. -- [ ] Eventually, increase the dependency of to newer Basis Modul and Basispofil-de and possibly others (package json and sushi-config) +- [ ] Eventually, increase the dependency of to newer Basisprofil-de and possibly others (package json and sushi-config) - [ ] Run Python script in terminal and increment version -- [ ] 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 +- [ ] New Release Notes were created, alined to the commit history. Possibly, if you want to check the release notes for completeness, check against automatic release 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.