Summary
There is no CI gate validating the Brev Launchable install path. Community users install via:
curl -fsSL .../launch-plugin.sh | PLUGIN_REF=main bash
PLUGIN_REF=main means Launchable users always get main HEAD, not a tagged release. Breaking changes on main reach Brev Launchable users before any release validation.
Bugs it would have caught
The entire Brev Launchable outage (Apr 20–25) — Ryan Lee reported in #nemoclaw-community Slack that his automation broke across 3–4 fresh Brev instances. He was on v0.0.24-16-g9fbfbaca (main HEAD, 16 commits past the v0.0.24 tag) which included:
If a nightly smoke test ran launch-plugin.sh with PLUGIN_REF=main, the dead gateway and empty token would have been caught immediately.
Current state
e2e-brev.yaml exists but provisions a bare Brev instance and installs from source — it does NOT test the Launchable install path (launch-plugin.sh).- No script or workflow validates the Launchable flow.
Proposed approach
New workflow (launchable-smoke.yaml) or nightly job. Minimal test:
- Run
launch-plugin.sh with PLUGIN_REF=main (or latest tag)
- Verify NemoClaw is installed and on PATH
- Verify the sandbox gateway started (health check)
- Verify
openclaw tui can connect (or basic inference works)
- Clean up
Constraints
- Requires
BREV_API_TOKEN to provision a Launchable instance, OR investigation into whether launch-plugin.sh can run on a standard ubuntu-latest runner
- If it requires a real Brev instance, this would be a
workflow_dispatch + nightly schedule (like e2e-brev.yaml), not a PR gate
Effort: Medium-High — new workflow, needs Brev integration or adaptation of install script.
Related issues
Summary
There is no CI gate validating the Brev Launchable install path. Community users install via:
curl -fsSL .../launch-plugin.sh | PLUGIN_REF=main bashPLUGIN_REF=mainmeans Launchable users always get main HEAD, not a tagged release. Breaking changes on main reach Brev Launchable users before any release validation.Bugs it would have caught
The entire Brev Launchable outage (Apr 20–25) — Ryan Lee reported in #nemoclaw-community Slack that his automation broke across 3–4 fresh Brev instances. He was on
v0.0.24-16-g9fbfbaca(main HEAD, 16 commits past the v0.0.24 tag) which included:"token": ""in openclaw.json)If a nightly smoke test ran
launch-plugin.shwithPLUGIN_REF=main, the dead gateway and empty token would have been caught immediately.Current state
e2e-brev.yamlexists but provisions a bare Brev instance and installs from source — it does NOT test the Launchable install path (launch-plugin.sh).Proposed approach
New workflow (
launchable-smoke.yaml) or nightly job. Minimal test:launch-plugin.shwithPLUGIN_REF=main(or latest tag)openclaw tuican connect (or basic inference works)Constraints
BREV_API_TOKENto provision a Launchable instance, OR investigation into whetherlaunch-plugin.shcan run on a standardubuntu-latestrunnerworkflow_dispatch+ nightly schedule (likee2e-brev.yaml), not a PR gateEffort: Medium-High — new workflow, needs Brev integration or adaptation of install script.
Related issues