Skip to content

[Snyk] Upgrade next from 12.1.6 to 12.3.7 #623

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

[Snyk] Upgrade next from 12.1.6 to 12.3.7 #623

Show file tree
Hide file tree
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
203 changes: 109 additions & 94 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

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 @@ -12,7 +12,7 @@
"format": "prettier '**/*' --write --ignore-unknown"
},
"dependencies": {
"next": "latest",
"next": "12.3.7",
Copy link

@gemini-code-assist gemini-code-assist bot Jan 23, 2026

Choose a reason for hiding this comment

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

medium

While pinning to a specific version 12.3.7 is a great improvement over using latest for ensuring build reproducibility, consider using a caret ^ prefix (e.g., ^12.3.7). This allows npm to automatically fetch non-breaking minor and patch updates, which often include important security fixes and bug fixes, without requiring manual version bumps. This is a common best practice for dependency management.

Suggested change
"next": "12.3.7",
"next": "^12.3.7",

"react": "17.0.2",
"react-dom": "17.0.2"
},
Expand Down
Loading