Skip to content

[Snyk] Security upgrade next from 12.3.7 to 16.1.7 #499

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.

Sign up for GitHub

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

Merged
Ramyromel merged 1 commit into from
Mar 23, 2026
Merged

[Snyk] Security upgrade next from 12.3.7 to 16.1.7 #499

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 edge-middleware/clerk-authentication/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
"@peculiar/webcrypto": "^1.2.3",
"add": "^2.0.6",
"jose": "^4.4.0",
"next": "^12.1.0",
"next": "^16.1.7",
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot Mar 17, 2026

Choose a reason for hiding this comment

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

P1 Badge Align React major with upgraded Next.js

Upgrading next to ^16.1.7 while leaving react/react-dom on 17.0.2 creates an incompatible dependency set for this example, so fresh installs or builds can fail due to Next 16 peer/runtime expectations not matching React 17. In this commit only next was changed, so the project is left in a broken upgrade state until React (and any dependent libraries) is upgraded in tandem.

Useful? React with 👍 / 👎.

"react": "17.0.2",
"react-dom": "17.0.2",
"swiper": "^8.0.2"
Expand Down