jwinterm a43e9fe122 fix(ci): publish tag builds to the release, where they can be fetched back ...

Run artifacts upload fine, but this Gitea reports zero artifacts for every run
through its REST API, and the web download route answers "Not found." under
token, bearer and basic auth alike. A signed build was therefore unreachable
from anywhere except the browser session that produced it.

Release assets do work: create, upload, list and download all round-trip with
an ordinary token, so tag builds now attach their output to the tag's release
as well as to the run. Retrieval must use browser_download_url; the asset-id
API path returns the asset's JSON metadata even when asked for octet-stream.

The step is fail-safe on purpose. With no token, no resolvable release, or a
non-201 upload it explains itself and exits 0 rather than turning a green
build red. The macOS upload also gains if-no-files-found, without which an
empty publish passes silently.

2026-09-13 13:18:22 -04:00

..

build-linux.yml

fix(ci): publish tag builds to the release, where they can be fetched back

2026-09-13 13:18:22 -04:00

build-macos.yml

fix(ci): publish tag builds to the release, where they can be fetched back

2026-09-13 13:18:22 -04:00

build-windows.yml

fix(ci): scope the embed extracts to the run, not to a shared /tmp

2026-09-13 13:13:35 -04:00