Create a Gitea release on tag #26

Merged
benvin merged 2 commits from benvin/gitea-releases into main 2026-10-04 15:00:19 +11:00
Member

Tagged releases should publish a Gitea release with binaries, not only an RPM in artifactapi.

  • release step runs on docker-internal/tea:0.1.0 (tea 0.14.0 on PATH) after upload-rpm
  • Generates notes from commits since the previous ancestor tag
  • Creates the Gitea release via RELEASER_TOKEN
  • Attaches tomswall-linux-amd64, the RPM and sha256sums.txt
Tagged releases should publish a Gitea release with binaries, not only an RPM in artifactapi. - `release` step runs on `docker-internal/tea:0.1.0` (tea 0.14.0 on PATH) after `upload-rpm` - Generates notes from commits since the previous ancestor tag - Creates the Gitea release via `RELEASER_TOKEN` - Attaches `tomswall-linux-amd64`, the RPM and `sha256sums.txt`
unkin-agent added 1 commit 2026-10-04 13:59:37 +11:00
Create a Gitea release with binary, RPM and checksums on tag
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/test Pipeline was successful
ci/woodpecker/pr/pre-commit Pipeline was successful
da32729556
Author
Member

No findings.

No findings.
unkin-agent added 1 commit 2026-10-04 14:51:16 +11:00
Run release step on prebuilt tea image
ci/woodpecker/pr/build Pipeline was successful
ci/woodpecker/pr/test Pipeline was successful
ci/woodpecker/pr/pre-commit Pipeline was successful
6fc8ae9256
Author
Member
  • .woodpecker/release.yaml:131 — nit: sha256sum $$ASSETS records the RPM as dist/<file>.rpm, so sha256sum -c sha256sums.txt fails for anyone who downloads the assets flat → cp "$$RPM" . and use basenames in ASSETS, or cd dist before hashing.
- .woodpecker/release.yaml:131 — nit: `sha256sum $$ASSETS` records the RPM as `dist/<file>.rpm`, so `sha256sum -c sha256sums.txt` fails for anyone who downloads the assets flat → `cp "$$RPM" .` and use basenames in `ASSETS`, or `cd dist` before hashing.
benvin merged commit 2dd408c54e into main 2026-10-04 15:00:19 +11:00
benvin deleted branch benvin/gitea-releases 2026-10-04 15:00:19 +11:00
Sign in to join this conversation.