$ the-wire · showcase
AbortSignal.any() leak fixed, diagnostics_channel context unblocked
By RepoJournal · Filed · About Node.js · Composed from the cited sources · methodology
Node's async primitives got two correctness fixes today: composite abort signals no longer strand collected inner signals in gcPersistentSignals, and traceCallback() stops writing into a frozen default context.
lib: fix AbortSignal.any() nested composite leak nodejs/node
Nested composites copied their source WeakRefs into the new composite and reused them as unregister tokens, so when an inner composite was collected first its cleanup also unregistered the outer one, leaving an observed outer composite stuck in gcPersistentSignals. If you build abort signals by combining signals that were themselves combined, that leak is now closed.
diagnostics_channel: fix default callback context nodejs/node
traceCallback() defaulted to a frozen context but then wrote the callback's result or error onto it; the fix allocates a fresh context when undefined is passed and subscribers are present, matching traceSync() and tracePromise(), with the prototype set after allocation to avoid dictionary-mode properties. Subscribe to a diagnostics channel with a callback and return a value from it, and the old...
tools: bump the doc group in /tools/doc with 2 updates nodejs/node
Dependabot bumps the doc group in /tools/doc across two doc-kit packages, @doc-kit/generator-react from 0.4.0 to 0.4.2 and @node-core/doc-kit.
benchmark,tools: fix napi benchmarks on GHA nodejs/node
The GitHub Actions benchmark job never built the addons under benchmark/napi, and its --debug-node build made benchmark/common.js look for them in build/Debug; addons now build when the napi category runs and the build type is picked the way test/common does. NAPI benchmark numbers out of CI were measuring a missing addon.
deps: V8: cherry-pick 8d14d49c4040 nodejs/node
A cherry-pick onto V8 fixes compilation with GCC 16 on arm64, which matters if you build Node on that toolchain and architecture.
Add report for 2026-10-12 nodejs/reliability
The reliability desk published its report for 2026-10-12.
