Crylia/lg_update_blocker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity
5 Commits 1 Branch 3 Tags
main
Commit Graph
2 Commits
Author SHA1 Message Date
Rene KievitsandClaude Opus 5 bf2daac146 ci: publish releases to Gitea instead of GitHub
Build / build (push) Successful in 48s
Details 
The workflow was written for github.com: actions/upload-artifact failed on
the Gitea runner, softprops/action-gh-release only talks to the GitHub API,
and gen-manifest.js hardcoded github.com URLs.

- drop the artifact upload (release assets are the deliverable)
- upload release assets with tools/release-gitea.js, a dependency-free
  Gitea API client; re-running a tag replaces the attachments
- gen-manifest.js takes --server/PUBLIC_SERVER_URL and knows that Gitea
  spells the latest-asset URL /releases/download/latest/<file>
- PUBLIC_SERVER_URL is set explicitly because the runner only sees the
  instance's internal LAN address

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
 2026-09-05 22:41:03 +02:00
Rene Kievits b137bf9eda init commit
Build / build (push) Failing after 1m50s
Details
2026-09-05 22:27:44 +02:00