Skip to content

chore(deps): bump the npm-minor-patch group with 6 updates - #740

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-patch-d6d4e2b29a
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-patch-d6d4e2b29a

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps the npm-minor-patch group with 6 updates:

Package From To
@next/mdx 16.4.5 16.4.6
@next/third-parties 16.4.5 16.4.6
next 16.4.5 16.4.6
simple-icons 16.36.0 16.37.0
@opennextjs/cloudflare 1.20.16 1.20.17
wrangler 4.158.0 4.162.0

Updates @next/mdx from 16.4.5 to 16.4.6

Release notes

Sourced from @​next/mdx'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 @next/third-parties from 16.4.5 to 16.4.6

Release notes

Sourced from @​next/third-parties'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 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 simple-icons from 16.36.0 to 16.37.0

Release notes

Sourced from simple-icons's releases.

Release 16.37.0

3 new icons

2 updated icons

Commits

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 wrangler from 4.158.0 to 4.162.0

Release notes

Sourced from wrangler's releases.

wrangler@4.162.0

Minor Changes

  • #16735 f005593 Thanks @​leostera! - Use the local simulator for Artifacts bindings that omit remote

    Behavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted remote in Wrangler and the Vite plugin used the deployed Artifacts resource. If you want deployed repos in wrangler dev or vite dev, set "remote": true on the binding (dev: { remote: true } in cloudflare.config.ts). Artifacts is in beta, so this ships as a minor release.

    While remote is omitted, wrangler dev, getPlatformProxy() and the Vite plugin warn when remote bindings are enabled, once for each binding rather than on every config reload: "Artifacts binding REPOS uses the local simulator by default. Set remote: true to use deployed repos, or remote: false to silence this warning." Workers Vitest and wrangler dev --local already used the simulator, so they don't warn. Local Artifacts needs no Cloudflare credentials, but requires Git 2.32 or newer on the host.

  • #16749 032f8c2 Thanks @​vaishnav-mk! - Reject settings on a workflows binding to a Workflow declared in exports

    A workflows binding can still bind a Workflow that the Worker declares in exports, but it can no longer set limits, concurrency, schedules, default_retention, or jurisdiction for it. Set them on the export instead. Previously the binding and the export could both set them as long as they agreed, so configurations that set them on the binding now stop with an error that says which setting to move.

  • #16749 032f8c2 Thanks @​vaishnav-mk! - Upload Workflow export settings with the Worker

    wrangler deploy and wrangler versions upload now include the settings of each workflow export (limits, concurrency, schedules, default_retention, and jurisdiction) in the upload, instead of sending only its type and name. Uploads of a Worker with workflow exports also send a Cloudflare-Workers-Script-Api-Date header, which lets the Workers API provision Workflow exports from these settings as part of the upload. wrangler deploy and wrangler triggers deploy still create or update each Workflow through the Workflows API afterwards, as before.

    If provisioning a scheduled Workflow fails because the account is on the free plan, wrangler deploy now explains that scheduled Workflows require a paid Workers plan.

Patch Changes

  • #16849 3cea40b Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-12

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16886 63eb6da Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-13

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16849 3cea40b Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261110.1 ^5.20261112.1
    workerd 1.20261110.1 1.20261112.1
  • #16886 63eb6da Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261112.1 ^5.20261113.1
    workerd 1.20261112.1 1.20261113.1
  • #16864 3b1b408 Thanks @​MattieTK! - Fix packages with nested package.json files missing from deploy metadata

    Packages such as hono, stripe and @modelcontextprotocol/sdk were silently omitted from the package dependency metadata reported during wrangler deploy and wrangler versions upload. These packages are now included with their installed versions. Autoconfig and codemods also detect their installed versions correctly.

... (truncated)

Commits
  • 79b890a Version Packages (#16863)
  • f005593 [wrangler] Use the local Artifacts simulator when remote is omitted (#16735)
  • 032f8c2 [deploy-helpers,wrangler,codemods] Upload Workflow export settings with the W...
  • c889551 [wrangler] Fix requests hanging after local Worker reloads (#16862)
  • 1e688ba Version Packages (#16836)
  • 8b2a363 Write source maps in Build Output with sources relative to each source map ...
  • 575d136 [autoconfig] Support SolidStart 2 on cf (#16559)
  • 3626ee8 Remove CLOUDFLARE_CF_AUTH and require explicit auth for remote bindings ses...
  • 5f539b5 Name cf commands and settings in remote bindings errors (#16833)
  • 12a9105 [wrangler] Quiet E2E cleanup and preserve deployment failure output (#16832)
  • Additional commits viewable in compare view

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 npm-minor-patch group with 6 updates:

| Package | From | To |
| --- | --- | --- |
| [@next/mdx](https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx) | `16.4.5` | `16.4.6` |
| [@next/third-parties](https://github.com/vercel/next.js/tree/HEAD/packages/third-parties) | `16.4.5` | `16.4.6` |
| [next](https://github.com/vercel/next.js) | `16.4.5` | `16.4.6` |
| [simple-icons](https://github.com/simple-icons/simple-icons) | `16.36.0` | `16.37.0` |
| [@opennextjs/cloudflare](https://github.com/opennextjs/opennextjs-cloudflare/tree/HEAD/packages/cloudflare) | `1.20.16` | `1.20.17` |
| [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) | `4.158.0` | `4.162.0` |


Updates `@next/mdx` 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/next-mdx)

Updates `@next/third-parties` 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/third-parties)

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 `simple-icons` from 16.36.0 to 16.37.0
- [Release notes](https://github.com/simple-icons/simple-icons/releases)
- [Commits](simple-icons/simple-icons@16.36.0...16.37.0)

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 `wrangler` from 4.158.0 to 4.162.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.162.0/packages/wrangler)

---
updated-dependencies:
- dependency-name: "@next/mdx"
  dependency-version: 16.4.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: "@next/third-parties"
  dependency-version: 16.4.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: next
  dependency-version: 16.4.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: simple-icons
  dependency-version: 16.37.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: "@opennextjs/cloudflare"
  dependency-version: 1.20.17
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: wrangler
  dependency-version: 4.162.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants