b32e20cddb
All checks were successful
release / build-and-release (push) Successful in 35s
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> |
||
|---|---|---|
| .. | ||
| release.yml | ||