Bump next from 14.2.1 to 15.5.18 in /apps/nextjs-14_2_1#84
Bump next from 14.2.1 to 15.5.18 in /apps/nextjs-14_2_1#84dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [next](https://github.com/vercel/next.js) from 14.2.1 to 15.5.18. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.1...v15.5.18) --- updated-dependencies: - dependency-name: next dependency-version: 15.5.18 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![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.
Reviewed by Cursor Bugbot for commit 81fa0b7. Configure here.
| "dependencies": { | ||
| "@sentry/nextjs": "8.9.2", | ||
| "next": "14.2.1", | ||
| "next": "15.5.18", |
There was a problem hiding this comment.
Sentry SDK incompatible with Next.js 15 major upgrade
High Severity
Bumping next to 15.5.18 while keeping @sentry/nextjs at 8.9.2 creates a breaking incompatibility. Version 8.9.2 was released before Next.js 15 existed and its peer dependencies only cover ^13.4.0 || ^14.0.0. The withSentryConfig wrapper in next.config.mjs and the instrumentation hooks rely on Next.js internals that changed significantly in the v14→v15 major version jump, likely causing build or runtime failures.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 81fa0b7. Configure here.
| "dependencies": { | ||
| "@sentry/nextjs": "8.9.2", | ||
| "next": "14.2.1", | ||
| "next": "15.5.18", |
There was a problem hiding this comment.
React 18 unsupported with Next.js 15 App Router
Medium Severity
next is bumped to 15.5.18 but react and react-dom remain at ^18. Next.js 15's App Router requires React 19; React 18 is only supported for the Pages Router. This application uses the App Router (app/ directory with layouts, pages, and route handlers), so the React 18 dependency will cause incompatibility issues with App Router features.
Reviewed by Cursor Bugbot for commit 81fa0b7. Configure here.
Bumps next from 14.2.1 to 15.5.18.
Release notes
Sourced from next's releases.
... (truncated)
Commits
9ff92cev15.5.1800ebe23[backport] Disable build caches for production/staging/force-preview deploys ...62c97abv15.5.17423623aTurbopack: Match proxy matchers with webpack implementation (#93594)fa78739Turbopack: Fix middleware matcher suffix (#93590)36e62c6[backport] Turbopack: more strict vergen setup (#93588)36589b5[backport][test] Pin package manager to patch versions (#93596)ad6fd4ev15.5.1679d7dffIgnore malformed CSP nonce headers (#103)c4f6908router-server: guard upgrade proxy against absolute-url SSRF (#77) (#102)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.
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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.