Skip to content

chore(deps): bump the next group with 3 updates - #502

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/next-94fa6c6b8b
Open

dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/next-94fa6c6b8b

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 17, 2026

Copy link
Copy Markdown
Contributor

Bumps the next group with 3 updates: @opennextjs/cloudflare, next and eslint-config-next.

Updates @opennextjs/cloudflare from 1.20.16 to 1.20.17

Release notes

Sourced from @​opennextjs/cloudflare's releases.

@​opennextjs/cloudflare@​1.20.17

Patch Changes

  • #1488 e6c6736 Thanks @​vicb! - chore: bump @opennextjs/aws to 4.1.16

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

    • Match fallback: false routes against the decoded pathname.
    • Do not expose more Next.js internal headers on the middleware response.
    • Send the time of entries made stale by a tag to the revalidation queue.
    • Do not copy next.config headers onto the request headers.
    • Strip the internal next-resume header from incoming requests.
  • #1479 223f07f Thanks @​vicb! - fix: do not serve /cdn-cgi/image/ for revalidation requests sent through WORKER_SELF_REFERENCE

  • #1427 2d4665a Thanks @​jkugsiya! - fix: stop the Durable Object queue from revalidating routes again after every restart

    Once a revalidation had failed, the Durable Object queue revalidated the route again every time it restarted, even after the retry succeeded or the queue gave up. The number of extra revalidations grew until the next deployment. The queue now forgets a route once it stops retrying it.

  • #1486 843723c Thanks @​vicb! - fix: leave cloudflare:* imports external in the server bundle

    postgres 4 maps its Workers build (src/cf.js) to the workerd condition, and that build imports cloudflare:sockets statically. With postgres 4 in serverExternalPackages, the build failed while bundling the server with:

    ✘ [ERROR] Could not resolve "cloudflare:sockets"
    

    cloudflare:* imports are now left to wrangler, as node:* imports already are, so postgres 4 uses cloudflare:sockets in the Worker.

  • #1441 7d97fe8 Thanks @​mathurshubham! - fix: stop the Durable Object queue from skipping ISR revalidations until the next deployment

    With the Durable Object queue, some ISR pages stayed x-nextjs-cache: STALE until the next deployment:

    • pages that took more than about a second to revalidate,
    • pages made stale by revalidateTag after their first revalidation.

    These pages are now revalidated.

  • #1434 e476844 Thanks @​mathurshubham! - fix: re-arm the bucket cache purge alarm when the stored alarm is in the past

    Affects apps using purgeCache({ type: "durableObject" }) (the NEXT_CACHE_DO_PURGE binding).

    Once the purge alarm had exhausted its retries (for example after the Wrong number of parameter bindings error fixed in #1289, or a purge rate limit), the Durable Object never scheduled another alarm. Every later revalidateTag / revalidatePath queued its tags but the CDN cache was never purged and pages stayed stale.

    The alarm is now re-armed when it is in the past. After upgrading, the next revalidation purges the queued tags without having to reset the Durable Object. See opennextjs/opennextjs-cloudflare#929

  • #1431 8d30187 Thanks @​kremnyi! - fix: retry all the failed revalidations of the Durable Object queue

    When three or more failed ISR revalidations were waiting to be retried at the same time with the Durable Object queue (DOQueueHandler), only some of them were retried. The routes that were not retried stayed marked as failed, so later ISR requests for these routes did not trigger a revalidation either. These pages stayed stale until another revalidation failed or the Durable Object restarted.

... (truncated)

Changelog

Sourced from @​opennextjs/cloudflare's changelog.

1.20.17

Patch Changes

  • #1488 e6c6736 Thanks @​vicb! - chore: bump @opennextjs/aws to 4.1.16

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

    • Match fallback: false routes against the decoded pathname.
    • Do not expose more Next.js internal headers on the middleware response.
    • Send the time of entries made stale by a tag to the revalidation queue.
    • Do not copy next.config headers onto the request headers.
    • Strip the internal next-resume header from incoming requests.
  • #1479 223f07f Thanks @​vicb! - fix: do not serve /cdn-cgi/image/ for revalidation requests sent through WORKER_SELF_REFERENCE

  • #1427 2d4665a Thanks @​jkugsiya! - fix: stop the Durable Object queue from revalidating routes again after every restart

    Once a revalidation had failed, the Durable Object queue revalidated the route again every time it restarted, even after the retry succeeded or the queue gave up. The number of extra revalidations grew until the next deployment. The queue now forgets a route once it stops retrying it.

  • #1486 843723c Thanks @​vicb! - fix: leave cloudflare:* imports external in the server bundle

    postgres 4 maps its Workers build (src/cf.js) to the workerd condition, and that build imports cloudflare:sockets statically. With postgres 4 in serverExternalPackages, the build failed while bundling the server with:

    ✘ [ERROR] Could not resolve "cloudflare:sockets"
    

    cloudflare:* imports are now left to wrangler, as node:* imports already are, so postgres 4 uses cloudflare:sockets in the Worker.

  • #1441 7d97fe8 Thanks @​mathurshubham! - fix: stop the Durable Object queue from skipping ISR revalidations until the next deployment

    With the Durable Object queue, some ISR pages stayed x-nextjs-cache: STALE until the next deployment:

    • pages that took more than about a second to revalidate,
    • pages made stale by revalidateTag after their first revalidation.

    These pages are now revalidated.

  • #1434 e476844 Thanks @​mathurshubham! - fix: re-arm the bucket cache purge alarm when the stored alarm is in the past

    Affects apps using purgeCache({ type: "durableObject" }) (the NEXT_CACHE_DO_PURGE binding).

    Once the purge alarm had exhausted its retries (for example after the Wrong number of parameter bindings error fixed in #1289, or a purge rate limit), the Durable Object never scheduled another alarm. Every later revalidateTag / revalidatePath queued its tags but the CDN cache was never purged and pages stayed stale.

    The alarm is now re-armed when it is in the past. After upgrading, the next revalidation purges the queued tags without having to reset the Durable Object. See opennextjs/opennextjs-cloudflare#929

  • #1431 8d30187 Thanks @​kremnyi! - fix: retry all the failed revalidations of the Durable Object queue

    When three or more failed ISR revalidations were waiting to be retried at the same time with the Durable Object queue (DOQueueHandler), only some of them were retried. The routes that were not retried stayed marked as failed, so later ISR requests for these routes did not trigger a revalidation either. These pages stayed stale until another revalidation failed or the Durable Object restarted.

... (truncated)

Commits
  • 0e007b3 Version Packages (#1480)
  • e6c6736 chore: bump @opennextjs/aws to 4.1.16 (#1488)
  • 843723c fix: leave cloudflare:* imports external in the server bundle (#1486)
  • b6ccf33 fix: resolve the workerd build of packages from the installed `node_modules...
  • e476844 fix: re-arm the bucket cache purge alarm when the stored alarm is in the past...
  • 7d97fe8 fix: do not skip ISR revalidations for pages that take longer than a second t...
  • 8d30187 fix: set the next Durable Object queue alarm for failed revalidations that th...
  • 2d4665a fix: delete the persisted failed revalidation once the Durable Object queue s...
  • 0e23c67 refactor(DOQueueHandler): document, test and clean up (#1481)
  • 223f07f fix: do not serve /cdn-cgi/image/ for revalidation requests sent through `W...
  • See full diff in compare view

Updates next from 16.4.5 to 16.4.6

Release notes

Sourced from next's releases.

v16.4.6

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

Core Changes

  • [lts-active] Pin Tailwind to 4.3.3 in create-next-app and tests (#101061, #101176) (#101307)
  • [lts-active] Automatically compress route handler responses if not already compressed (#101280)
  • [lts-active] Turbopack GC fixes for dev (#100279, #100370) (#101308)

Credits

Huge thanks to @​lukesandberg and @​eps1lon for helping!

Commits

Updates eslint-config-next from 16.4.5 to 16.4.6

Release notes

Sourced from eslint-config-next's releases.

v16.4.6

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

Core Changes

  • [lts-active] Pin Tailwind to 4.3.3 in create-next-app and tests (#101061, #101176) (#101307)
  • [lts-active] Automatically compress route handler responses if not already compressed (#101280)
  • [lts-active] Turbopack GC fixes for dev (#100279, #100370) (#101308)

Credits

Huge thanks to @​lukesandberg and @​eps1lon for helping!

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the next group with 3 updates: [@opennextjs/cloudflare](https://github.com/opennextjs/opennextjs-cloudflare/tree/HEAD/packages/cloudflare), [next](https://github.com/vercel/next.js) and [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next).


Updates `@opennextjs/cloudflare` from 1.20.16 to 1.20.17
- [Release notes](https://github.com/opennextjs/opennextjs-cloudflare/releases)
- [Changelog](https://github.com/opennextjs/opennextjs-cloudflare/blob/main/packages/cloudflare/CHANGELOG.md)
- [Commits](https://github.com/opennextjs/opennextjs-cloudflare/commits/@opennextjs/cloudflare@1.20.17/packages/cloudflare)

Updates `next` from 16.4.5 to 16.4.6
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.4.5...v16.4.6)

Updates `eslint-config-next` from 16.4.5 to 16.4.6
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](https://github.com/vercel/next.js/commits/v16.4.6/packages/eslint-config-next)

---
updated-dependencies:
- dependency-name: "@opennextjs/cloudflare"
  dependency-version: 1.20.17
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: next
- dependency-name: next
  dependency-version: 16.4.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: next
- dependency-name: eslint-config-next
  dependency-version: 16.4.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: next
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 17, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants