Skip to content

[Snyk] Security upgrade next from 15.3.1 to 16.1.5 #17

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

Open
KB01111 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade next from 15.3.1 to 16.1.5 #17

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 frontend/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@
"leaflet": "^1.9.4",
"leaflet-defaulticon-compatibility": "^0.1.2",
"lucide-react": "^0.474.0",
"next": "15.3.1",
"next": "16.1.5",
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot Feb 2, 2026

Choose a reason for hiding this comment

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

critical

This upgrade to Next.js v16 is a major version change and introduces breaking changes. To ensure the project remains consistent and functional, a couple of things need to be addressed:

  1. Update pnpm-lock.yaml: As noted in the PR description, the lockfile has not been updated. You must run pnpm install to update pnpm-lock.yaml and commit the changes. Without this, the dependency update will not take effect, and the security vulnerabilities will persist.

  2. Update eslint-config-next: The eslint-config-next package in your devDependencies is still at version 15.3.1. It's crucial to keep this aligned with your next version to avoid linting errors and ensure compatibility. Please update it to match the new next version.

    -    "eslint-config-next": "15.3.1",
+    "eslint-config-next": "16.1.5",

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Feb 2, 2026

Choose a reason for hiding this comment

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

P2 Badge Update pnpm-lock.yaml to reflect the Next.js bump

frontend/package.json now requests next@16.1.5, but frontend/pnpm-lock.yaml still pins next@15.3.1 (see the next@15.3.1 entries around line 3879). As a result, any install that relies on the checked-in lockfile will continue using 15.3.1, so the security upgrade is not actually applied and environments may stay vulnerable until the lockfile is regenerated to match the new manifest.

Useful? React with 👍 / 👎.

"next-themes": "^0.4.6",
"react": "^19.1.0",
"react-dom": "^19.1.0",
Expand Down