Hivemind turns agent traces into skills and shares with your team

Why

PR #206 (fix(deps): build tree-sitter from source on linux-arm64 / Node >=22) introduced a postinstall heal that turned a hard install failure on Node 24 into a silent WARNING: tree-sitter bindings still unavailable + exit 0. Because ci.yaml runs only on Node 22 — where the linux-x64 prebuild ABI matches and the heal short-circuits cleanly — the regression was invisible at PR time and only surfaced post-merge in the Release workflow (run 26430516153), which was pinned to Node 24.12. That broke v0.7.55 mid-release.

The unblock is in #207 (pin release.yaml to Node 22). This PR closes the detection gap so the next regression of this class fails on the PR instead of on main.

What

Two pieces:

1. New cross-node-install job in ci.yaml

• Matrix [22, 24] — every Node major the engines field (>=22.0.0) admits
• Runs npm install && npm run build only — the bug class is install/build-time, not runtime, so running the full test suite on every matrix slot doubles CI cost for no extra signal
• continue-on-error: true — keeps PRs unblocked while the known upstream [email protected] + Node 24 incompatibility is being resolved. Signal is still visible in the PR checks table as yellow/red. Flip to false once Node 24 install is healthy.

2. Opt-in strict mode for scripts/ensure-tree-sitter.mjs

• HIVEMIND_STRICT_POSTINSTALL=1 (set by this repo's own CI workflows) turns WARNING: bindings still unavailable into exit 1 instead of exit 0
• Downstream consumers of @deeplake/hivemind never see this flag, so their install stays non-fatal as before
• Strict path turns a buried tsc: Cannot find module 'tree-sitter' 30 seconds later into an immediate, labeled install-time failure

How this would have caught #206 → #207

PR #206 in the new canary's Node 24 slot:

1. npm install runs the postinstall heal
2. Heal fails to make bindings loadable → WARNING + HIVEMIND_STRICT_POSTINSTALL=1 → exit 1
3. Job fails at the install step with a clear [ensure-tree-sitter] WARNING: ... (strict mode — failing this install)
4. PR check shows red Node 24 row; reviewer / author sees the regression before merging

Even with strict mode off, the next step (npm run build) would have failed tsc with Cannot find module 'tree-sitter' — same failure as the Release run, but on the PR.

Test plan

• [ ] Node 22 canary slot passes (existing prebuild ABI match, heal no-op)
• [ ] Node 24 canary slot fails RED but doesn't block PR merge (continue-on-error)
• [ ] Existing test (Node 22) and duplication jobs unaffected
• [ ] Locally verified: strict-mode logic in ensure-tree-sitter.mjs exits 1 only when both HIVEMIND_STRICT_POSTINSTALL=1 AND bindingsLoad() === false; healthy bindings still exit 0

Follow-up (not in this PR)

• Align release.yaml and publish-smoke-test.yaml env to also set HIVEMIND_STRICT_POSTINSTALL=1 once #207 lands
• Add Node 26 to matrix when it ships
• Once [email protected] vs Node 24 is resolved upstream (or we upgrade tree-sitter), flip continue-on-error to false to make Node 24 install a hard gate

Summary by CodeRabbit

• Chores
  • Enhanced CI pipeline to test builds across multiple Node.js versions (22, 24) with stricter validation rules, ensuring improved build reliability and compatibility.