Bump next from 14.1.4 to 15.5.10 in /_config/nodeAPI#8
Bump next from 14.1.4 to 15.5.10 in /_config/nodeAPI#8dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [next](https://github.com/vercel/next.js) from 14.1.4 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@v14.1.4...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>
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.
| }, | ||
| "dependencies": { | ||
| "next": "^14.1.4", | ||
| "next": "^15.5.10", |
There was a problem hiding this comment.
Next.js 15 async params break route handlers
High Severity
Upgrading to Next.js 15 introduces a breaking change where params in route handlers is now a Promise. The existing route handlers access context.params.chainID, context.params.filename, and context.params.tokenAddress synchronously, but since params is now a Promise, these property accesses return undefined. The fallback values (|| 1, || '') then take over, causing all API requests to use incorrect default values (chainID 1, empty strings) instead of actual route parameters. This will silently break the API endpoints.
|
Superseded by #9. |
Bumps next from 14.1.4 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.
Note
Upgrades the app to Next.js 15.5.10 and refreshes dependencies.
nextfrom^14.1.4to^15.5.10; updates@next/envand@next/swc-*toolchainsstyled-jsxto5.1.6,@swc/helpersto0.5.15withtslib ^2.8, addssharp ^0.34and platform-specific@img/sharp-*binariesbusboy,streamsearch); general transitive upgrades (e.g.,semver,graceful-fs)Written by Cursor Bugbot for commit 43f6ec1. This will update automatically on new commits. Configure here.