[ci] No `v*` tag has been pushed; `build-linux.yaml` exists but never triggered #5

New issue

Open

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

mik-tf commented

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

Owner

Audit context

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

State

Tags: none
Forgejo Releases: none
Forgejo package registry: empty (not checked)
.forgejo/workflows/build-linux.yaml exists, 74 lines, standard shared-helper template (matches hero_biz / hero_browser / hero_foundry).

Root cause

The workflow has on: push: tags: ["v*"] — never triggered because no v* tag has been pushed.

Caveat — depends on cluster A fix

The shared-helper template currently writes to package registry only (hero_biz#13 cluster A). So even after a tag is pushed, --from-ci hero_editor will fail until cluster A's Release-assets step is added.

Recommended fix

Wait for cluster A fix to land in scripts/build_lib.sh (or apply locally via PR).
Push v0.1.0 (or whatever's appropriate from buildenv.sh::VERSION).
Watch the build-linux run, verify Release + assets attach.
Wire --from-ci into hero_skills/tools/modules/services/service_editor.nu.

Effort

Quick win — 30 min once cluster A unblocks. 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: **none** - Forgejo Releases: **none** - Forgejo package registry: **empty (not checked)** - `.forgejo/workflows/build-linux.yaml` exists, 74 lines, standard shared-helper template (matches hero_biz / hero_browser / hero_foundry). ## Root cause The workflow has `on: push: tags: ["v*"]` — never triggered because no `v*` tag has been pushed. ## Caveat — depends on cluster A fix The shared-helper template currently writes to package registry only ([hero_biz#13 cluster A](https://forge.ourworld.tf/lhumina_code/hero_biz/issues/13)). So even after a tag is pushed, `--from-ci hero_editor` will fail until cluster A's Release-assets step is added. ## Recommended fix 1. Wait for cluster A fix to land in `scripts/build_lib.sh` (or apply locally via PR). 2. Push `v0.1.0` (or whatever's appropriate from `buildenv.sh::VERSION`). 3. Watch the build-linux run, verify Release + assets attach. 4. Wire `--from-ci` into `hero_skills/tools/modules/services/service_editor.nu`. ## Effort Quick win — 30 min once cluster A unblocks. Phase 2 implementation.