179 wires and counting

$ follow Node.js

Keep up with Node.js in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-11-07
stories 26

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Stale OpenSSL errors cleared, npm 12.2.2 lands in node

By RepoJournal · Filed · About Node.js · Composed from the cited sources · methodology

Node's crypto layer now clears OpenSSL's thread-local error queue at the API boundaries, closing a path where one operation's leftover error surfaced in the next, and npm advanced to 12.2.2 in the same day's batch.

crypto: prevent stale OpenSSL errors nodejs/node

by mcollina

Several crypto operations could return a normal result or a Node.js error while leaving entries in OpenSSL's thread-local error queue, which a later operation would then consume; errors are now cleared at the affected API boundaries and before TLS I/O and private-key parsing, with new regression coverage for key comparison, SPKAC methods, and EC JWK import. If you check OpenSSL error state afte...

deps: upgrade npm to 12.2.2 nodejs/node

by npm-cli-bot

npm moves from 12.2.0 through 12.2.2 inside node, per the vendored release notes, bundling the three 12.2.x releases into one dependency bump. Anyone relying on npm behavior pinned to the prior vendored version gets the 12.2.x feature set on the next node build.

build: sync Torque outputs with V8 nodejs/node

by Filip Skokan

V8 15.2 dropped the per-source .inc files and replaced bit-fields.h with bit-field-asserts.cc, so the Torque build outputs are resynced to match. The change is build plumbing for the V8 bump and matters to anyone building node from source against the new V8.

stream: fix pipeTo assert when writer is released during microtask nodejs/node

by colinaaa

The deferred write from an earlier change wraps the write in queueMicrotask(), leaving a window where pipeTo can shut down and release the writer before the microtask runs, tripping ERR_INTERNAL_ASSERTION on an undefined writer stream. The fix checks for that released-writer state inside the microtask before writing, so the race no longer aborts the process.

meta: build docs for PRs whose base has no main run nodejs/doc-kit

by ovflowd

Also landing: doc-kit's "Generate and Compare Docs" no longer fails on PRs whose base commit has no main run (the stacked PR case), and a follow-up restricts the base lookup to push runs so a pull_request run's missing commit artifact is no longer fetched.

Merge pull request #1763 from vmoroz/PR/fix-windows-addon-pgo nodejs/node-addon-api

by Vladimir Morozov

Smaller items: node-core-utils keeps llvm-libc src/string through V8 updates, node's security pre-alert template was corrected, and Windows CI for node-addon-api disables inherited PGO.

Quick answers

What shipped in Node.js on November 7, 2026?
Node's crypto layer now clears OpenSSL's thread-local error queue at the API boundaries, closing a path where one operation's leftover error surfaced in the next, and npm advanced to 12.2.2 in the same day's batch. In total, 13 commits and 13 pull requests landed.
Who contributed to Node.js on November 7, 2026?
8 developers shipped this update, including Claudio Wunder, Joyee Cheung, Antoine du Hamel, npm-cli-bot, Filip Skokan, mcollina, colinaaa, and Vladimir Morozov.
What were the notable Node.js updates?
crypto: prevent stale OpenSSL errors, deps: upgrade npm to 12.2.2, and build: sync Torque outputs with V8.