Repository navigation
Upgrade Electron to a Node 24 runtime - #39
Merged
Merged
Conversation
qduc
marked this pull request as ready for review
November 8, 2026 10:10
This was referenced Nov 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ChatForge's desktop build uses Electron 39, which embeds Node 22, while the shared agent harness targets Node 24. Upgrade Electron to 43 and refresh the builder and SQLite binding needed for its native ABI. Linux builds use Clang 19 for the Electron headers.
The packaged backend also needs
@qduc/web-fetchandp-limit: without them startup fails and the tool concurrency limit silently falls back to unbounded execution. Pin the backend CI runner to Ubuntu 24.04 because Playwright 1.60 rejects the new Ubuntu 26.04ubuntu-latestimage before tests run.Validation:
/health. The fixture used a placeholder frontend.