Fix Forgejo release asset publication #31

Merged
pti merged 1 commit from fix/release-publish-api into main 2026-07-24 12:53:39 +02:00
Owner

Replaces the incompatible Forgejo release action after v0.2.1 verification tests and all six builds succeeded but publication failed because FORGEJO_PATH is unavailable on the native runner. Uses the Forgejo API with the automatic repository token and supports safe immutable tag retries by reusing a release and replacing existing same named assets. Tests vet lint shell tests YAML parsing and diff checks pass.

Replaces the incompatible Forgejo release action after v0.2.1 verification tests and all six builds succeeded but publication failed because FORGEJO_PATH is unavailable on the native runner. Uses the Forgejo API with the automatic repository token and supports safe immutable tag retries by reusing a release and replacing existing same named assets. Tests vet lint shell tests YAML parsing and diff checks pass.
fix(release): publish through Forgejo API
All checks were successful
Lint / lint (pull_request) Successful in 23s
0b543bfdbd
The Forgejo release action expects runner environment files unavailable on the native runner. Use the repository API directly and make asset uploads replaceable so immutable-tag retries remain safe.
pti merged commit ba9692a7c2 into main 2026-07-24 12:53:39 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pti/wraptool!31
No description provided.