jwinterm f4bbfd49ad fix(ci): publish the signed Windows zips to the tag's release ...

The Linux and macOS jobs already attach their tag-build output to the release,
because this Gitea reports zero artifacts for every run through its REST API and
its web download route answers "Not found." under every auth style. The Windows
job was left out, so even a green signed build produced an exe nobody could
fetch back.

The step runs after the Authenticode, RFC 3161 timestamp and signer checks, so
an unsigned or untimestamped binary can never reach a release. Both archives go
up: the signed one users should download, and the unsigned one that stays
byte-reproducible for verifiers.

curl.exe rather than Invoke-WebRequest, because `shell: powershell` is Windows
PowerShell 5.1 and its Invoke-WebRequest has no -Form for multipart uploads.
Fail-safe like the others: no token, no resolvable release or a non-201 upload
reports itself and exits 0 rather than reddening a build that produced a
correctly signed binary.

2026-09-13 18:09:17 -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): publish the signed Windows zips to the tag's release

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