build(deps): bump next from 12.1.4 to 15.5.14 in /example/nextjs#306
build(deps): bump next from 12.1.4 to 15.5.14 in /example/nextjs#306dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [next](https://github.com/vercel/next.js) from 12.1.4 to 15.5.14. - [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.1.4...v15.5.14) --- updated-dependencies: - dependency-name: next dependency-version: 15.5.14 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
|
Deploy preview for team-scope-test ready! ✅ Preview Built with commit 1bb722f. |
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="example/nextjs/package.json">
<violation number="1" location="example/nextjs/package.json:10">
P1: Next.js 15 requires `react` and `react-dom` `^18.2.0 || ^19.0.0`, but both are pinned at `18.0.0`. This will cause peer-dependency conflicts and likely build failures. The `eslint-config-next` in devDependencies also needs to be bumped from `12.1.4` to match the new Next.js major version.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| }, | ||
| "dependencies": { | ||
| "next": "12.1.4", | ||
| "next": "15.5.14", |
There was a problem hiding this comment.
P1: Next.js 15 requires react and react-dom ^18.2.0 || ^19.0.0, but both are pinned at 18.0.0. This will cause peer-dependency conflicts and likely build failures. The eslint-config-next in devDependencies also needs to be bumped from 12.1.4 to match the new Next.js major version.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At example/nextjs/package.json, line 10:
<comment>Next.js 15 requires `react` and `react-dom` `^18.2.0 || ^19.0.0`, but both are pinned at `18.0.0`. This will cause peer-dependency conflicts and likely build failures. The `eslint-config-next` in devDependencies also needs to be bumped from `12.1.4` to match the new Next.js major version.</comment>
<file context>
@@ -7,7 +7,7 @@
},
"dependencies": {
- "next": "12.1.4",
+ "next": "15.5.14",
"react": "18.0.0",
"react-dom": "18.0.0",
</file context>
|
@dependabot rebase |
|
The dependabot.yml entry that created this PR has been deleted so this PR can't be rebased. Please close the PR so Dependabot can create a new one with the current dependabot.yml. |



Bumps next from 12.1.4 to 15.5.14.
Release notes
Sourced from next's releases.
Commits
d7b012dv15.5.142b05251[backport] feat(next/image): add lru disk cache and `images.maximumDiskCacheS...f88cee9Backport: Fix(pages-router): restore Content-Length and ETag for /_next/data/...cfd5f53v15.5.1315f2891[backport]: fix: patch http-proxy to prevent request smuggling in rewrites (#...d23f41cv15.5.128e75765fix unlock in publish-native6cef992[backport] normalize CRLF line endings in jscodeshift tests on Windows (#8800...7a94645Apply needs for publishReleasebbfd4e3v15.5.11Dependabot 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.