Skip to main content

Deno 2.9.6

Release Date: August 27, 2026

Deno 2.9.6 dropped on August 27, 2026. It is a maintenance release in the 2.9 line, packing a handful of new features, a large set of runtime fixes, and improvements to the Deno Desktop runtime. If you are on the preceding 2.9.5, this is a routine, low-risk upgrade.

New Features

The compressible response list now recognizes the text/x-component content type, which matters for React Server Component payloads. The Deno Desktop runtime adds a clipboard API, and desktop menu items now support checked, icon, and tooltip properties, rounding out the desktop menu story for building local-first apps.

Runtime and HTTP Fixes

Several fetch and HTTP fixes landed in this release. Fetch now enforces permissions for proxy transports, and transport errors are only retried on pooled connections. The default HTTP/2 SETTINGS_MAX_HEADER_LIST_SIZE is raised to 256 KB to accommodate larger headers, and the request body of an HTTP response stays readable even after the response is sent. Invalid async responses are now routed to onError instead of being mishandled.

Node and NAPI Compatibility

The Node and NAPI layers get a substantial batch of stabilization work. NAPI finalizers are no longer invoked twice at teardown, OS errors and paths are surfaced when an addon fails to load, and the event loop wakes at the next uv_timer deadline. DNS lookups accept string ports, TLS client sessions are only resumed when requested, and a proxy path duplication issue in perf_hooks detail URLs is fixed.

Desktop Improvements

On the desktop side, Vite-based HMR dev servers now run inside the desktop runtime, macOS bundle signatures are kept valid unless an update is applied, and deno.json version and license metadata is propagated into packaged installers. The JS thread is never blocked by the error-report dialog, and dots are preserved in app names when resolving the runtime library.

Deno 2.9.6 is available now through deno upgrade or the usual install channels. As a patch release it changes no major APIs, so existing scripts should continue running unchanged.

What is New?

By continuing to use the site, you agree to the use of cookies.