lhumina_code/home
0
0
Fork 0
Code Issues 63 Pull requests Projects Releases Packages Wiki Activity Actions

Sandbox: publish stable releases from main (status and per-repo follow-ups) #269

New issue
Open
opened 2026-06-07 22:36:03 +00:00 by mik-tf · 2 comments
mik-tf commented 2026-06-07 22:36:03 +00:00
Owner
Copy link

Single status note for moving the tester sandbox onto stable main builds.

Rule: every sandbox repo publishes its latest release from main and a separate latest-dev prerelease from development. The tester install pulls each repo's latest, so latest must come from main.

Background: recently several repos published latest from development, so a fresh install pulled unfinished development builds that disagreed on internal APIs and failed setup. Root cause and fix are in #268 (now closed). A fresh test install after the fix reached the working cockpit login page.

Done this session:

  • lab (hero_skills), hero_proc, hero_router now publish latest from main (lab and hero_proc were the actual blockers).
  • hero_proxy and hero_cockpit already published latest from main.
  • The deployer reliability fix (wait for the new VM network route, push the login-gate provider deterministically, resilient service restarts) is merged to main and verified live.
  • The publish rule was applied to the enabled component repos.

Sandbox components (the 11 the deployer enables) and whether main builds the released binary:

  • Builds on main: hero_proxy, hero_router, hero_proc, hero_cockpit, hero_db, hero_slides, hero_whiteboard, hero_planner, hero_kimi, hero_orchestrator.
  • Does not build on main: hero_voice. Its source needs updating to the stricter openrpc client macro and a changed secret API. Handed to its owner in lhumina_code/hero_voice#37. The deployed voice release still works in the sandbox, so onboarding is not blocked.

Not in the enabled sandbox set (not blocking, noted for later): hero_books, hero_agent, hero_osis, hero_biz, hero_collab. Their main branches may need a development to main catch-up before their latest is a main build.

Net: the sandbox runs on stable main builds for everything except voice, which keeps working on its last released build while its owner updates the source.

Signed-by: mik-tf mik-tf@noreply.invalid

Single status note for moving the tester sandbox onto stable main builds. Rule: every sandbox repo publishes its `latest` release from main and a separate `latest-dev` prerelease from development. The tester install pulls each repo's `latest`, so `latest` must come from main. Background: recently several repos published `latest` from development, so a fresh install pulled unfinished development builds that disagreed on internal APIs and failed setup. Root cause and fix are in https://forge.ourworld.tf/lhumina_code/home/issues/268 (now closed). A fresh test install after the fix reached the working cockpit login page. Done this session: - lab (hero_skills), hero_proc, hero_router now publish `latest` from main (lab and hero_proc were the actual blockers). - hero_proxy and hero_cockpit already published `latest` from main. - The deployer reliability fix (wait for the new VM network route, push the login-gate provider deterministically, resilient service restarts) is merged to main and verified live. - The publish rule was applied to the enabled component repos. Sandbox components (the 11 the deployer enables) and whether main builds the released binary: - Builds on main: hero_proxy, hero_router, hero_proc, hero_cockpit, hero_db, hero_slides, hero_whiteboard, hero_planner, hero_kimi, hero_orchestrator. - Does not build on main: hero_voice. Its source needs updating to the stricter openrpc client macro and a changed secret API. Handed to its owner in https://forge.ourworld.tf/lhumina_code/hero_voice/issues/37. The deployed voice release still works in the sandbox, so onboarding is not blocked. Not in the enabled sandbox set (not blocking, noted for later): hero_books, hero_agent, hero_osis, hero_biz, hero_collab. Their main branches may need a development to main catch-up before their `latest` is a main build. Net: the sandbox runs on stable main builds for everything except voice, which keeps working on its last released build while its owner updates the source. Signed-by: mik-tf <mik-tf@noreply.invalid>
mik-tf commented 2026-06-07 23:26:20 +00:00
Author
Owner
Copy link

Update on voice: it now builds on main. The cause was an erroneous merge of development into main (confirmed with Scott) that left conflict markers across several files. Main was reset to the last building commit before that merge with the VAD work cherry-picked on top, so voice now joins the same main flow as the rest of the sandbox and is rebuilding its release. The in-progress openrpc migration stays on development for the owner to land later (tracked in lhumina_code/hero_voice#37).

Net: all 11 sandbox components now build and publish their release from main.

Signed-by: mik-tf mik-tf@noreply.invalid

Update on voice: it now builds on main. The cause was an erroneous merge of development into main (confirmed with Scott) that left conflict markers across several files. Main was reset to the last building commit before that merge with the VAD work cherry-picked on top, so voice now joins the same main flow as the rest of the sandbox and is rebuilding its release. The in-progress openrpc migration stays on development for the owner to land later (tracked in https://forge.ourworld.tf/lhumina_code/hero_voice/issues/37). Net: all 11 sandbox components now build and publish their release from main. Signed-by: mik-tf <mik-tf@noreply.invalid>
mik-tf commented 2026-06-08 00:00:38 +00:00
Author
Owner
Copy link

Voice is now green on main. The gnu build succeeded and republished the voice release from main (hero_voice_server and hero_voice_admin built from the corrected main). The gnu workflow had also been missing the git credential step for private dependencies, which is now added (and the same gap was fixed in three other gnu workflows: hero_embedder_provider, hero_lib_rhai, hero_voice_provider).

Status: all 11 sandbox components now build and publish their release from main.

Signed-by: mik-tf mik-tf@noreply.invalid

Voice is now green on main. The gnu build succeeded and republished the voice release from main (hero_voice_server and hero_voice_admin built from the corrected main). The gnu workflow had also been missing the git credential step for private dependencies, which is now added (and the same gap was fixed in three other gnu workflows: hero_embedder_provider, hero_lib_rhai, hero_voice_provider). Status: all 11 sandbox components now build and publish their release from main. Signed-by: mik-tf <mik-tf@noreply.invalid>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
development
main
No results found.
Labels
Clear labels   
meeting-notes

Meeting notes and follow-ups

  
meeting-transcript

Raw meeting transcript; AI drafts the report

No labels
meeting-notes
meeting-transcript
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/home#269
No description provided.