Skip to content

chore(deps): bump next from 16.3.7 to 16.3.8 in /sites/mainweb #495

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

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps): bump next from 16.3.7 to 16.3.8 in /sites/mainweb #495

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 sites/mainweb/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
"geist": "^1.7.2",
"lucide-react": "^1.48.0",
"minimatch": "10.2.6",
"next": "16.3.7",
"next": "16.3.8",

@cursor cursor Bot Oct 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Lockfile still pins vulnerable Next

High Severity

sites/mainweb/package.json now asks for next 16.3.8, but pnpm-lock.yaml still specifies 16.3.7 for that workspace. CI runs pnpm install --frozen-lockfile, so verify fails, and lockfile-honoring installs stay on the unpatched release.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 98da3a1. Configure here.

"next-auth": "5.0.0-beta.32",
"next-themes": "^0.4.6",
"pdf-lib": "^1.17.1",
Expand Down
Loading