ci: drop paths filter so version-tag pushes always build

Forgejo applies the push 'paths' filter to tag pushes too (unlike GitHub),
so a version tag on a docs-only commit (e.g. "docs: release 0.10") was
silently skipped and never produced a named release - it had to be kicked
off manually via workflow_dispatch on the tag ref. Continuous builds on
every main push are the documented behavior anyway, so drop paths entirely.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.forgejo/workflows/release.yml

@@ -5,15 +5,11 @@ on:
   push:
     branches: [main]
     tags: ['v*']
-    paths:
-      - '**.go'
-      - 'go.mod'
-      - 'go.sum'
-      - 'scripts/**'
-      - 'assets/**'
-      - 'embed.go'
-      - 'cmd/xetup/app.manifest'
-      - '.forgejo/workflows/release.yml'
+    # No 'paths' filter on purpose: Forgejo (unlike GitHub) also applies paths
+    # to TAG pushes, so a version tag on a docs-only commit gets silently
+    # skipped and never produces a named release. Continuous builds on every
+    # main push are the documented behavior anyway (see CHANGELOG header), so
+    # the paths optimization is not worth the release-tag footgun.
 
 jobs:
   build-and-release:

web/index.html

@@ -161,6 +161,7 @@
     <a href="/changelog/">Changelog</a>
     <a href="https://git.xetup.x9.cz/x9/xetup">Git</a>
     <a href="https://git.xetup.x9.cz/x9/xetup/issues">Issues</a>
+    <a href="https://git.xetup.x9.cz/x9/xetup-runs/issues">Chyby behu</a>
   </nav>
 </header>