[dependabot]

Bumps the minor-and-patch group with 2 updates in the / directory: @next/third-parties and @opennextjs/cloudflare.

Updates @next/third-parties from 16.4.2 to 16.4.3

Release notes

Sourced from @​next/third-parties's releases.

v16.4.3

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• [lts-active] Fix extensionless Google font URLs in both bundlers (#100277)
• [lts-active] Don't load the app-page runtime in proxy.ts (#100423)
• [lts-active] Revert "Turbopack: loader change invalidation (#95732)" (#100438)
• [lts-active][cd] Gate release bot credentials behind GitHub environments (#100123)
• [lts-active] test: Pin react-virtualized (#100545)
• [lts-active][cd] Move release un-draft to a follow-up job in bot-autonomous (#100572)
• [lts-active] Keep OpenTelemetry request traces together (#100349, #100294, #100324, #100350, #100552, #100583) (#100542)
• [lts-active] Avoid loading standalone React in server bootstrap (#100610)

Credits

Huge thanks to @​mischnic, @​lukesandberg, @​acdlite, @​eps1lon, and @​sokra for helping!

Commits

• 29bbeab v16.4.3
• See full diff in compare view

Updates @opennextjs/cloudflare from 1.20.13 to 1.20.14

Release notes

Sourced from @​opennextjs/cloudflare's releases.

@​opennextjs/cloudflare@​1.20.14

Patch Changes

• #1470 7460f53 Thanks @​vicb! - chore: bump @opennextjs/aws to 4.1.13

  See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v4.1.13

  • Export the code patch test utilities as @opennextjs/aws/build/patch/testUtils.js

• #1466 3e50371 Thanks @​NathanDrake2406! - fix: reuse cached manifests to reduce CPU and memory usage

  The inlined manifests were re-created on every load, so apps with large manifests (e.g. the prerender manifest) spent CPU time building and garbage collecting the same objects and kept multiple copies in memory.

• #1470 7460f53 Thanks @​vicb! - fix: scope the module-loading signal to the request on Next 16

  Starting with Next.js 16, the module-loading patch silently stopped matching the changed CacheSignal constructor. Concurrent requests could then fail with Cannot perform I/O on behalf of a different request and return truncated responses. Scope the signal to each request again so concurrent renders complete.

Changelog

Sourced from @​opennextjs/cloudflare's changelog.

1.20.14

Patch Changes

• #1470 7460f53 Thanks @​vicb! - chore: bump @opennextjs/aws to 4.1.13

  See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v4.1.13

  • Export the code patch test utilities as @opennextjs/aws/build/patch/testUtils.js

• #1466 3e50371 Thanks @​NathanDrake2406! - fix: reuse cached manifests to reduce CPU and memory usage

  The inlined manifests were re-created on every load, so apps with large manifests (e.g. the prerender manifest) spent CPU time building and garbage collecting the same objects and kept multiple copies in memory.

• #1470 7460f53 Thanks @​vicb! - fix: scope the module-loading signal to the request on Next 16

  Starting with Next.js 16, the module-loading patch silently stopped matching the changed CacheSignal constructor. Concurrent requests could then fail with Cannot perform I/O on behalf of a different request and return truncated responses. Scope the signal to each request again so concurrent renders complete.

Commits

• 16e9f1e Version Packages (#1469)
• 7460f53 fix: scope the module-loading signal to the request on Next 16 (#1470)
• 3e50371 fix: reuse cached manifests to reduce CPU and memory usage (#1466)
• See full diff in compare view

[github-actions]

Preview deployment

Status	URL
Skipped	-

Commit: 6fdd509
Updated: 2026-11-02T06:24:26.757Z

Reason: Dependabot-triggered workflows do not have access to repository secrets in this workflow.

If you want a preview deployment, please ask a maintainer to run this from a branch within the main repository.