[ci] No release artifacts despite "success" tag runs (Feb-2026); likely same root cause as hero_biz cluster #26

New issue

Open

opened 2026-05-03 23:36:57 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-03 23:36:57 +00:00

Owner

Audit context

Filed during Phase 2 CI audit (hero_demo#54, session 55).

State

Tags exist: v0.0.1-rc1, v0.1.0
Forgejo Releases: none
Forgejo package registry: empty
Tag-triggered runs: 2 attempts on Feb 2026, both status=success per Forgejo API

Root cause (likely)

This repo's build-linux.yaml is the same shared-helper template as hero_biz / hero_books / hero_browser (cluster A) — scripts/build_lib.sh::publish_binaries writes only to the package registry. The fact that pkg registry is empty (unlike its siblings) suggests these Feb-2026 runs ran before the publish_binaries step did anything useful, or before forge_config was wired correctly. No tags pushed since.

Verification needed

Re-tag v0.1.1 and watch the run — expect a binary to appear in the pkg registry (proving the helper is now wired).
Then it joins the same cluster-A fix path: add Release-assets upload step.

Cluster

Cluster A sibling: hero_biz, hero_books, hero_browser.

Recommended fix

Same as cluster A — add Create Release + Upload Release Assets steps to build-linux.yaml. Then re-tag.

Effort

Quick win — 1-2 h once cluster A is templated. Phase 2 implementation.

## Audit context Filed during Phase 2 CI audit ([hero_demo#54](https://forge.ourworld.tf/lhumina_code/hero_demo/issues/54), session 55). ## State - Tags exist: `v0.0.1-rc1`, `v0.1.0` - Forgejo Releases: **none** - Forgejo package registry: **empty** - Tag-triggered runs: 2 attempts on Feb 2026, both `status=success` per Forgejo API ## Root cause (likely) This repo's `build-linux.yaml` is the same shared-helper template as hero_biz / hero_books / hero_browser ([cluster A](https://forge.ourworld.tf/lhumina_code/hero_biz/issues/13)) — `scripts/build_lib.sh::publish_binaries` writes only to the package registry. The fact that pkg registry is empty (unlike its siblings) suggests these Feb-2026 runs ran before the `publish_binaries` step did anything useful, or before `forge_config` was wired correctly. No tags pushed since. ## Verification needed - Re-tag v0.1.1 and watch the run — expect a binary to appear in the pkg registry (proving the helper is now wired). - Then it joins the same cluster-A fix path: add Release-assets upload step. ## Cluster Cluster A sibling: hero_biz, hero_books, hero_browser. ## Recommended fix Same as cluster A — add **Create Release** + **Upload Release Assets** steps to `build-linux.yaml`. Then re-tag. ## Effort Quick win — 1-2 h once cluster A is templated. Phase 2 implementation.