SubochevAV eed1ab9a17 ci: replace forgejo-release action with direct API call to attach assets ...

forgejo-release@v1 calls 'tea release create' which errors with
'There already is a release for this tag' when the release is
pre-created (which release.yml needs because the trigger is
'release.published').

Workaround: do the upload ourselves via POST /api/v1/repos/.../releases/{id}/assets
with binary body. This is what forgejo-release ends up doing internally
after it successfully creates the release.

2026-09-16 22:20:37 +03:00

..

workflows

ci: replace forgejo-release action with direct API call to attach assets

2026-09-16 22:20:37 +03:00