PR #42 only uploaded the built .pkg.tar.zst to the GitHub release. The Gitea release for the same version (the plain vX.Y.Z tag build-app.yml's Linux job creates, already holding the .deb/.rpm/.AppImage) never got it, so anyone checking releases on Gitea instead of GitHub saw it missing.
Adds a second upload step that mirrors build-app.yml's own Gitea upload step exactly: same get-or-create-by-tag, delete-existing-asset, upload-as-octet-stream shape, same REGISTRY_TOKEN secret — no new secret setup needed.
Test plan
YAML parses
Dry-ran the read side (release lookup by tag, asset listing) against the real v0.4.16 Gitea release before writing the delete/upload calls — resolves to release id 925, correctly finds no existing asset yet
Re-run Publish Arch Package via workflow_dispatch after merge to confirm it lands on both releases
PR #42 only uploaded the built `.pkg.tar.zst` to the GitHub release. The Gitea release for the same version (the plain `vX.Y.Z` tag build-app.yml's Linux job creates, already holding the `.deb`/`.rpm`/`.AppImage`) never got it, so anyone checking releases on Gitea instead of GitHub saw it missing.
Adds a second upload step that mirrors `build-app.yml`'s own Gitea upload step exactly: same get-or-create-by-tag, delete-existing-asset, upload-as-octet-stream shape, same `REGISTRY_TOKEN` secret — no new secret setup needed.
## Test plan
- [x] YAML parses
- [x] Dry-ran the read side (release lookup by tag, asset listing) against the real `v0.4.16` Gitea release before writing the delete/upload calls — resolves to release id 925, correctly finds no existing asset yet
- [ ] Re-run `Publish Arch Package` via workflow_dispatch after merge to confirm it lands on both releases
The workflow only ever uploaded to the GitHub release — the Gitea release
for the same version (the plain, unsuffixed vX.Y.Z tag build-app.yml's
Linux job creates, which already holds the .deb/.rpm/.AppImage) never got
it, so it looked missing to anyone checking releases on Gitea instead of
GitHub.
New step mirrors build-app.yml's own Gitea upload step exactly: same
get-or-create-by-tag, delete-existing-asset, upload-as-octet-stream shape,
same REGISTRY_TOKEN secret. Verified the read side (release lookup, asset
listing) against the real v0.4.16 release before writing this — resolves
to the correct release id and correctly finds no existing asset yet.
jknapp
merged commit 8beb62b12c into main2026-08-27 22:21:58 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
PR #42 only uploaded the built
.pkg.tar.zstto the GitHub release. The Gitea release for the same version (the plainvX.Y.Ztag build-app.yml's Linux job creates, already holding the.deb/.rpm/.AppImage) never got it, so anyone checking releases on Gitea instead of GitHub saw it missing.Adds a second upload step that mirrors
build-app.yml's own Gitea upload step exactly: same get-or-create-by-tag, delete-existing-asset, upload-as-octet-stream shape, sameREGISTRY_TOKENsecret — no new secret setup needed.Test plan
v0.4.16Gitea release before writing the delete/upload calls — resolves to release id 925, correctly finds no existing asset yetPublish Arch Packagevia workflow_dispatch after merge to confirm it lands on both releases