CI: the release badge follows a tag, not only a push to main
CI / build (pull_request) Successful in 8m6s

After v0.11.0 was published the badge still said v0.10.0 until the next
push to main. Tag runs run the tests and coverage already; they now
publish the badges too.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT
This commit is contained in:
2026-10-06 17:01:04 +02:00
co-authored by Claude Sonnet 5.5
parent 148611ff4c
commit 12006bdf94
+3 -2
View File
@@ -59,9 +59,10 @@ jobs:
if: github.event_name == 'pull_request' || github.ref_type == 'tag' if: github.event_name == 'pull_request' || github.ref_type == 'tag'
run: scripts/ci.sh builds run: scripts/ci.sh builds
# The README's badges are files on a branch of their own, replaced at each push to main. # The README's badges are files on a branch of their own, replaced at each push to main and
# at each tag (the release badge says which tag is the latest)
- name: Publish the badges - name: Publish the badges
if: github.event_name == 'push' && github.ref == 'refs/heads/main' if: github.event_name == 'push' && (github.ref == 'refs/heads/main' || github.ref_type == 'tag')
env: env:
GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }} GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}
run: | run: |