Repository navigation
Conversation
frgfm
changed the title
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.
Summary
Node.js 22.23.4 is the patched Node 22 release for the 21 October 2026 security issues, including compromised eMudhra certificate trust paths (advisory). The viewer stays on Node 22:
viewer/.nvmrcpins local development, CI reads that file, and the setup guides name the patched version.Test plan
npm ci— passed on Node 22.23.4 with npm 10.9.9; npm reported 18 dependency audit findings (3 moderate, 14 high, 1 critical). No dependencies or lockfile changed.npm run lint— passed.npm run format:check— passed.npm test -- --maxWorkers=2— passed (48 tests).npm run build— passed with a temporary two-worker cap; Next.js emitted a file-tracing warning fromlib/paths.ts.