From b32e20cddba5b7e87fb76864ca2023ff3e4beb31 Mon Sep 17 00:00:00 2001 From: X9 Dev Date: Tue, 28 Jul 2026 19:19:58 +0200 Subject: [PATCH] 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 --- .forgejo/workflows/release.yml | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/.forgejo/workflows/release.yml b/.forgejo/workflows/release.yml index 43b3154..82b1d03 100644 --- a/.forgejo/workflows/release.yml +++ b/.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: