Bump next from 15.5.9 to 16.1.5 in the npm_and_yarn group across 1 directory #8
Conversation
Bumps the npm_and_yarn group with 1 update in the / directory: [next](https://github.com/vercel/next.js). Updates `next` from 15.5.9 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@v15.5.9...v16.1.5) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.5 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
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.
| "lucide-react": "^0.477.0", | ||
| "motion": "^12.23.12", | ||
| "next": "^15.5.8", | ||
| "next": "^16.1.5", |
There was a problem hiding this comment.
Peer dependency mismatch after Next.js major upgrade
Medium Severity
Upgrading next to 16.1.5 while @next/third-parties remains at ^15.5.8 creates a peer dependency conflict. The @next/[email protected] package declares a peer dependency of next: ^13.0.0 || ^14.0.0 || ^15.0.0, which does not include Next.js 16.x. This mismatch could cause runtime errors or unexpected behavior with third-party integrations like Google Analytics, Google Maps, or YouTube embeds.
| "lucide-react": "^0.477.0", | ||
| "motion": "^12.23.12", | ||
| "next": "^15.5.8", | ||
| "next": "^16.1.5", |
There was a problem hiding this comment.
Sentry integration incompatible with Next.js 16 upgrade
Medium Severity
The @sentry/[email protected] package has a peer dependency of next: ^13.2.0 || ^14.0 || ^15.0.0-rc.0, which does not include Next.js 16.x. Upgrading next to 16.1.5 while keeping @sentry/nextjs at ^9.46.0 creates a peer dependency conflict. This could cause Sentry's error tracking, source map uploads, or server-side error capturing to malfunction or fail silently in production.
Bumps the npm_and_yarn group with 1 update in the / directory: next.
Updates
nextfrom 15.5.9 to 16.1.5Release notes
Sourced from next's releases.
... (truncated)
Commits
acba4a6v16.1.5e1d1fc6Add maximum size limit for postponed body parsing (#88175)500ec83fetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)1caaca3feat(next/image)!: addimages.maximumResponseBodyconfig (#88183)522ed84Sync DoS mitigations for React Flight8cad197[backport][cna] Ensure created app is not considered the workspace root in pn...2718661Backport/docs fixes (#89031)5333625Backport/docs fixes 16.1.5 (#88916)60de6c2v16.1.45f75d22backport: Only filter next config if experimental flag is enabled (#88733) (#...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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 conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.
Note
Medium Risk
Medium risk because this is a major Next.js upgrade (15→16) that can change build/runtime behavior and requires a newer Node engine; it also refreshes a wide set of transitive build tooling dependencies.
Overview
Upgrades
apps/webfrom[email protected]to[email protected].Updates
pnpm-lock.yamlaccordingly, pulling in the new Next.js SWC binaries and related transitive upgrades (notablysharp,esbuild,terser/terser-webpack-plugin,webpackresolution deps), and adjusting tooling dependency resolutions (e.g.,@sentry/nextjsandreact-scannow resolve against Next 16).Written by Cursor Bugbot for commit b738d2d. This will update automatically on new commits. Configure here.