chore(deps-dev): bump next from 15.2.4 to 16.1.5#558
chore(deps-dev): bump next from 15.2.4 to 16.1.5#558dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [next](https://github.com/vercel/next.js) from 15.2.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@v15.2.4...v16.1.5) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.5 dependency-type: direct:development ... 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 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| "marked": "^15.0.7", | ||
| "marked-highlight": "^2.2.1", | ||
| "next": "15.2.4", | ||
| "next": "16.1.5", |
There was a problem hiding this comment.
Version mismatch between Next.js and ESLint config
Low Severity
The next package was updated to version 16.1.5 but eslint-config-next remains at 15.2.4. These packages are designed to work together at matching major versions. This mismatch may cause ESLint to miss new Next.js 16 patterns, produce false positives for deprecated patterns, or have compatibility issues during linting.
Bumps next from 15.2.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
Medium risk because this is a major Next.js upgrade that can change build/runtime behavior and now requires a newer Node version, potentially impacting CI/deploy environments and image processing (
sharp).Overview
Bumps
nextfrom15.2.4to16.1.5inpackage.jsonand regeneratespackage-lock.jsonaccordingly.The lockfile update pulls in Next 16’s updated internals (new
@next/*swcartifacts,baseline-browser-mapping) and upgradessharp/libvips-related packages while removing older transitive deps (e.g.busboy,@swc/counter,color), and reflects Next 16’s newer Node engine requirement (>=20.9.0).Written by Cursor Bugbot for commit 543c924. This will update automatically on new commits. Configure here.