chore(deps): bump next from 13.5.6 to 16.1.5 #49
Conversation
Bumps [next](https://github.com/vercel/next.js) from 13.5.6 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@v13.5.6...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
PR SummaryHigh Risk Overview The lockfile reflects Next 16’s new dependency set and constraints, including an updated SWC toolchain, Written by Cursor Bugbot for commit 4de2a80. This will update automatically on new commits. Configure here. |
![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 3 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": "^16.1.5", |
There was a problem hiding this comment.
Removed next export command breaks export script
High Severity
The export script uses the next export command which was removed in Next.js 14. In Next.js 16.1.5, running next export -o $DOCS_DIST will fail because this command no longer exists. The replacement approach requires adding output: 'export' to next.config.js instead of using the CLI command. The current next.config.js does not have this configuration.
| "isomorphic-fetch": "^3.0.0", | ||
| "markdownlint-cli": "^0.37.0", | ||
| "next": "^13.5.6", | ||
| "next": "^16.1.5", |
There was a problem hiding this comment.
ESLint plugin version mismatched with Next.js version
Low Severity
Upgrading next to 16.1.5 while @next/eslint-plugin-next remains at ^13.4.12 creates a version mismatch. The ESLint plugin is designed to work with the corresponding Next.js version and may produce incorrect linting results (false positives or missed issues) when used with a framework version three major releases ahead.
| "isomorphic-fetch": "^3.0.0", | ||
| "markdownlint-cli": "^0.37.0", | ||
| "next": "^13.5.6", | ||
| "next": "^16.1.5", |
There was a problem hiding this comment.
CI workflow uses Node 18, Next.js 16 requires Node 20
High Severity
Next.js 16.1.5 requires Node.js >= 20.9.0, but the GitHub Actions workflow (.github/workflows/docs.yml) uses node-version: 18 across all jobs. After this upgrade, CI jobs will fail because the Node.js runtime doesn't meet Next.js's engine requirements. The npm install or next build commands will error out in the CI pipeline.
Bumps next from 13.5.6 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.