Skip to content

fix(installer): keep the shared harness on latest (0.1.8) - #12

Merged
brunoazoulay merged 2 commits into
mainfrom
fix/harness-refresh
Oct 12, 2026
Merged

brunoazoulay merged 2 commits into
mainfrom
fix/harness-refresh

Conversation

@brunoazoulay

Copy link
Copy Markdown
Collaborator

Summary

  • Installer refreshes the shared @fusengine/harness to latest on every run (bun update, fallback bun install, fail-open) — new services/harness-vendor.ts + interface + 6 tests
  • hook.sh wrapper comment (21 plugins + plugin-runtime, all identical) no longer claims auto-upgrade; names the upgrade path
  • Installation docs updated
  • Release 0.1.8: PATCH bump of the 21 touched plugins, mirrored in marketplace.json; suite 0.1.7 -> 0.1.8

Test plan

  • bunx tsc --noEmit clean, bun test 285 pass / 0 fail
  • tests/*.sh 7/7
  • verify.sh: only the 6 known pre-existing FAILs
  • 21 hook.sh copies byte-identical to plugin-runtime/hook.sh
  • CI green

Breaking changes

None

- installer refreshes @fusengine/harness on every run (bun update, falling
  back to bun install) via new services/harness-vendor.ts, fail-open
- hook.sh wrappers (21 plugins + plugin-runtime): comment no longer claims
  auto-upgrade and names the upgrade path (re-run the installer)
- 6 tests for harness vendoring; installation docs updated
@brunoazoulay
brunoazoulay merged commit 58a24ba into main Oct 12, 2026
3 checks passed
@brunoazoulay
brunoazoulay deleted the fix/harness-refresh branch October 12, 2026 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant