Lately I've found myself repeating the same explanations to different people about how Node.js and V8 build/test/stay in sync with each other. To reduce the parroting, here's a blog post about the workflows, challenges I see, and some hands-on tips

Tomorrow, we’re releasing the full technical walkthrough for CVE-2026-5865, a chrome v8 0-day found by our AI security agent "Vega". More Linux kernel and Chrome 0-day writeups are coming later this month. Stay tuned, and follow our bug list for updates:

Deno v2.7.13 is out! The big one: `node:http` has been completely rewritten bringing major compatibility and performance improvements for Node.js HTTP workloads. Also in this release: - Proper NAPI V8 handle scopes and callback scopes - Extensive node:http2 fixes - node:tls improvements: STARTTLS auto-start, validation, JS stream and pipe support - Lower memory usage for `Deno.Command.output()` - Restored glibc < 2.27 compat for Linux builds

We're cooking... Deno v2.7.5 is out! - `fs.cp` moved to Rust for 2x performance boost - `deno install` handles peer deps faster - CPU profiling with --cpu-prof flags - `deno doc` now supports npm packages - Node compat fixes: ECDH, DiffieHellman, PQC keys, worker_threads, v8 APIs 38 bug fixes total, more here: