chore(deps): bump next from 14.2.35 to 16.1.5 in /ui/litellm-dashboard#21
chore(deps): bump next from 14.2.35 to 16.1.5 in /ui/litellm-dashboard#21dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [next](https://github.com/vercel/next.js) from 14.2.35 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.2.35...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
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
![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.
| "lucide-react": "^0.513.0", | ||
| "moment": "^2.30.1", | ||
| "next": "^14.2.32", | ||
| "next": "^16.1.5", |
There was a problem hiding this comment.
Node.js version requirement mismatch after upgrade
High Severity
The engines field specifies node >= 18.17.0, but Next.js 16.1.5 requires Node.js >= 20.9.0. This mismatch means the application will fail to build or run on Node.js 18.x environments, despite the package.json claiming compatibility. CI/CD pipelines and developer machines using Node 18 will encounter runtime failures.
| "lucide-react": "^0.513.0", | ||
| "moment": "^2.30.1", | ||
| "next": "^14.2.32", | ||
| "next": "^16.1.5", |
There was a problem hiding this comment.
ESLint config version mismatched with Next.js major version
Medium Severity
The eslint-config-next remains at version 14.2.32 while next was upgraded to 16.1.5. These versions are typically meant to be kept in sync, and version mismatches can cause linting rules to miss new patterns or incorrectly flag valid Next.js 16 code patterns.
|
Superseded by #47. |
Bumps next from 14.2.35 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 (Next 14→16) with an updated lockfile, which can introduce runtime/build and Node version compatibility issues despite being dependency-only.
Overview
Upgrades
ui/litellm-dashboardto Next.js16.1.5(from14.2.x).Updates
package-lock.jsonto match the new Next version, including updated Next/SWC artifacts and new optional dependencies (notablysharp) while removing/replacing some prior transitive packages.Written by Cursor Bugbot for commit 2010877. This will update automatically on new commits. Configure here.