ci: retry release file uploads over HTTP/1.1

jcoffey-dev commented

2026-09-30 23:50:05 +00:00

Owner

The same fix as inbuxa-server #138. That repo's first GitHub-built release lost 50 MB uploads to Gitea's release API through Cloudflare on both runs of its binaries job (curl 92, HTTP/2 PROTOCOL_ERROR; origin logged 400). This workflow uploads the same way.

Uploads now use HTTP/1.1, and the asset listing and uploads retry (5 tries, 15 s apart).

This only runs on a tag, so the next release tests it. No new strings.

The same fix as inbuxa-server #138. That repo's first GitHub-built release lost 50 MB uploads to Gitea's release API through Cloudflare on both runs of its binaries job (curl 92, HTTP/2 PROTOCOL_ERROR; origin logged 400). This workflow uploads the same way. Uploads now use HTTP/1.1, and the asset listing and uploads retry (5 tries, 15 s apart). This only runs on a tag, so the next release tests it. No new strings.

jcoffey-dev added 1 commit 2026-09-30 23:50:05 +00:00

ci: retry release file uploads over HTTP/1.1

ci / announce (pull_request) Skipped

Details

github/ci (branch) GitHub Actions

Details

ci / github (pull_request) Successful in 2m15s

Details

ci / test (pull_request) Skipped

Details

25083c8388

inbuxa-server's first GitHub-built release lost 50 MB uploads to
Gitea's release API through Cloudflare (curl 92, HTTP/2 PROTOCOL_ERROR)
on both runs of its binaries job. This job uploads the same way. Uploads
now go over HTTP/1.1, and the asset listing and uploads retry 5 times.

jcoffey-dev merged commit 86b24460b6 into main

2026-09-30 23:52:45 +00:00

jcoffey-dev deleted branch ci/release-upload-retry

2026-09-30 23:52:45 +00:00

ci: retry release file uploads over HTTP/1.1 #14