next.js 16.5.0-canary.29 released

The latest update, next.js 16.5.0-canary.29, introduces several critical enhancements for developers working with the framework. Among the core changes, developers will see the creation of a cache directory before persisting the Chrome DevTools workspace UUID, tracked under issue #100802.

This release also mandates an upgrade of React from `ab0d927f-20261020` to `dc9aed36-20261027` (#100791). Furthermore, a fix for compressed HTTP responses when using a test proxy has been implemented in test mode (#100805), alongside a dependency bump for sharp to version 0.35.5 (#997).

Turbopack receives notable tooling improvements, including the ability to auto-detect pnpm GVS and configure an extra root for it (#99758). Persistence capabilities are extended, allowing storage cache to persist within Docker environments (#100790) and fully static PPR payloads to persist in the filesystem cache (#100759).

Other foundational changes include stamping FileSystemCache revalidations and entries with the monotonic clock (#100357). In terms of example additions, the eve example has been incorporated (#100758).

Miscellaneous updates refine internal mechanisms, such as making turbo-bitset block storage pluggable (#100779) and establishing fixed encoding for 'id' types (#100764). Several backend and testing adjustments were made, including resolving task priority when creating child contexts in turbo-tasks-backend (#100767) and adding a server-only leak pass to next-bundle-optimizer (#100330).

Earlier canary builds provided significant groundwork; for instance, next.js 16.5.0-canary.28 addressed draft mode rendering with Cache Components (#100728) and ensured complete HTML document rendering after MPA Server Actions (#100740).

In the canary.27 release, the inline Flight script now builds from React's strings rather than re-encoding them (#100142), and a fix was applied for the dist dir lockfile on filesystems lacking robust lockfile implementations (like NFS) (#100684).

The release history shows ongoing refinement in Turbopack, with canary.26 seeing the bump of the trace format header to TRACEv1 (#99781) and passing staged fallback params directly to adapter renders (#100456).