GRM-52: fix: badges job runs after release to reflect actual state

.gitea/workflows/post-merge.yml

@@ -8,9 +8,13 @@ name: Post-merge
 #
 #   detect-type ──┬── release (skip if release commit)
 #                 ├── sync-wiki (skip if release commit)
-#                 ├── badges (skip if release commit)
+#                 ├── badges (runs after release, even if it fails)
 #                 └── vikunja (skip if release commit)
 #
+# The badges job depends on release so it picks up the latest version
+# number. It uses `if: always()` to run even if release fails or is
+# skipped, ensuring badges always reflect the current repo state.
+#
 # When release.py creates a "release: vX.Y.Z" commit, all jobs skip
 # because it's a release commit. The tag push triggers publish.yml.
 
@@ -98,15 +102,20 @@ jobs:
             --commit "${{ github.sha }}"
 
   badges:
-    needs: [detect-type]
-    if: needs.detect-type.outputs.is-release == 'false'
+    needs: [detect-type, release]
+    if: always() && needs.detect-type.outputs.is-release == 'false'
     runs-on: docker
     timeout-minutes: 10
     steps:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
+          ref: master
           token: ${{ secrets.REPO_TOKEN }}
+      - name: Fetch latest master
+        run: |
+          git fetch origin master
+          git reset --hard origin/master
       - name: Set up environment
         run: make setup
       - name: Generate and push badges