Repository navigation
build: move Sysnode backend to patched Node 26 - #50
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Moves backend development, CI and the separately installed deployment runner to the patched Node 26.12.1 runtime. The runner enforces the patched Node 26 floor, puts its own interpreter first on staged child-process PATH, and requires the matching frontend/backend CI job names. Existing admission, schema, deployment and rollback checks remain intact.
Validation on Node 26.12.1: clean locked install with verified Node headers; real better-sqlite3 native compile/load (ABI 147, SQLite integrity
ok); 1,620 Jest tests across 79 suites; 12 codec tests; 10 real local Anvil recovery tests. Production dependency audit passes with zero high/critical findings. The current better-sqlite3 engine metadata stops at Node 25, but its actual native build and these tests pass on Node 26; no dependency version change is made.Deployment prerequisite: explicitly upgrade the host Node runtime, rebuild native dependencies, restart the existing PM2 apps under Node 26, and install the reviewed runner outside the live checkout. Preserve the database, environment and old runtime/dependencies for rollback. The old runner rejects the new CI job names before cutover; merging repository changes alone does not upgrade live processes. The coordinated migration steps are documented in
deploy/automation/README.md.