Bump next from 13.1.6 to 15.5.14 in /apps/site#1547
Conversation
Bumps [next](https://github.com/vercel/next.js) from 13.1.6 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.1.6...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>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 3 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| "mock-block-dock": "0.1.10", | ||
| "mongodb": "^4.17.0", | ||
| "next": "13.1.6", | ||
| "next": "15.5.14", |
There was a problem hiding this comment.
Next 15 build breaks due to removed swcMinify option
High Severity
Bumping next to 15.5.14 will cause the build to fail because next.config.js contains swcMinify: true, which was removed as a config option in Next.js 15. Next.js 15 rejects this as an unrecognized key and errors during build. The option needs to be removed from the config (SWC minification is now the non-configurable default).
| "mock-block-dock": "0.1.10", | ||
| "mongodb": "^4.17.0", | ||
| "next": "13.1.6", | ||
| "next": "15.5.14", |
There was a problem hiding this comment.
Companion @next/bundle-analyzer version not updated alongside next
Medium Severity
next is bumped to 15.5.14 but @next/bundle-analyzer remains at 13.0.7. The @next/* packages are designed to be version-matched with next. A two-major-version mismatch between these packages can cause build or runtime errors due to changed internal APIs. It needs to be updated to a 15.x version.
There was a problem hiding this comment.
ISR cache config silently ignored after rename in Next 15
Medium Severity
The experimental.isrMemoryCacheSize config option was stabilized and renamed to top-level cacheMaxMemorySize before Next.js 15. After this bump, the isrMemoryCacheSize: 0 setting in next.config.js is silently ignored, causing the ISR memory cache to revert to its default (50 MB). This breaks an intentional design decision — the test infrastructure in tests/shared/fixtures.ts explicitly depends on this being zero to avoid stale cached pages after database reseeding.



Bumps next from 13.1.6 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.