-
Notifications
You must be signed in to change notification settings - Fork 15
chore(deps): bump next from 13.5.6 to 15.5.10 #48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Bumps [next](https://github.com/vercel/next.js) from 13.5.6 to 15.5.10. - [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.5.6...v15.5.10) --- updated-dependencies: - dependency-name: next dependency-version: 15.5.10 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
PR SummaryUpgrades the app to Next.js 15.5.10.
Written by Cursor Bugbot for commit 8936c69. This will update automatically on new commits. Configure here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| "isomorphic-fetch": "^3.0.0", | ||
| "markdownlint-cli": "^0.37.0", | ||
| "next": "^13.5.6", | ||
| "next": "^15.5.10", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deprecated experimental config incompatible with Next.js 15
High Severity
Upgrading next from 13.5.6 to 15.5.10 without updating next.config.js introduces incompatibility. The experimental.swcMinify: true option was removed in Next.js 15 (now always-on default). The experimental.esmExternals and experimental.externalDir options may also have changed behavior. This major version jump (skipping v14) requires running the official migration codemod and updating config options to avoid build failures or unexpected runtime behavior.
| "isomorphic-fetch": "^3.0.0", | ||
| "markdownlint-cli": "^0.37.0", | ||
| "next": "^13.5.6", | ||
| "next": "^15.5.10", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed next export command breaks export script
High Severity
The export script uses next export -o $DOCS_DIST, but the next export command was removed in Next.js 14 and does not exist in Next.js 15. Running npm run export will fail with "Unknown command: export". Static export in Next.js 14+ requires adding output: 'export' to next.config.js and running next build instead, which outputs to the out directory by default.
|
Superseded by #49. |
Bumps next from 13.5.6 to 15.5.10.
Release notes
Sourced from next's releases.
... (truncated)
Commits
60a2aa9v15.5.10e5b834dfetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)39a2f6afeat(next/image)!: addimages.maximumResponseBodyconfig (#88183)bf9f084Sync DoS mitigations for React Flightc5de33ev15.5.9dd23399Backport facebook/react#35351 for 15.5.8 (#87086)7526cd6v15.5.81e9ec41Update React Version (#41)16141e5Update React Version (#30)e01e589Backport Next.js changes to v15.5.8 (#23)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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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.