The 'Create Forgejo release + upload artifact' step has been failing
intermittently with no useful error message in the logs (just a 0s
step duration and 'Complete job' failure). Replace the
curl -fsS + bash-set-e pattern that swallows HTTP error bodies with:

- explicit empty-token guard that aborts with a clear ::error::
  message instead of an opaque 401
- python-generated JSON payload (replacing the heredoc-with-$(python)
  trick that lost the python exit code and could produce malformed
  JSON on weird content)
- use of git rev-parse HEAD (full SHA) instead of --short, since
  Forgejo's release API accepts either but full is unambiguous
- captured HTTP status + response body so any 4xx/5xx prints the
  actual server-side error message before the step aborts
- a visible skip message when the asset isn't available so it's
  obvious why the asset-upload block was skipped

Together these turn a silent 0s failure into a self-documenting run
that either succeeds or tells you exactly what the API rejected.

akinus merged commit 61f7a7fdd2 into main

2026-06-27 18:58:28 +00:00

akinus referenced this pull request from a commit

2026-06-27 18:58:31 +00:00

Merge pull request 'devops -> main' (#50) from devops into main