ci(release): publish the release to tildeforge as well

.forgejo/workflows/release.yml

@@ -38,7 +38,7 @@ jobs:
 
       # No `submodules:` on the checkout above, so the tap is empty here and the
       # sdist below differs from a local `uv build` with the submodule populated.
-      # The published asset is therefore the authority: tools/bump_packaging.py
+      # The published asset is therefore the authority: bump_packaging.py
       # hashes the download, never a rebuild.
       - name: Build the sdist and wheel
         run: |
@@ -72,3 +72,28 @@ jobs:
           tag: ${{ forgejo.ref_name }}
           title: ${{ forgejo.ref_name }}
           release-notes-file: dist/notes.md
+
+      # Every packaging channel (AUR, the Homebrew tap and the flake) downloads
+      # its source from tildeforge, so the release is published there as well.
+      # That repository is not a mirror of this one: nothing reaches it unless
+      # it is pushed, hence the tag push before the upload.  Pushing a tag that
+      # is already there and identical is a no-op, so this stays re-runnable.
+      - name: Push the tag to tildeforge
+        env:
+          TILDEFORGE_TOKEN: ${{ secrets.TILDEFORGE_TOKEN }}
+        run: |
+          git push \
+            "https://beefcarver:${TILDEFORGE_TOKEN}@tildeforge.dev/beefcarver/beefy-player.git" \
+            "refs/tags/${FORGEJO_REF_NAME}"
+
+      - name: Publish the release to tildeforge
+        uses: actions/forgejo-release@v2
+        with:
+          direction: upload
+          url: https://tildeforge.dev
+          repo: beefcarver/beefy-player
+          token: ${{ secrets.TILDEFORGE_TOKEN }}
+          override: true
+          tag: ${{ forgejo.ref_name }}
+          title: ${{ forgejo.ref_name }}
+          release-notes-file: dist/notes.md