Bump next from 15.4.10 to 16.1.5 in /website#144
Conversation
Bumps [next](https://github.com/vercel/next.js) from 15.4.10 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.4.10...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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![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.
| "mermaid": "^11.10.0", | ||
| "motion": "^11.18.0", | ||
| "next": "15.4.10", | ||
| "next": "16.1.5", |
There was a problem hiding this comment.
Version mismatch between next 16 and @next/mdx 15
Medium Severity
The next package is upgraded to 16.1.5, but @next/mdx remains at ^15.4.5. The @next/mdx package is tightly coupled with Next.js internals and is typically versioned to match the major version of next. This major version mismatch could cause MDX compilation failures, runtime errors, or unexpected behavior since the packages may rely on incompatible internal APIs.
Additional Locations (1)
| "mermaid": "^11.10.0", | ||
| "motion": "^11.18.0", | ||
| "next": "15.4.10", | ||
| "next": "16.1.5", |
There was a problem hiding this comment.
Version mismatch between next 16 and eslint-config-next 15
Low Severity
The next package is upgraded to 16.1.5, but eslint-config-next remains at 15.4.5. The ESLint config package is versioned alongside Next.js and contains rules specific to each major version. This mismatch could cause incorrect linting results—either missing valid warnings for Next.js 16 patterns or producing false positives for deprecated patterns.
Additional Locations (1)
|
Superseded by #162. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/website/next-16.1.5
branch
Bumps next from 15.4.10 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 Next.js upgrade plus a higher Node.js minimum version can affect builds and runtime behavior; changes are dependency-only but may require CI/runtime environment updates.
Overview
Updates the
websiteapp from Next.js 15.4.10 to 16.1.5, refreshing the lockfile to pull in the matching@next/*packages and SWC binaries.The
package-lock.jsonchanges also add Next 16’s new dependencybaseline-browser-mapping, adjust Next’s Node engine requirement to>=20.9.0, and change how some optional native packages (e.g.,sharpplatform artifacts) are classified in the lockfile.Written by Cursor Bugbot for commit b26fc18. This will update automatically on new commits. Configure here.