chore: bump next from 12.1.4 to 15.5.14 - #305
Closed
dependabot[bot] wants to merge 1 commit into
Closed
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>
dependabot
Bot
added
dependencies
|
Contributor
|
Deploy preview for team-scope-test ready! ✅ Preview Built with commit 806feb2. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 2 files
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: `react` and `react-dom` at `18.0.0` don't satisfy Next.js 15's peer dependency requirement of `^18.2.0`. Bump both to at least `18.2.0` (or to `19.x` for full Next 15 support).</violation>
</file>
Architecture diagram
sequenceDiagram
participant Client as Browser / Client
participant Server as Next.js Server
participant Cache as LRU Disk Cache
participant Proxy as Rewrites / HTTP Proxy
participant Upstream as Upstream Service
Note over Client, Upstream: Next.js v15 Runtime Behavioral Changes
rect rgb(240, 240, 240)
Note right of Client: Image Optimization Flow
Client->>Server: GET /_next/image?url=...
Server->>Cache: NEW: Check LRU Disk Cache
alt Cache Miss
Server->>Server: Optimize image
Server->>Cache: NEW: Write to disk (respect images.maximumDiskCacheSize)
end
Cache-->>Server: Optimized Image
Server-->>Client: 200 OK (Image)
end
rect rgb(230, 230, 230)
Note right of Client: Data Prefetching (Pages Router)
Client->>Server: GET /_next/data/.../page.json
Server->>Server: Resolve getStaticProps / getServerSideProps
Server-->>Client: CHANGED: JSON response (Restored ETag & Content-Length)
end
rect rgb(220, 220, 220)
Note right of Client: Rewrites & Proxying
Client->>Server: Request /api/rewritten-path
Server->>Proxy: process rewrite
Proxy->>Proxy: CHANGED: Patch http-proxy (Prevent request smuggling)
Proxy->>Upstream: Forward secured request
Upstream-->>Proxy: Response
Proxy-->>Client: Response
end
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: react and react-dom at 18.0.0 don't satisfy Next.js 15's peer dependency requirement of ^18.2.0. Bump both to at least 18.2.0 (or to 19.x for full Next 15 support).
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>`react` and `react-dom` at `18.0.0` don't satisfy Next.js 15's peer dependency requirement of `^18.2.0`. Bump both to at least `18.2.0` (or to `19.x` for full Next 15 support).</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>
Contributor
Author
|
Looks like next is up-to-date now, so this is no longer needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.