Update version with first beta of v2.6.1 (v2.6.0 was created based on previous commit) (#304)

.scripts/HowToCreateANewRelease.md

@@ -80,7 +80,7 @@ Following script calls
 - Update README.md with the new release header and title (based on the `readme_release_header.txt` template)
 
 ```bash
-python ./.scripts/transform_files.py UpdateC4WithReleaseVersion
+python ./.scripts/transform_files.py UpdateAllIncludes
 python ./.scripts/transform_files.py UpdateAllImages
 python ./.scripts/transform_files.py ReplaceREADMEHeader
 ```
@@ -91,6 +91,8 @@ Following commit all changes and tag it locally with `$release_version` (e.g. `v
 
 ```bash
 git checkout release/$release_version
+git add -u *.md
+git add -u *.puml
 git add -u **/*.md
 git add -u **/*.puml
 git commit -m "Create release (branch) $release_version"

.scripts/transform_files.py

@@ -219,7 +219,7 @@ def update_c4_release_version():
 def update_c4_next_beta_version():
     # $c4Version is defined without starting 'v'
     print(
-        f"updating C4Version() definition in C4.puml with new release_version {release_version[1:]} ..."
+        f"updating C4Version() definition in C4.puml with new release_version {next_version[1:]} ..."
     )
     replace_first_regex_in_file(
         "C4.puml", r'!\$c4Version  =  ".+"', f'!$c4Version  =  "{next_version[1:]}beta1"'

C4.puml

@@ -4,7 +4,7 @@
 ' ##################################
 !function C4Version()
   ' 2 spaces and ' are used as unique marker, that the release scripts makes the correct version update
-  !$c4Version  =  "2.6.0beta2"
+  !$c4Version  =  "2.6.1beta1"
   !return $c4Version
 !end function