Bump next from 14.1.4 to 16.1.5 in /_config/nodeAPI#9
Bump next from 14.1.4 to 16.1.5 in /_config/nodeAPI#9dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [next](https://github.com/vercel/next.js) from 14.1.4 to 16.1.5. - [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...v16.1.5) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.5 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 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| }, | ||
| "dependencies": { | ||
| "next": "^14.1.4", | ||
| "next": "^16.1.5", |
There was a problem hiding this comment.
eslint-config-next version mismatch with Next.js 16
Medium Severity
The next dependency is upgraded to ^16.1.5, but eslint-config-next remains at ^14.1.4. These packages are designed to work together and should be kept in sync. The ESLint config for Next.js 14 may not correctly validate Next.js 16 patterns, potentially missing new linting rules or incorrectly flagging valid Next.js 16 code. The eslint-config-next dependency should be updated to ^16.1.5 to match.
Additional Locations (1)
| }, | ||
| "dependencies": { | ||
| "next": "^14.1.4", | ||
| "next": "^16.1.5", |
There was a problem hiding this comment.
Export script broken by removed next export command
High Severity
The upgrade to Next.js 16 breaks the existing export script at line 12, which uses next export -o ipfs. The next export command was fully removed in Next.js 16 and now throws an error: "next export has been removed in favor of 'output: export' in next.config.js." Static exports now require setting output: 'export' in next.config.js instead of using a CLI command.
Bumps next from 14.1.4 to 16.1.5.
Release notes
Sourced from next's releases.
... (truncated)
Commits
acba4a6v16.1.5e1d1fc6Add maximum size limit for postponed body parsing (#88175)500ec83fetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)1caaca3feat(next/image)!: addimages.maximumResponseBodyconfig (#88183)522ed84Sync DoS mitigations for React Flight8cad197[backport][cna] Ensure created app is not considered the workspace root in pn...2718661Backport/docs fixes (#89031)5333625Backport/docs fixes 16.1.5 (#88916)60de6c2v16.1.45f75d22backport: Only filter next config if experimental flag is enabled (#88733) (#...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
Medium Risk
Major framework upgrade in
_config/nodeAPIthat can introduce runtime/build differences and includes new native optional deps (e.g.,sharp) that may affect install/CI across platforms.Overview
Upgrades the
_config/nodeAPIapp fromnext@14.1.4tonext@16.1.5and refreshesyarn.lockaccordingly.The lockfile update pulls in new/updated Next-related dependencies (notably
@next/*SWC binaries,@swc/helpers,styled-jsx) and addssharp(plus platform-specific@img/*packages) as an optional dependency via Next.Written by Cursor Bugbot for commit b9706f8. This will update automatically on new commits. Configure here.