You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Move the portable runtime from the Node 24.18.1 hold to 24.22.0, which contains the #135 fix #362
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):
The packaged Electron 43.8.1 (embedded Node 24.22.0, ABI 148) passed the allocation-driven SQLite check in every packaging job: Linux x64/arm64 folders, AppImage and DEB, both macOS thin apps including native Intel, and the Windows native folder and MSI folders.
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.
Activity
Update Electron to 43.8.3 for its security fixes (#360)
Re-pin the portable runtime to the Node 24.22.1 security release (#362 …
Give the Intel SQLite check timing the measured range (#362 review)
Time each Intel SQLite check from its own runs (#362 review)
State the Intel SQLite check timing as the recent range (#362 review)
Move the portable runtime from the Node 24.18.1 hold to 24.22.1 (#362) (