added seperate workflow to publish releases

.github/workflows/platformio.yml

@@ -1,12 +1,12 @@
-name: PlatformIO CI
+name: build_firmware
 
 on: [push]
 
 
 # see e.g. https://cgrotz.github.io/2020-08-24-esp32_ci_cd_part2/
 
 jobs:
-  build:
+  buildFirmware:
     #runs-on: ubuntu-latest
     runs-on: windows-latest
 

.github/workflows/publish_release.yml

@@ -0,0 +1,32 @@
+name: publish_artifacts_as_release
+
+
+# Only trigger, when the build workflow succeeded, see https://stackoverflow.com/questions/62750603/github-actions-trigger-another-action-after-one-action-is-completed
+on:
+  workflow_run:
+    workflows: ["build_firmware","build_simhub_plugin"]
+    types:
+      - completed
+
+
+# This is the list of jobs that will be run concurrently.
+# Since we use a build matrix, the actual number of jobs
+# started depends on how many configurations the matrix
+# will produce.
+jobs:
+
+# https://docs.github.com/de/actions/using-workflows/storing-workflow-data-as-artifacts
+
+jobs:
+  deploy:
+    name: deploy
+    runs-on: ubuntu-latest
+    steps:
+      - name: Download math result for job 2
+        uses: actions/download-artifact@v4
+        with:
+          name: ["simhub_plugin","firmware_esp32"]
+      - name: Print the final result
+        shell: bash
+        run: |
+          echo The result is good