Bump next from 15.4.6 to 15.5.18#4973
Conversation
Bumps [next](https://github.com/vercel/next.js) from 15.4.6 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@v15.4.6...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>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Pull Request Overview
This PR upgrades Next.js to version 15.5.18 to mitigate several security vulnerabilities, including DoS, SSRF, and XSS. Although Codacy indicates the changes are up to standards, a critical peer dependency conflict has been identified that prevents successful installation: Next.js 15 requires React 19, but the project is currently configured with React 18.3.1. This blocker must be resolved by also upgrading the React dependencies to ensure the application remains functional.
Test suggestions
- Verify that the application builds successfully without errors using Next.js 15.5.18.
- Verify that the application's core functionality, such as routing and server-side rendering, remains intact after the upgrade.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that the application builds successfully without errors using Next.js 15.5.18.
2. Verify that the application's core functionality, such as routing and server-side rendering, remains intact after the upgrade.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
| "mongoose": "^8.12.1", | ||
| "newrelic": "^13.6.5", | ||
| "next": "^15.4.6", | ||
| "next": "^15.5.18", |
There was a problem hiding this comment.
🔴 HIGH RISK
Next.js 15 requires React 19 and React DOM 19 as peer dependencies. The package.json currently specifies React 18.3.1, which will lead to installation failures. Try running the following prompt in your coding agent: > Upgrade react and react-dom to version 19.
Bumps next from 15.4.6 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.