[ci] No release workflow exists — only `ci.yml` (test/lint); needs `build-linux.yaml` #4

New issue

Open

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

mik-tf commented

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

Owner

Audit context

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

State

.forgejo/workflows/: only ci.yml (71 lines, runs on push to development/main: fmt + check + clippy + test). No build-linux.yaml or release workflow.
Tags: none
Forgejo Releases: none
Forgejo package registry: empty

Root cause

There is no tag-triggered build/release workflow at all. The CI is test-only.

Distinct from cluster A

This needs a workflow file added, not just a fix to an existing one. Once added (and after cluster A fix lands so the shared helper does the right thing), the standard hero_biz template should drop in cleanly.

Recommended fix

Wait for cluster A fix in scripts/build_lib.sh (or use hero_proc / hero_router as a template — those have inline Release-asset logic and don't depend on cluster A).
Add .forgejo/workflows/build-linux.yaml modeled on hero_proc's.
Push v0.1.0.
Wire --from-ci into hero_skills/tools/modules/services/service_matrixchat.nu.

Effort

Medium — 1-2 h to add + validate the workflow. 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 - `.forgejo/workflows/`: only `ci.yml` (71 lines, runs on push to `development`/`main`: fmt + check + clippy + test). **No `build-linux.yaml` or release workflow.** - Tags: **none** - Forgejo Releases: **none** - Forgejo package registry: **empty** ## Root cause There is no tag-triggered build/release workflow at all. The CI is test-only. ## Distinct from cluster A This needs a workflow file added, not just a fix to an existing one. Once added (and after cluster A fix lands so the shared helper does the right thing), the standard hero_biz template should drop in cleanly. ## Recommended fix 1. Wait for cluster A fix in `scripts/build_lib.sh` (or use hero_proc / hero_router as a template — those have inline Release-asset logic and don't depend on cluster A). 2. Add `.forgejo/workflows/build-linux.yaml` modeled on hero_proc's. 3. Push `v0.1.0`. 4. Wire `--from-ci` into `hero_skills/tools/modules/services/service_matrixchat.nu`. ## Effort Medium — 1-2 h to add + validate the workflow. Phase 2 implementation.