Skip to content

[Snyk] Security upgrade diff from 3.5.0 to 8.0.3 #41

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

[Snyk] Security upgrade diff from 3.5.0 to 8.0.3 #41

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 packages/components/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"@wordpress/url": "file:../url",
"classnames": "^2.2.5",
"clipboard": "^2.0.1",
"diff": "^3.5.0",
"diff": "^8.0.3",

@chatgpt-codex-connector chatgpt-codex-connector Bot Jan 23, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Update lockfile so diff actually upgrades

Changing packages/components/package.json alone doesn’t update the resolved version in package-lock.json, which still pins diff to 3.5.0. Any install that uses the lockfile (e.g. npm ci in CI or contributors) will continue to pull 3.5.0 and the ReDoS fix won’t be applied, so the security upgrade is effectively skipped in those environments. The lockfile needs to be updated alongside this dependency bump to make the upgrade take effect.

Useful? React with 👍 / 👎.

"dom-scroll-into-view": "^1.2.1",
"lodash": "^4.17.10",
"memize": "^1.0.5",
Expand Down