[ci] Release v0.1.4 has zero assets; v0.1.5 has no Release at all — `--from-ci` blind #118

New issue

Open

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

mik-tf commented

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

Owner

Audit context

Filed during Phase 2 CI audit (hero_demo#54, session 55). Distinct symptom: a Release object DOES exist for v0.1.4 (asset count 0), but v0.1.5 has no Release.

State

Tags: v0.1.0 … v0.1.5
Forgejo Release: v0.1.4 only (created 2026-02-08), 0 assets
Forgejo package registry: hero_books 0.1.2 / 0.1.3 / 0.1.4 / 0.1.5 / dev ✓ binaries present
build-linux.yaml runs all status=success

Root cause

Same as hero_biz#13 — scripts/build_lib.sh::publish_binaries only writes to the package registry, never to Release assets. v0.1.4's empty Release was likely auto-created by Forgejo on tag-push (separate from CI), and the workflow never attached assets to it.

svc_install_from_ci consumes Release assets, not pkg-registry, so this repo is invisible to --from-ci hero_books.

Cluster

Sibling issues: hero_biz, hero_browser. Likely also hero_foundry.

Recommended fix

Same as cluster: add Create Release + Upload Release Assets steps to build-linux.yaml (mirror hero_proc pattern). Then re-tag v0.1.6 and verify --from-ci hero_books resolves.

Effort

Quick win — 1-2 h. 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). Distinct symptom: a Release object DOES exist for v0.1.4 (asset count 0), but v0.1.5 has no Release. ## State - Tags: `v0.1.0` … `v0.1.5` - Forgejo Release: `v0.1.4` only (created 2026-02-08), **0 assets** - Forgejo package registry: `hero_books 0.1.2 / 0.1.3 / 0.1.4 / 0.1.5 / dev` ✓ binaries present - `build-linux.yaml` runs all `status=success` ## Root cause Same as [hero_biz#13](https://forge.ourworld.tf/lhumina_code/hero_biz/issues/13) — `scripts/build_lib.sh::publish_binaries` only writes to the package registry, never to Release assets. v0.1.4's empty Release was likely auto-created by Forgejo on tag-push (separate from CI), and the workflow never attached assets to it. `svc_install_from_ci` consumes Release assets, not pkg-registry, so this repo is invisible to `--from-ci hero_books`. ## Cluster Sibling issues: hero_biz, hero_browser. Likely also hero_foundry. ## Recommended fix Same as cluster: add **Create Release** + **Upload Release Assets** steps to `build-linux.yaml` (mirror hero_proc pattern). Then re-tag v0.1.6 and verify `--from-ci hero_books` resolves. ## Effort Quick win — 1-2 h. Phase 2 implementation.