-
Notifications
You must be signed in to change notification settings - Fork 187
chore(deps): bump next from 12.3.4 to 15.5.10 #404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Bumps [next](https://github.com/vercel/next.js) from 12.3.4 to 15.5.10. - [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...v15.5.10) --- updated-dependencies: - dependency-name: next dependency-version: 15.5.10 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryUpgrades the app framework.
Written by Cursor Bugbot for commit cc0eba3. Configure here. |
There was a problem hiding this 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": "15", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Next.js 15 incompatible with React 17
High Severity
Next.js 15 requires React 18.2.0 or higher as a peer dependency (react: ^18.2.0 || 19.0.0-rc || ^19.0.0), but the project specifies react: ^17.0.2 and react-dom: ^17.0.2. This peer dependency mismatch will likely cause runtime failures because Next.js 15 relies on React 18+ features like concurrent rendering, automatic batching, and the use hook that don't exist in React 17.
Additional Locations (1)
| "lodash.debounce": "^4.0.8", | ||
| "monaco-editor": "^0.47.0", | ||
| "next": "12", | ||
| "next": "15", |
There was a problem hiding this comment.
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 15
Medium Severity
The next-plausible@3.12.0 package declares peer dependency next: ^11.1.0 || ^12.0.0 || ^13.0.0 || ^14.0.0, which explicitly excludes Next.js 15. This upgrade forces next-plausible to use Next.js 15 (visible at lock file line 8289), creating a peer dependency mismatch that may cause the analytics integration to malfunction or fail at runtime due to API changes between Next.js versions.
Additional Locations (1)
|
Superseded by #405. |
Bumps next from 12.3.4 to 15.5.10.
Release notes
Sourced from next's releases.
... (truncated)
Commits
60a2aa9v15.5.10e5b834dfetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)39a2f6afeat(next/image)!: addimages.maximumResponseBodyconfig (#88183)bf9f084Sync DoS mitigations for React Flightc5de33ev15.5.9dd23399Backport facebook/react#35351 for 15.5.8 (#87086)7526cd6v15.5.81e9ec41Update React Version (#41)16141e5Update React Version (#30)e01e589Backport Next.js changes to v15.5.8 (#23)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 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.