-
Notifications
You must be signed in to change notification settings - Fork 2
chore(deps): bump next from 15.3.0 to 16.1.5 in /packages/ai-database #235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -39,7 +39,7 @@ | |
| "gray-matter": "^4.0.3", | ||
| "isolated-vm": "^5.0.4", | ||
| "libsql": "^0.5.10", | ||
| "next": "15.3.0", | ||
| "next": "16.1.5", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Payload CMS incompatible with Next.js 16 TurbopackHigh Severity Upgrading |
||
| "payload": "3.33.0", | ||
| "react": "19.1.0", | ||
| "react-dom": "19.1.0", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ESLint config version mismatched with Next.js version
Low Severity
The
nextdependency is upgraded to16.1.5buteslint-config-nextin devDependencies remains at version15.3.0. These versions are designed to be kept in sync, as the ESLint configuration is version-specific to Next.js and contains rules that match the framework version's conventions and APIs. Using a mismatched version may result in outdated linting rules, false positives for newer Next.js 16 patterns, or missing warnings for deprecated patterns.