Changelog

nodejs/node · · 6 commits

Crypto hardens, fs watch race fixed

Node.js patches a crypto allocation failure path and fixes recursive fs watch ENOENT races; docs and tooling also updated.

Crypto now fails gracefully on cipher context allocation errors (Herrtianf47f941)

WebCrypto AES and ChaCha20-Poly1305 now return a failure status if cipher context allocation fails instead of hard-checking and aborting. The lower-level cipher init path also surfaces a proper ERR_CRYPTO_OPERATION_FAILED error, making these OOM-style failures handleable rather than fatal.

Recursive fs watch ignores deleted directories during scan (trivikr4d7996f)

The non-native recursive watcher now suppresses ENOENT when a directory disappears between discovery and scan, avoiding an unhandled watcher error in a real deletion race. A regression test was added to lock in the behavior.

Other misc changes

  • zlib updater script fixed to be more portable/robust (aduh958346181)
  • Node.js 25 marked End-of-Life in the changelog index (aduh95b345a17)
  • async-hooks abort tests updated to accept platform-specific abort signals (trivikr3dfd512)
  • http2 docs typo fix: “used to sent” → “used to send” (watildeaf2e68b)