Node.js v25 scheduled for 2025‑10‑15 — semver‑major release imminent
Key update
The Node.js project has scheduled a semver‑major v25 release for 2025‑10‑15; commits landed through 2025‑09‑15 are included in the release window. (github.com)
Why it matters
A semver major from Node.js is operationally significant: it can introduce breaking API changes, runtime behavior differences, and new V8/npm/tooling combinations that affect production services, CI matrices, Docker images, and native addons. Teams should treat this as an immediate compatibility checkpoint — run your full test matrix against Node 25 builds, rebuild and smoke‑test any native modules or N‑API bindings, confirm your CI/CD images and pinned engine ranges, and prepare a canary deployment path so you can detect regressions quickly after the release. If you maintain tooling or libraries, expect downstream consumers to test and report issues within days, so prioritize reproducible builds and automated test coverage for platform‑specific code paths.
Source
Read Next
Azure Functions Proxies: community support ends 2025‑09‑30 — migrate off Proxies now
September 29, 2025Azure announced Azure Functions Proxies will be unsupported after 2025‑09‑30; teams still using Proxies must inventory and migrate to a supported API surface (APIM, Front Door, or a lightweight reverse proxy) immediately.
NodeShield: runtime SBOM enforcement (CBOM) for Node.js limits supply‑chain attacks with negligible overhead
September 28, 2025A new paper introduces NodeShield, a runtime enforcement system that uses SBOMs extended with per‑dependency capabilities (CBOM) to prevent supply‑chain abuses in Node.js with ~98% effectiveness and <1ms overhead.
Wasm 3.0 completed — Memory64, multi‑memory, GC, and SpecTec are now official
September 27, 2025WebAssembly 3.0 finalised (Sep 17, 2025): 64‑bit address space, multiple memories, host garbage collection, JS string builtins and SpecTec for a verifiable spec — a step change for compiling high‑level languages and server‑side Wasm.