Skip to content

[Snyk] Security upgrade next from 16.1.4 to 16.1.5 #21

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

[Snyk] Security upgrade next from 16.1.4 to 16.1.5 #21

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 @@ -18,7 +18,7 @@
"class-variance-authority": "^0.7.1",
"clsx": "^2.1.1",
"lucide-react": "^0.562.0",
"next": "16.1.4",
"next": "16.1.5",
Copy link

Copilot AI Feb 2, 2026

Choose a reason for hiding this comment

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

Updating the next version in package.json without updating bun.lock leaves the lockfile pinned to 16.1.4, so installs using the existing lockfile will not pick up 16.1.5 and the Snyk-reported vulnerability may remain. Please regenerate and commit bun.lock (e.g. via bun install) so the lockfile reflects next@16.1.5 (see bun.lock lines 17 and 762).

Suggested change
"next": "16.1.5",
"next": "16.1.4",

Copilot uses AI. Check for mistakes.
"next-themes": "^0.4.6",
"posthog-js": "^1.332.0",
"react": "^19.2.3",
Expand Down