Skip to content

chore(deps): bump next from 12.3.4 to 16.1.5#405

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/next-16.1.5
Open

chore(deps): bump next from 12.3.4 to 16.1.5#405
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/next-16.1.5

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 29, 2026

Bumps next from 12.3.4 to 16.1.5.

Release notes

Sourced from next's releases.

v16.1.5

Please refer the following changelogs for more information about this security release:

https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472 https://vercel.com/changelog/summary-of-cve-2026-23864

v16.1.4

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

Core Changes

  • Only filter next config if experimental flag is enabled (#88733)

Credits

Huge thanks to @​mischnic for helping!

v16.1.3

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

Core Changes

  • Fix linked list bug in LRU deleteFromLru (#88652)
  • Fix relative same host redirects in node middleware (#88253)

Credits

Huge thanks to @​acdlite and @​ijjk for helping!

v16.1.2

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

Core Changes

  • Turbopack: Update to swc_core v50.2.3 (#87841) (#88296)
    • Fixes a crash when processing mdx files with multibyte characters. (#87713)
  • Turbopack: mimalloc upgrade and enabling it on musl (#88503) (#87815) (#88426)
    • Fixes a significant performance issue on musl-based Linux distributions (e.g. Alpine in Docker) related to musl's allocator.
    • Other platforms have always used mimalloc, but we previously did not use mimalloc on musl because of compilation issues that have since been resolved.

Credits

Huge thanks to @​mischnic for helping!

v16.1.1

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

... (truncated)

Commits
  • acba4a6 v16.1.5
  • e1d1fc6 Add maximum size limit for postponed body parsing (#88175)
  • 500ec83 fetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)
  • 1caaca3 feat(next/image)!: add images.maximumResponseBody config (#88183)
  • 522ed84 Sync DoS mitigations for React Flight
  • 8cad197 [backport][cna] Ensure created app is not considered the workspace root in pn...
  • 2718661 Backport/docs fixes (#89031)
  • 5333625 Backport/docs fixes 16.1.5 (#88916)
  • 60de6c2 v16.1.4
  • 5f75d22 backport: Only filter next config if experimental flag is enabled (#88733) (#...
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [next](https://github.com/vercel/next.js) from 12.3.4 to 16.1.5.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v12.3.4...v16.1.5)

---
updated-dependencies:
- dependency-name: next
  dependency-version: 16.1.5
  dependency-type: direct:production
...

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 Jan 29, 2026
@vercel
Copy link

vercel bot commented Jan 29, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
evm-codes Error Error Jan 29, 2026 0:53am

Request Review

@cursor
Copy link

cursor bot commented Jan 29, 2026

PR Summary

Medium Risk
Major Next.js upgrade with significant framework/runtime and build pipeline changes; may require Node >=20.9 and can break routing/build behavior or image processing dependencies at runtime.

Overview
Updates the app to Next.js 16 by bumping next from 12.x to 16.1.5 and refreshing the pnpm-lock.yaml to match the new dependency graph.

The lockfile changes bring in Next 16’s updated runtime/build toolchain (new @next/* SWC binaries, updated styled-jsx/postcss/@swc/helpers, and new optional sharp-related packages used by next/image).

Written by Cursor Bugbot for commit 1546b4a. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

Comment @cursor review or bugbot run to trigger another review on this PR

"lodash.debounce": "^4.0.8",
"monaco-editor": "^0.47.0",
"next": "12",
"next": "16",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

React version incompatible with Next.js 16 requirements

High Severity

Next.js 16 requires react and react-dom version ^18.2.0 or ^19.0.0, but the project uses ^17.0.2. This peer dependency mismatch will cause the application to fail at runtime or during build since Next.js 16 relies on React 18+ features like the improved concurrent rendering APIs.

Additional Locations (1)

Fix in Cursor Fix in Web

"lodash.debounce": "^4.0.8",
"monaco-editor": "^0.47.0",
"next": "12",
"next": "16",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

next-plausible incompatible with Next.js 16

Medium Severity

The next-plausible@3.12.0 package declares peer dependencies of next: ^11.1.0 || ^12.0.0 || ^13.0.0 || ^14.0.0, which explicitly excludes Next.js 15 and 16. Upgrading to Next.js 16 violates this constraint and the analytics integration may fail or behave unexpectedly at runtime.

Additional Locations (1)

Fix in Cursor Fix in Web

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