Skip to content

Move the portable runtime from the Node 24.18.1 hold to 24.22.0, which contains the #135 fix #362

Closed

Description

@shariqh

The portable runtime (Setup's MCP server, hooks and watcher) is pinned to Node 24.18.1 under the #135 compatibility hold. Node 24.19.0's node::ObjectWrap headers added cleanup hooks without the matching runtime fix (nodejs/node#65446). As a result, a better-sqlite3 built against them aborts during allocation-driven GC. The doc says to revisit the pin "when a corrected Node 24 release passes the same native GC and packaged MCP/watcher checks".

Node 24.22.0 looks like that release. This came out of the Electron 43.8.1 bump (#360):

Proposal: move the portable runtime to Node 24.22.0.

  • Update the node distributions (archives, URLs, SHA-256 from nodejs.org's SHASUMS256.txt) in release/macos-inputs.json, release/linux-inputs.json and release/windows-inputs.json, and update their tests.
  • Staging already rebuilds better-sqlite3 against the distribution's own headers, then runs scripts/runtime-sqlite-check.mjs and the runtime MCP probe. Those checks, run natively on each architecture (including Intel), are the proof. A failure refuses publication, so a wrong guess fails closed.
  • Rewrite the hold section of docs/macos-release.md (linked from the Linux and Windows docs) to record why the hold ended and what proved it.

Why bother: the runtime that runs every Setup user's MCP server and hooks would get the Node 24 fixes since 24.18.1, and the app and runtime would be on the same Node again. Exposure is low today: the stdio server makes no network calls, and the viewer runs inside Electron's Node 24.22.0.

Not for v1.7.0.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions