Skip to content

[Snyk] Security upgrade next from 13.5.6 to 14.2.35 #1109

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
patinthehat wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade next from 13.5.6 to 14.2.35 #1109

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 package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
"@heroicons/react": "^2.2.0",
"axios": "^1.12.0",
"dotenv": "^16.4.7",
"next": "^13.5.6",
"next": "^14.2.35",
"react": "^18.2.0",
Comment on lines 31 to 33
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Dec 15, 2025

Choose a reason for hiding this comment

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

P1 Badge Update package-lock to match Next 14 bump

The dependency is bumped to next@^14.2.35 in package.json, but package-lock.json still pins Next 13.5.6 (lines 9066‑9072), so any install using the lockfile (e.g., npm ci in CI) will fail because the locked version no longer satisfies the declared range and the security upgrade never actually gets applied.

Useful? React with 👍 / 👎.

"react-dom": "^18.3.1",
"react-ga": "^3.3.1",
Expand Down
Loading