Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/ai-database/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Copy link

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 next dependency is upgraded to 16.1.5 but eslint-config-next in devDependencies remains at version 15.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.

Fix in Cursor Fix in Web

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Payload CMS incompatible with Next.js 16 Turbopack

High Severity

Upgrading next to 16.1.5 while @payloadcms/next remains at version 3.33.0 creates a known incompatibility. Next.js 16 uses Turbopack as the default bundler, but @payloadcms/next 3.33.0's withPayload function unconditionally injects webpack configuration, which breaks the Turbopack setup. This is documented in GitHub issue #14354 on the Payload repository. The application may fail to build or run correctly in development mode.

Fix in Cursor Fix in Web

"payload": "3.33.0",
"react": "19.1.0",
"react-dom": "19.1.0",
Expand Down
Loading