From 12006bdf944da75a6874e46c5b57d00da43b2f58 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Martin?= Date: Tue, 6 Oct 2026 17:01:04 +0200 Subject: [PATCH] CI: the release badge follows a tag, not only a push to main 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 Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT --- .gitea/workflows/ci.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index d41473a..2531c73 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -59,9 +59,10 @@ jobs: if: github.event_name == 'pull_request' || github.ref_type == 'tag' 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 - 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: GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }} run: |