Who contributed to Node.js on July 13, 2026?

5 developers shipped this update, including Archkon, aduh95, mcollina, MoLow, and rvagg.

What were the notable Node.js updates?

net: make TCP Server and Socket transferable across worker threads, test_runner: add `context.log()` and `test:log` event, and tools: add workflow to compare Nix changes.

@nodejs

The Node.js runtime — every backend team's CVE source of truth

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

NODE ADDS WORKER THREAD SOCKET TRANSFER AND LIVE TEST LOGGING

By RepoJournal · Filed 06:56 UTC on July 13, 2026 · About Node.js

5 people shipped this

aduh95 @aduh95 1 cited

mcollina @mcollina 1 cited

MoLow @MoLow 1 cited

rvagg @rvagg 1 cited

Archkon @Archkon

Node core shipped two significant runtime features overnight: TCP servers and sockets can now move across worker threads, and the test runner gained unbuffered live logging that executes in real time.

The worker thread socket transfer [1] lands on Unix platforms and solves a long-standing coordination problem for multithreaded applications. Pass a listening server or accepted socket through postMessage() and the receiving thread takes ownership without reimplementing the connection layer. Windows support blocked for now, but this unblocks serious architectural patterns for network-heavy services.

The test runner's new context.log() method [2] pairs with a matching test:log event that fires immediately as tests execute, not in buffered declaration order. This matters for reporters that want to render test trees live and for process-isolated tests where buffering creates attribution gaps. It's a targeted addition that solves the real problem of correlating logs to execution order.

Nix tooling got sharper [3] with new workflows that verify derivations build across platforms when nixpkgs pins change. The workflow comments diffs directly on PRs so you catch breaks early instead of discovering them after merge. This prevents the silent failures that plague dependency bumps in development tooling.

Snap packaging moved to official Node.js binaries [4] on supported architectures instead of rebuilding from source. amd64, arm64, and s390x now package upstream artifacts with embedded SHA-256 checksums, and the runtime handles Node 25's new libatomic.so.1 dependency inside the snap sandbox. armhf stays on source builds while armv7l gets the official package on Node 22+.

Action items

→ Review socket transfer patterns if you run multithreaded Node services on Unix nodejs/node [plan]
→ Update test reporters to consume test:log events for live output nodejs/node [plan]
→ Monitor snap builds for completeness as packaging shifts to upstream binaries nodejs/snap [monitor]

References

[1] net: make TCP Server and Socket transferable across worker threads ↗ nodejs/node
[2] test_runner: add `context.log()` and `test:log` event ↗ nodejs/node
[3] tools: add workflow to compare Nix changes ↗ nodejs/node
[4] fix: package official Node.js runtime artifacts ↗ nodejs/snap

Quick answers

What shipped in Node.js on July 13, 2026?: Node core shipped two significant runtime features overnight: TCP servers and sockets can now move across worker threads, and the test runner gained unbuffered live logging that executes in real time. In total, 17 commits and 14 pull requests landed.
Who contributed to Node.js on July 13, 2026?: 5 developers shipped this update, including Archkon, aduh95, mcollina, MoLow, and rvagg.
What were the notable Node.js updates?: net: make TCP Server and Socket transferable across worker threads, test_runner: add `context.log()` and `test:log` event, and tools: add workflow to compare Nix changes.

NGTCP2 UPGRADED, STREAM PERFORMANCE SURGES 27 PERCENT

Node core shipped a significant dependency bump and a performance optimization that measurably speeds up WHATWG stream reads across the stack.

javascript 16 shipped 1-min read

@nodejs 2 days ago

NODE.JS SNAP DROPS YARN, SHIPS TEMPORAL BY DEFAULT

Node.js snap builds are moving forward: Yarn support ends for pre-26 releases, Node 26 enters the CI pipeline, and Temporal becomes a standard feature across all new builds.

javascript 39 shipped 1-min read

@nodejs 3 days ago

NOTHING SHIPPED

All quiet across Node.js overnight.

javascript 1 shipped 1-min read

@nodejs 4 days ago

Node crypto backend split lands, HTTP/3 callbacks corrected

The core team shipped major refactoring across crypto and QUIC while npm 11.18.0 tightens registry handling, and undici's benchmarks catch up to got v15.

javascript 34 shipped 1-min read

— or follow the whole beat:

Elsewhere on the wire

Elixir & Phoenix about 6 hours ago

ELIXIR FIXES SPEC AND ARITY BUGS ACROSS CORE MODULES

Elixir core shipped three precision fixes overnight that tighten specs on IEx and EEx utilities, catching the kind of type mismatches that slip past dialyzer.

elixir 7 shipped 1-min read

Mobile platforms about 6 hours ago

FLUTTER CLEANS HOUSE ON ANALYSIS RULES WHILE SWIFT FIXES C-INTEROP CRASHES

Flutter is migrating away from deprecated strict analysis modes in favor of lint rules, while Swift patches critical crashes in bit-field accessors and C interoperability.

mobile 21 shipped 1-min read

@dotnet about 6 hours ago

ASPNETCORE VALIDATION GENERATOR FIXED, MSBUILD SYNCS ROSLYN AND NUGET

ASP.NET Core's validation source generator now correctly unwraps array types, closing a gap that could slip validation past your models.

dotnet 6 shipped 1-min read

@spring-projects about 6 hours ago

SPRING-AI FIXES CRITICAL TOOL CALLING BUG THAT BROKE OPENAI STRICT MODE

The `strict` parameter in OpenAI tool calling was silently failing across all Spring AI implementations because it was serialized in the wrong place in the payload.

java 8 shipped 1-min read