Conversation
Bumps [next](https://github.com/vercel/next.js) from 13.2.0 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@v13.2.0...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
![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 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| "@types/react": "18.2.79", | ||
| "@types/react-dom": "18.2.25", | ||
| "next": "13.2.0", | ||
| "next": "15.5.14", |
There was a problem hiding this comment.
Version-specific test app bumped to wrong Next.js version
High Severity
The nextjs-13_2_0 test application exists specifically to test Sentry SDK compatibility with Next.js 13.2.0. Dependabot has bumped next from 13.2.0 to 15.5.14, which completely defeats the purpose of this version-pinned test fixture. The repository also has a separate nextjs-14_2_1 app, confirming each app targets a specific Next.js version. Additionally, the next.config.js uses experimental.appDir: true, which was removed in later Next.js versions and will cause an "Unrecognized key" build error with Next.js 15.
Bumps next from 13.2.0 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.