Skip to content

[Snyk] Security upgrade netlify-cli from 3.31.16 to 4.0.0 #11

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: master
Choose a base branch
from
Open

[Snyk] Security upgrade netlify-cli from 3.31.16 to 4.0.0 #11

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 @@ -28,7 +28,7 @@
"eslint": "^7.27.0",
"husky": "^6.0.0",
"lint-staged": "^11.0.0",
"netlify-cli": "^3.31.16",
"netlify-cli": "^4.0.0",
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Jan 12, 2026

Choose a reason for hiding this comment

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

P2 Badge Update lockfile to match netlify-cli bump

The change bumps netlify-cli to ^4.0.0 in package.json, but package-lock.json still pins it at ^3.31.16 (see package-lock.json lines 10–21). Any environment that installs strictly from the lockfile will continue using 3.31.16 and miss the intended upgrade, so the security fix won’t actually apply until the lockfile is regenerated and committed.

Useful? React with 👍 / 👎.

"prettier": "^2.3.0",
"typescript": "^4.3.2"
},
Expand Down