[ci] No tag ever pushed + WASM workflow publishes to pkg registry only — --from-ci blind #203

New issue

Open

opened 2026-05-04 01:45:00 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-04 01:45:00 +00:00

Owner

Phase 3 scope (Hero CI roadmap, hero_demo#54)

Two compounding gaps:

Gap 1 — Workflow has never run

build-release.yaml exists (137 lines, tag-triggered, builds WASM islands via wasm-pack and packages to hero_archipelagos-wasm.tar.gz) but:

No v* tag has ever been pushed
No releases
No package-registry entries

Same shape as binary cluster D (hero_editor#5, hero_slides#42) — workflow exists but trigger never fires.

Gap 2 — Workflow publishes to wrong place

When the workflow does run, it publishes only to package registry (/api/packages/.../generic/hero_archipelagos/${VERSION}/). No Forgejo Release creation, no Release-asset upload. Same root cause as cluster A binary repos (hero_biz#13 and siblings) and hero_os#125 WASM.

Gap 3 — No consumer path

There is no service_archipelagos.nu deploy module. Hero's archipelagos islands are consumed by hero_os which serves them statically from ~/hero/share/hero_os/islands/. The current install flow is a local make build + copy. No --from-ci consumer exists for the WASM tarball.

Recommended fix order

Wait for cluster A workflow pattern to land in hero_browser/books/foundry (Phase 2). Pattern then transfers cleanly here.
Add Release-asset upload to build-release.yaml (single tarball asset, not multiple binaries — same shape as hero_os).
Tag v0.1.0 to trigger the first run; validate Release + asset on heroci.
Wire consumer (depends on whether islands install via service_os install path or a new service_archipelagos.nu — design decision).

Effort

~2-3 h once cluster A pattern stabilizes. Tag-and-validate dominates because the workflow itself has never run — first push will surface any latent build issues.

Tracker

Hero CI roadmap Phase 3, hero_demo#54.

## Phase 3 scope (Hero CI roadmap, [hero_demo#54](https://forge.ourworld.tf/lhumina_code/hero_demo/issues/54)) Two compounding gaps: ### Gap 1 — Workflow has never run `build-release.yaml` exists (137 lines, tag-triggered, builds WASM islands via `wasm-pack` and packages to `hero_archipelagos-wasm.tar.gz`) but: - **No `v*` tag has ever been pushed** - **No releases** - **No package-registry entries** Same shape as binary cluster D ([hero_editor#5](https://forge.ourworld.tf/lhumina_code/hero_editor/issues/5), [hero_slides#42](https://forge.ourworld.tf/lhumina_code/hero_slides/issues/42)) — workflow exists but trigger never fires. ### Gap 2 — Workflow publishes to wrong place When the workflow does run, it publishes only to package registry (`/api/packages/.../generic/hero_archipelagos/${VERSION}/`). No Forgejo Release creation, no Release-asset upload. Same root cause as cluster A binary repos ([hero_biz#13](https://forge.ourworld.tf/lhumina_code/hero_biz/issues/13) and siblings) and [hero_os#125](https://forge.ourworld.tf/lhumina_code/hero_os/issues/125) WASM. ### Gap 3 — No consumer path There is no `service_archipelagos.nu` deploy module. Hero's archipelagos islands are consumed by hero_os which serves them statically from `~/hero/share/hero_os/islands/`. The current install flow is a local `make build` + copy. No `--from-ci` consumer exists for the WASM tarball. ## Recommended fix order 1. **Wait for cluster A workflow pattern to land** in hero_browser/books/foundry (Phase 2). Pattern then transfers cleanly here. 2. **Add Release-asset upload** to `build-release.yaml` (single tarball asset, not multiple binaries — same shape as hero_os). 3. **Tag `v0.1.0`** to trigger the first run; validate Release + asset on heroci. 4. **Wire consumer** (depends on whether islands install via `service_os` install path or a new `service_archipelagos.nu` — design decision). ## Effort ~2-3 h once cluster A pattern stabilizes. Tag-and-validate dominates because the workflow itself has never run — first push will surface any latent build issues. ## Tracker Hero CI roadmap Phase 3, [hero_demo#54](https://forge.ourworld.tf/lhumina_code/hero_demo/issues/54).